Agent Sandboxesagentsandboxes.org
Sandbox profile · Open-source project

Matchlock

Answer in brief

Experimental MIT CLI and Go, Python and TypeScript SDKs that run AI agents from OCI images in ephemeral microVMs, with a host-side proxy that enforces an egress allow-list and injects secrets the VM never sees. An experimental local microVM sandbox for agents whose distinguishing feature is host-side egress control and secret injection.

By the Agent Sandboxes editors · Updated

Overview

Matchlock is an MIT-licensed CLI, with Go, Python and TypeScript SDKs, for "running AI agents in ephemeral microVMs". It boots OCI images (pulled from a registry, imported from docker save or built from a Dockerfile with BuildKit inside a VM) as microVMs: Firecracker on Linux with KVM and Apple Virtualization.framework on Apple Silicon Macs, according to the repository's developer reference. The README says a sandbox "boots in under a second" and that the CLI behaves the same on a Linux server and a MacBook. The examples directory covers Claude Code, OpenAI Codex CLI, Docker inside the sandbox and browser automation with Playwright MCP.

Its focus is the network boundary. With an allow-list or a secret configured, a host-side proxy blocks every host not on the list and substitutes real credentials into outbound requests in flight, so code in the VM only ever reads a placeholder; SDK hooks can also rewrite requests and responses. Host directories are never shared: files are copied in and out explicitly, and only attached block volumes persist. The README marks the project "Experimental" and subject to breaking changes; it was at v0.3.1 at verification, and no hosted service is documented.

Notable

  • Release v0.3.1 on 31 October 2026; 654 GitHub stars at verification.
  • Secrets are injected by a host-side MITM proxy, so the guest environment only holds a placeholder value.
  • matchlock build runs BuildKit inside a VM and imports the result into the local image store.

Matchlock specifications

AttributeDetails
IsolationMicroVM per sandbox: Firecracker on Linux with KVM and Apple Virtualization.framework on macOS (Apple Silicon); no host directories are shared with the guest, and a host-side policy and HTTP/TLS proxy sits between the guest and the network
DeploymentOpen-source project · Self-hostable
Open sourceYes (MIT)
SDKs and interfacesGo, Python, JavaScript/TypeScript, CLI
Cold start (vendor claim)README: a full Linux environment that "boots in under a second" (vendor claim); pulled images are cached for faster startup
Max session lengthNot documented
PersistenceGuest-local changes are disposable unless a persistent block volume is attached (matchlock volume with run --disk @name:/guest/path). Sandboxes started with --rm=false or -d keep running for later exec. There are no host-directory mounts; files move in and out with matchlock cp, --copy-in/--copy-out or the SDK file APIs
GPUNot documented
NetworkingPassing --allow-host or --secret seals the network so only allowed hosts are reachable, and the allow list can be edited at runtime; real secrets stay on the host and are injected into allowed outbound requests while the guest sees a placeholder. SDK interception rules can mutate requests and responses. The Go SDK blocks private IP ranges by default when a network config is sent; --no-network gives a guest with no NIC; ports can be published or forwarded. Linux uses a transparent proxy (nftables DNAT on ports 80/443); macOS uses Virtualization.framework NAT, or gVisor's userspace TCP/IP stack when intercepting
PricingFree and open source under MIT; no hosted offering is documented
Free tierFree (MIT)
ComplianceNot documented
RegionsNot documented
Company headquartersNot documented

Facts from Matchlock’s public documentation, verified November 18, 2026. Performance numbers are vendor claims.

Strengths and trade-offs

Strengths

  • You want an agent to have a full Linux VM while its API keys never enter the guest.
  • You need a default-deny egress allow-list you can edit while the sandbox runs.
  • You run agents on both Linux servers and Apple Silicon Macs and want one CLI and SDK for both.
  • You want no host-directory sharing, with explicit copy-in and copy-out.

Trade-offs

  • Labelled experimental and subject to breaking changes.
  • No host-directory mounts; files must be copied in and out or kept on block volumes.
  • Snapshots, pause/resume, GPU support and session limits are not documented.
  • Self-host only; no hosted service is documented.

Good fit for: Running coding agents on a Linux server or Apple Silicon Mac in disposable microVMs with locked-down egress and API keys kept on the host.

How Matchlock compares

SandboxCompany HQIsolationOpen sourceSelf-host / BYOCCold start (vendor)Max sessionSnapshots / pauseGPUSDKs
MatchlockNot documentedFirecracker / Apple VZ microVMYesYes / Not documented<1 s (claim)Not documentedNot documented / Not documentedNot documentedGo, Python, JavaScript/TypeScript, CLI
smol machines (smolvm)Not documentedlibkrun microVMYesYes / Not documented<200 ms (claim)Not documentedYes / YesYesJavaScript/TypeScript, Python, Rust, Go, CLI, REST API
MicrosandboxNot documentedMicroVM (libkrun)YesYes / Yes<100 msNot documentedYes / Not documentedNot documentedTypeScript, Python, Rust, Go, Ruby, CLI, MCP server
nonoNot documentedLandlock / SeatbeltYesNo / NoNot documentedNot documentedYes / Not documentedNot documentedCLI, Rust, Python, JavaScript/TypeScript, Go
PullrunNot documentedFirecracker / Apple VM / runcYesYes / No~500 ms (claim)Not documentedYes / Not documentedNot documentedCLI, MCP server
BoxLiteNot documentedmicroVM + jailerYesYes / Not documented~1 s (claim)Not documentedNot documented / Not documentedNot documentedPython, JavaScript/TypeScript, Go, Rust, C, CLI, REST API
Docker SandboxesUnited StatesMicroVMNoYes / NoNot documentedUntil removed (local)Yes / YesYessbx CLI, TypeScript (cloud), REST API (cloud)

Head-to-head: Gondolin vs Matchlock

See all Matchlock alternatives →

Frequently asked questions

What is Matchlock?
Experimental MIT CLI and Go, Python and TypeScript SDKs that run AI agents from OCI images in ephemeral microVMs, with a host-side proxy that enforces an egress allow-list and injects secrets the VM never sees. An experimental local microVM sandbox for agents whose distinguishing feature is host-side egress control and secret injection.
How does Matchlock isolate code?
Matchlock documents its isolation as: MicroVM per sandbox: Firecracker on Linux with KVM and Apple Virtualization.framework on macOS (Apple Silicon); no host directories are shared with the guest, and a host-side policy and HTTP/TLS proxy sits between the guest and the network.
Is Matchlock open source?
Yes (MIT). It can be self-hosted.
How much does Matchlock cost?
Free and open source under MIT; no hosted offering is documented Check the official pricing page for current rates.
What are the alternatives to Matchlock?
Common alternatives include smol machines (smolvm), Microsandbox, nono, Pullrun, BoxLite, Docker Sandboxes. See Matchlock alternatives for a full comparison.

Sources

  1. github.com/jingkaihe/matchlock
  2. github.com/jingkaihe/matchlock/blob/main/AGENTS.md
  3. github.com/jingkaihe/matchlock/tree/main/docs
  4. github.com/jingkaihe/matchlock/blob/main/docs/lifecycle.md
  5. github.com/jingkaihe/matchlock/releases

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 18, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

Agent Sandboxes. (2026). Matchlock. agentsandboxes.org. Last reviewed November 18, 2026. https://agentsandboxes.org/sandboxes/matchlock/