Code & AI agent sandboxes: read the guide

Brig

Open source toolSandbox

The microVM sandbox for AI coding agents.

Homepage Docs Repository

Scanned 14 Oct 2026 · Schema v5 · features v21

Licence: Apache-2.0
Self-hosted; you pay for the infrastructure.
Free tier: Free to run
Isolation: Virtual machine
hypervisor, or nothing at all
Regions: —
Not disclosed on the public surface.
Capabilities: 13 / 61
0 partial · 45 fail · 0 not assessed
Agent readiness: 7/10 · 5/8
read · drive, pre-login surface

Advertised for

Coding agents · Interactive shells · OCI based development environments

Built for

Developers, then technical

· CLI-first local VM sandbox, OCI profiles, security policies.

01 Website design Desktop public website · assessed 14 Oct 2026

Complete assessment.

The desktop landing and documentation pages use a restrained white, dark-ink and amber visual system: bold sans-serif headings, generous aligned spacing, pale technical panels and a pixel-like wordmark. Documentation adds flanking navigation and a hand-drawn four-step microVM explanation.

Editorial minimalism
Swiss-inspired
Technical illustration

Landing page: captured
Pricing: not applicable
Docs: captured

02 Runtime Each fact carries its source; dots show confidence. Open a row for the evidence.

Isolation & lifecycle

Isolation primitive

Virtual machinehypervisor, or nothing at all

Persistence

Project and guest-home host mounts persist; disposable guest state does not. Brig-created home survives stop/reboot but rm deletes it.

Snapshots / forks

Resources & limits

Storage

Selected project read-write mount and per-session guest home.

Limits & quotas

Local host resources and profile settings; no cloud quota.

GPU

Not documented

Access

Deploy interface

clilocal-unix-socket

SDK languages

None

Network & secrets

Egress controls

hvi gateway or Linux nftables policies; unsupported backends refuse policy-bound runs.

Secrets

Named credentials forwarded into guest; host keychain/keyring, per-exec injection.

Bring your own cloud

Placement & use

Jurisdiction

Advertised workloads

Coding agentsInteractive shellsOCI based development environments

03 Capabilities 13 pass · 0 partial · 45 fail · 61 of 61 assessed

Supported — Documented on the public surface and verified.
Partially supported — Exists with caveats: gated, thin, or enterprise-only.
Not supported — Checked and not offered.
Not assessed — Scanned before this capability was tracked. Not a lack.

Compute & storage 3/10

Persistent diskStorage that survives restart/stop (not ephemeral-only).

Supported

Object storageManaged S3-compatible / blob object store the platform PROVIDES to a user's workloads (buckets, presigned URLs). DISTINCT from persistent-disk (block/volume attached to an instance) and from a self-host dependency (source.self_host.deps[]=["object-storage"] is an infra dep to RUN an OSS tool — the opposite direction). SCOPE varies and matters: native first-class (Railway Buckets, Cloudflare R2) vs a sibling SKU / extension (Fly Tigris, Bunny Storage, DigitalOcean Spaces) — record which in the evidence quote / note. Admitted v15.

Not supported

Snapshots / forkingSnapshot or copy-on-write fork of a running instance (filesystem-only counts). Whether the snapshot also restores memory + running processes is recorded separately by memory-snapshot (v19).

Not supported

Live-state (memory) snapshotsA snapshot / checkpoint / pause captures a running instance's MEMORY and PROCESS state and restores it, so running processes continue where they left off instead of a freshly booted instance with the same files. Counts whether user-triggered (snapshot, checkpoint, pause-to-storage) or used to restore pre-initialised state (memory snapshots for fast cold starts). Distinct from snapshots-forks (any snapshot or fork, including filesystem-only; a product passing that key may still fail this one) and from scale-to-zero (an idle-cost property; suspension may or may not keep memory). Actor multiplexing (see scale-to-zero) records its live-state half here — only when the suspended actor's MEMORY/process state is what comes back, not a freshly booted worker with the actor's files.

Not supported

