Skip to main content
A sandbox is a KVM microVM started from a template. It has its own Linux kernel, a writable root filesystem, and its own network policy. Inside it, E2B’s envd daemon serves commands, files and terminals on port 49983; the SDKs and the CLI talk to it through the Anona gateway.

Metadata and listing

Attach string metadata at create time, then filter on it when you list:
Metadata keys starting with anona. are reserved and refused, and so are the keys the sandbox engine uses itself, such as host-mount and anything starting with cube. or io.kubernetes., in any letter case. The 400 names the key.

Names

A sandbox can carry a human name: the name metadata key. Set it with metadata={"name": "nightly-eval"}, anona-compute create --name nightly-eval or the Name field of New sandbox; the dashboard and anona-compute list show it beside the ID, and anona-compute list --name nightly-eval (or the metadata filter) finds it. Change it later with anona-compute rename or PUT /v1/sandboxes/{id}/name, which take 1 to 64 letters, digits, spaces, dots, dashes or underscores. The sandbox ID stays the identifier: every API call and command still takes the ID.

Connect from anywhere

A sandbox outlives the process that created it. Any process holding an API key of the same organization can reconnect by ID:
Another organization’s sandbox answers “not found”, exactly like a sandbox that does not exist.