● firelock
Firecracker-microVM execution shell

Every agent has a pulse. Now you can watch it.

Sealed by construction. Visible by design.

Firelock confines an untrusted guest to a single, guest-initiated vsock egress and relays that connection to a handler you choose. No network interface for the guest to reach out on — just the one audited seam everything, including what you watch, travels through.

Status: 1.1.0 — this repository carries the confinement/relay contract, the OSS default handler, the TypeScript runtime (Firecracker client and pool, jailer, vsock, fd-handoff FFI bindings, per-invocation VM), the native crates (fd-handoff transport, handler confinement with seccomp) and the guest init.
The Sealed Heart — a precision-machined mechanical heart, glowing blue, hermetically sealed inside a crystal-clear glass chamber, with one thin fibre-optic cable carrying its heartbeat out to the one audited channel on the outside.

The runtime gap

Three trade-offs every sandbox or serverless runtime forces on you. Three answers Firelock is built around.

01 · the blind sandbox

Kernel-native visibility

Seal a workload properly and you usually lose sight of it. Firelock keeps resource and lifecycle signals emitting from inside the sealed guest, riding out over the same seam as everything else — no sidecar required.

02 · the leaky sidecar

One audited egress

The usual fix punches a hole in the seal: a monitoring agent that talks to the network. Firelock gives the guest exactly one vsock channel it can ever dial out on — everything leaves the same single, auditable way.

03 · the open network

Network-less by construction

A workload with a network stack can reach anything the network can. Firelock's guest has zero virtual network interfaces — no tun/tap, no bridge — so it structurally cannot scan a LAN or resolve a domain.

What's in the box

Four capabilities that define what Firelock is. Ship status is marked plainly — nothing here claims more than the repo does.

Network-less microVM shipped

Zero NICs on the guest — no tun/tap, no bridge, no TCP/IP stack. Asserted fail-closed by assertFirelockTopology.

A single audited egress shipped

One vsock seam, one fd handoff. Never zero-leak — data does leave, through that one seam, by design. See the wire contract.

Fast warm starts design intent

In the platform Firelock was extracted from, a pre-warmed snapshot pool resumes a slot in ~17 ms. That pool/orchestration layer isn't yet part of this repo.

Runaway-resource circuit-breaker roadmap

Autonomous teardown of a workload that saturates its resource budget — not a claim of catching every infinite loop. Not yet implemented in src/.

The confinement guarantee

A Firelock-confined microVM has zero network interfaces and exactly one vsock device. That is asserted, fail-closed, in one place — assertFirelockTopology. "Could not check" is never "it is fine": an unreadable or ambiguous VM config is refused, not waved through.

  ZERO network interfaces (no NIC, no add-interface code path)  → closes IP egress   [BY CONSTRUCTION]
  Firecracker's built-in seccomp filters                        → closes non-vsock families
  ONE vsock device / one host socket per VM                     → closes multi-channel
  —————————————————————————————————————————————
  = exactly one guest-initiated egress, and it is the seam.

Isolation, precisely stated: no network interface — by construction. Not "unhackable," not "mathematically impossible" — a structural property you can check. The seam itself is tamper-evident: a topology that would allow a second channel is refused outright, not silently accepted.

Go deeper

The wire contract is the whole language-agnostic boundary. The repo is where the code lives.