Scale to zeroIdle instances suspend at no / negligible cost. ACTOR MULTIPLEXING (many suspended stateful actors sharing a small pool of pre-warmed workers, woken on request — Agent Substrate, AX, kagent; Rivet's hibernating actors) has NO key of its own (proposal REJECTED v20) — score the idle-cost half HERE and the live-state half under memory-snapshot; the oversubscription ratio / density is a performance characteristic the registry does not key.

Not supported

GPU computeGPU-backed instances available.

Not supported

Multi-regionCompute placeable in more than one geographic region.

Not applicable

Sandbox templates / custom imagesBuild reusable sandbox/VM images from an OCI image or Dockerfile (a base you fork instances from).

Supported

Cloud-init / ignition configCustomise a VM / microVM / instance at boot via cloud-init (or ignition) user-data — the same boot-metadata interface as AWS/Azure/GCP. Inject packages, users, SSH keys, files, and run-commands declaratively at launch. Distinct from sandbox-templates (a PREBUILT image you fork instances from) — this is PER-LAUNCH declarative customisation, not a baked image.

Not supported

Desktop / computer-use sandboxA virtual desktop (GUI) for LLM computer-use — browser + desktop automation, often via noVNC/VNC.

Not supported

Selectable isolation runtimeThe user chooses the isolation runtime per workload / environment / sandbox from more than one option (e.g. microVM vs gVisor vs plain container, native namespaces vs gVisor, gVisor vs VM). Records the CHOICE; the isolation_primitive facet still records the best-evidenced primary. A platform that switches runtime automatically without a user choice (e.g. gVisor forced for GPU) does not pass on that alone.

Supported

Networking & delivery 2/9

Automatic HTTPSTLS endpoints provisioned automatically per workload.

Not supported

Built-in reverse proxyPlatform routes external traffic to workload services.

Not supported

Custom domainsBring-your-own domain via CNAME/DNS.

Not supported

Public preview URLsShareable per-deploy / per-branch URLs.

Not supported

Direct public IPv6Per-instance stable public IPv6 for raw TCP/UDP (beyond a managed HTTPS proxy) — e.g. mosh / raw sockets.

Not supported

Egress controlsConfigurable OUTBOUND network policy — egress firewall / allowlist / egress proxy on traffic LEAVING a workload. Scoped to OUTBOUND only (v15): private-network REACHABILITY between a user's own services is private-networking, not this. Static-egress-IP belongs here (an outbound concept).

Supported

Private networkingA platform-internal private network between a user's OWN services — service-to-service connectivity, VPC, service mesh, and/or service discovery, not exposed to the public internet. DISTINCT from egress-controls (OUTBOUND firewall/allowlist), reverse-proxy (PUBLIC inbound ingress), and direct-ipv6 (per-instance PUBLIC addressing). Admitted v15.

Supported

Email send / receiveSend and/or receive email from the workload.

Not supported

Edge KV storeA globally-replicated key-value store read from WITHIN an edge runtime at the PoP (low-latency, eventually-consistent) — Cloudflare Workers KV, Deno KV, Fastly KV Store, Akamai EdgeKV, Vercel Edge Config. Distinct from first-party-db (a managed DATABASE service you provision and connect to) and from http-query-api (HTTP access to an external store) — edge-kv is colocated with the edge compute and read at the edge.

Not supported

Developer access 2/10

Public APIDocumented programmatic API.

Supported

OpenAPI specMachine-readable OpenAPI / Swagger spec published.

Not supported

CLIOfficial command-line tool.

Supported

SDKOfficial client library/libraries.

Not supported

SSH accessDirect SSH into workloads.

Not supported

Filesystem APIRemote file operations over the API (list/read/write/watch/copy/upload) without SSH.

Not supported

Git deployDeploy from a Git repo / push-to-deploy.

Not supported

Private container registryHosted private image registry.

Not supported

E2B-compatible APIDrop-in compatibility with the E2B sandbox API/SDKs — existing E2B client code runs against this product by changing the endpoint/domain + key, with no business-code changes. E2B itself passes as the reference implementation. Distinct from public-api / sdk (the product has its own API — this key says it also speaks another vendor's) and from self-host-oss (a self-hosted E2B-compatible server is scored on both).

Not supported

HTTP data APIQuery / read / write the stored DATA over plain HTTP/REST (or GraphQL) WITHOUT the native protocol driver (Postgres wire / Redis RESP) — agent- and edge-friendly data access via fetch(). The DATA plane; distinct from public-api (a control-plane / management API). Auto-generated-from-schema REST/GraphQL (PostgREST, pg_graphql) is a flavour of this.

Not supported

AI & agents 3/12

Built-in coding agentShips a first-party AI coding agent in the product.

Not supported

Agent skillsInstallable / declarable agent skills or tools.

Supported

AI app builderPrompt-to-app / vibe-coding generation surface.

Not supported

MCP serverExposes a Model Context Protocol server for agents.

Not supported

MCP clientActs as an MCP client / consumes MCP tools.

Not supported

MCP-server hostingRun/host MCP servers as a workload on the platform (distinct from exposing a first-party MCP control server — that is mcp-server).

Not supported

LLM gatewayRoutes LLM API calls through the platform (multi-provider).

Not supported

BYOK for LLMsBring-your-own LLM provider keys.

Supported

Model inference API (first-party)A FIRST-PARTY hosted LLM/model inference API — the provider serves its OWN catalogue of (usually open-weight) models behind a (typically OpenAI-compatible) endpoint, billed per token. Distinct from llm-gateway (a multi-PROVIDER proxy/router for YOUR calls to external providers like OpenAI/Anthropic) and from byok-llm (bring your own provider keys) — here the platform IS the inference provider, serving its own models.

Not supported

Autonomous QA agentA first-party AUTONOMOUS AI agent that QA-TESTS a running app / implementation — exercising it like a real user (clicking through flows, checking behaviour) and reporting bugs/defects (often back to a coding agent, or before a human review). Distinct from built-in-agent (a code-AUTHORING agent — this one VERIFIES the result, it does not write the feature; a product can ship both), from ai-guided-code-review (organises a diff for a HUMAN to review — not an autonomous tester), and from observability (runtime metrics/logs, not active testing).

Not supported

Credential-injection proxyThe platform holds real secrets OUTSIDE the workload and injects them on the wire (an egress / broker proxy swaps a placeholder or phantom token for the real credential on matching outbound requests), so code running in the sandbox — e.g. an untrusted agent — never sees or can exfiltrate the real key. Distinct from secrets-management (storage + injection INTO the workload as env vars/files — the workload holds the secret) and from egress-controls (outbound allow/deny POLICY; a product can have an allowlist without injecting credentials, and vice versa).

Not supported

Preinstalled coding agentThe platform installs and launches a THIRD-PARTY coding agent (a harnesses.yml entry — Claude Code, Codex, OpenCode, Pi ...) inside a workspace/sandbox it provisions, with the agent's auth wired in (your own account or API key), so you start an agent session rather than an empty box. Distinct from built-in-agent (a FIRST-PARTY agent the vendor ships) and from harnesses[] (which records that a harness CAN target the product, not that the product runs it for you).

Supported

Data 0/4

First-party databasePlatform-provided managed database.

Not supported

Database branchingCopy-on-write branch of a DATABASE (schema + data) as a dev-lifecycle primitive — branch your data like code, usually instant via a metadata operation. Distinct from snapshots-forks (forks a running compute INSTANCE / VM state) and from preview-environments (a full per-PR environment that may USE a DB branch). For a data product a CoW branch maps HERE, not to snapshots-forks.

Not supported

Vector searchFirst-class storage, indexing, and similarity search of vector embeddings — a native vector type/index or a managed vector DB. The data-layer primitive for RAG / semantic retrieval.

Not supported

Ephemeral instant DB (no-signup)Provision a working, usable instance via a single command / HTTP call with NO account, signup, or card — typically time-boxed (expires unless claimed). A zero-onboarding path an agent can hit directly.

Not supported

Platform & operations 1/6

Scheduled tasksCron / scheduled job primitive.

Not supported

Durable workflowsDurable execution / long-running workflow primitive.

Not supported

Preview environmentsA full EPHEMERAL environment spun up per PR / branch — compute + addons + (often) a DB branch — torn down on merge. More than preview-urls (which is just a shareable URL for one deploy).

Not supported

Built-in observabilityFirst-party metrics / logs / tracing / APM / profiling included in the platform (no third-party stack required to see what a workload is doing).

Supported

Managed CI/CD runnersPlatform-hosted, drop-in CI/CD runner VMs (GitHub Actions / GitLab), typically faster and cheaper than the CI vendor's own hosted runners, billed per runner-minute; isolated + ephemeral per job. Distinct from git-deploy (push-to-deploy of an APP) and scheduled-tasks (cron) — this is managed CI COMPUTE you point your existing pipelines at.

Not supported

Project template marketplaceA marketplace / gallery of prebuilt PROJECT STARTER templates (apps or websites) a user clones or launches a new project from and then customises — the "start from a template" surface of a builder / PaaS. Distinct from sandbox-templates (a COMPUTE base IMAGE you fork runtime INSTANCES from — Dockerfile / OCI), from app-builder (the prompt-to-app GENERATION surface — a product can have both), and from one-click OSS-app catalogues / helm-addon-marketplace (deploy a FINISHED app as-is, not a starter you build on).

Not supported

Organisation & security 2/7

Built-in authPlatform-provided authentication / IAM for workloads.

Not supported

SSO / SAMLEnterprise single sign-on.

Not supported

Secrets managementFirst-class secrets storage / injection.

Supported

TeamsMulti-user team accounts.

Not supported

SharingShare a running workload/resource via link (optionally gated).

Not supported

BYOCRuns inside the customer's own cloud account.

Not applicable

Deploy into customers' VPCsA SaaS vendor uses the platform to deploy and operate ITS software inside ITS CUSTOMERS' cloud accounts / VPCs (nested or "customer BYOC"), managed from the vendor's control plane. Distinct from byoc (your own workloads in your own cloud account).

Not applicable

Workload identityThe platform gives each workload its own verifiable identity (OIDC token, SPIFFE SVID, cloud IAM federation) that it exchanges for short-lived credentials, so no long-lived static secret is stored or injected. Distinct from secrets-management (stores / injects static secrets) and credential-injection-proxy (swaps real secrets in on the wire).

Not supported

Self-host / OSS coreOpen-source core that can be self-hosted.

Supported

04 Agent readiness Pre-login surface · counts, not a grade

Can an agent read it?

parse-ability · docs, metadata, machine-readable surfaces

7/10

6 full · 1 partial · 70% of applicable checks

llms.txt
Supported
“https://www.brig.sh/llms.txt: substantive categorized documentation index.”
llms-full.txt
Not supported
“https://www.brig.sh/llms-full.txt: 404; docs variant also absent.”
robots.txt AI policy
Partially supported
“https://www.brig.sh/robots.txt: wildcard Allow, no AI-specific directives.”
JSON-LD
Not supported
“Homepage HTML has no JSON-LD.”
Sitemap
Supported
“https://www.brig.sh/sitemap.xml: substantive docs sitemap.”
Meta tags
Supported
“Homepage descriptive title, description, Open Graph.”
Markdown negotiation
Not supported
“Homepage/docs Accept text/markdown returns HTML; .md variants 404.”
Content efficiency
Supported
“Visible text excluding scripts/styles: 7.27% of 30258 homepage HTML bytes.”
Docs discoverable
Supported
“Homepage header links /docs/.”
Machine-readable pricing
Not applicable
“No hosted pricing: free local Apache-2.0 tool.”
No anti-bot wall
Supported
“Product homepage, docs and well-known files accessible without challenge.”

Can an agent drive it?

act-ability · APIs, SDKs, MCP, credentials, webhooks

5/8

4 full · 1 partial · 63% of applicable checks

Public API
Supported
“https://www.brig.sh/docs/brigd/: documented owner-only Unix-socket JSON lifecycle API.”
OpenAPI spec
Not applicable
“Local JSON socket protocol, not hosted HTTP API.”
MCP server
Not supported
“No first-party MCP server documented; well-known probe 404.”
SDK packages
Not supported
“https://github.com/brig-sh/brig/blob/main/docs/non-goals.md: SDKs explicitly non-goal.”
Auth documented
Supported
“https://www.brig.sh/docs/brigd/: socket 0600 and kernel peer UID authentication.”
Self-serve credentials
Not applicable
“No hosted account/key issuance; local owner UID.”
Webhooks
Not supported
“No lifecycle webhooks documented.”
CLI tool
Supported
“https://www.brig.sh/docs/cli/: official CLI and JSON output.”
Error model
Supported
“https://www.brig.sh/docs/brigd/: v, ok, code, error response fields and version rules.”
Rate limits documented
Not applicable
“No hosted API rate limits; local timeout/size limits documented.”
Agent config files
Partially supported
“https://www.brig.sh/docs/agents/: repository coding-agent instructions; no well-known endpoint.”

05 Coding harnesses Which agents and IDEs are documented to run here

Advertised integrations 4

Claude Code Anthropic
Supported
“Built-in claude-code profile.”
Source brig.sh
Codex CLI OpenAI
Supported
“Built-in codex profile.”
Source brig.sh
Gemini CLI Google
Supported
“Built-in gemini example profile; not tested continuously.”
Source brig.sh
OpenCode opencode
Supported
“Built-in opencode example profile; not tested continuously.”
Source brig.sh

Plausible compatibility 0

Derived, not stored: the product passes SSH access, so any CLI coding agent is installable inside it. This is plausible compatibility, not a supported integration.

No general shell access documented, so nothing is derived. Absence is not unsupported.

06 Compliance & regions Standards held, with ordinal rigor; never a score

Certifications held 0

No attestations found on the public surface. Empty means nothing is advertised, after checking, not that nothing was checked.

Regions —

No region list captured.

07 Open source Apache-2.0 · fetched by machine, not quoted from marketing

Licence & repository

Licence: Apache-2.0OSI
Primary language: Go
Stars: 229
Forks: 21
Created: 12 Aug 2026
Archived: No

Activity

Last commit: 14 Oct 2026
Latest release: v0.4.0 · 6 Oct 2026
Issues open / closed: 172 / 107 · 38% closed

v0.2.0 Sep 15; v0.3.0 Sep 26; v0.4.0 Oct 6. Newer channel-main builds explicitly are not releases.

Fetched via gh on 14 Oct 2026.

Self-hosting

Methods: binarypackage-managersource-build
You operate: hullnerdctlcontainerdurunccosignoras

macOS Apple Silicon or Linux runtime bundle; no managed hosting. Agent-provider subscriptions/API usage separate. Runtime backend determines GUI and policy support. Boot-bundle publisher repository is private and its license unconfirmed in runtime docs. Default egress unrestricted until a policy is attached; writable projects and forwarded credentials remain accessible to guest code.

Documentation signals 7/8

SupportedQuickstart
SupportedAPI reference
SupportedSelf-host guide
SupportedChangelog
Not supportedOpenAPI
Supportedllms.txt
SupportedExamples
SupportedArchitecture doc

08 Company & presence Facts only, not scored

Company

Headquarters: Not disclosed
Founded: —
Team size: Not disclosed
Hiring: Unknown

Activity

Last release: 2026-10-06 github.com
Last blog post: —

Presence 2

Links found on the public surface scanned; not an exhaustive search.

09 Sources & method How this entry was produced

Public surface only

Everything here was read from brig.sh's unauthenticated pages, docs, pricing and repository on 14 Oct 2026. Nothing behind a login was used.

Statuses, not scores

Capabilities are pass, partial or fail against a written rubric (features v21). “Not assessed” means the scan predates the key.

Confidence is separate

Each fact carries its own confidence. Low-confidence facts are shown, never hidden, so you can weigh them.

Schema: scan v5
Features registry: v21
Keys tracked today: 61
Assessed on this entry: 61

Something wrong on this page?

Nearby in the atlas

All Sandbox products →