Isolation
Your workspace is its own container, not shared with any other user.
Figure as text
- Your workspace sits in a glass cabinet. The glass cabinet stands inside a steel cabinet that fences in the host process.
- Every system call from the workspace rolls along the belt to the Sentry, gVisor's user-space kernel. No call goes straight to the host kernel.
- The Sentry refuses calls a development environment does not need, such as keyctl, bpf, syslog and userfaultfd. The portcullis drops and the call rolls back with an error.
- The Sentry answers every other call itself. Most never leave the gatehouse.
- When a call needs the host, for example to open a file, the Sentry makes one small call of its own. It passes through a narrow slot in the steel wall to the host machine.
- Three gauges count refused calls, calls answered inside, and calls that reached the host. On the 24-call demo tape that is 4 refused, 20 answered inside, and 5 of those that reached the host.
Diagram as text
- You reach the app server from the browser, the CLI or the app.
- The app server starts and stops workspaces only through a filtered container API; workspaces get no Docker socket.
- Standard class: the workspace is a container under gVisor, a user-space kernel, with all capabilities dropped, on an internal network.
- VM class (Ultra plan): the workspace runs in a Kata micro-VM with its own guest kernel.
- In both classes the only way out is the egress broker, which runs inside the app process and applies target and port rules.
- The broker passes allowed traffic to the public internet.
- For hosts that have a key profile, the broker hands the request to the key service, a separate VM reached over mutual TLS from the app host only. The key service inserts the real key on the way to the third-party API.
-
Your own workspace
Nobody else's workspace can read your files, see your processes or reach your running services.
-
An extra layer under the container
ZeroLog runs workspaces on gVisor, a userspace kernel: your workspace's system calls are handled without reaching the host kernel directly. A machine without gVisor does not start workspaces at all.
-
No shared processor cores
The machines that run workspaces never execute at the same moment as other machines on the two halves of one physical processor core, and identical memory pages are not merged with other machines. Both close known ways for one machine to observe another through shared hardware.
-
The layer under your workspace is itself fenced in
The host process that runs your workspace cannot read ZeroLog's own keys, database or configuration, cannot reach the container engine, and cannot change the rules that fence it in. If that layer were ever broken out of, the next wall is already standing.
-
No path between workspaces
Workspaces cannot reach each other over the network, even when they run on the same machine.
-
Outbound traffic is filtered
A workspace's own internet access goes through ZeroLog's network protections; see Outbound network.
Choose a stronger class for risky code
When you create a container you can pick its isolation class. Standard runs the workspace on gVisor with an extra system call filter that blocks interfaces a development environment does not need. VM gives the workspace its own small virtual machine with its own kernel, inside which it runs; use it for untrusted code. A VM workspace starts a few seconds slower and cannot be switched back later.
The VM class is part of the Ultra plan. Mini, Pro and Max run the standard class, and Free has no workspace. See Plans and Pricing.
Previews cannot reach your account
Websites, apps and designs you preview run sealed off from ZeroLog itself: they cannot read your session, your chats or anything else in your account, even when they come from code the AI wrote.
What this does not change
Commands still wait for you
Isolation keeps workspaces apart from each other, not from you. A command the AI wants to run still waits for your approval first — see Command approval.
Secrets go through the vault
Credentials you attach are handled by the vault, not pasted in the clear — see Secrets vault.
Pausing keeps the disk
Pausing a workspace frees its running slot; it does not delete anything. A paused workspace's disk stays until you delete it yourself.
Credentials for agents: API key proxy for AI agents.
Something missing or wrong here? Say so. The documentation is part of the product, not an afterthought. All topics · Security · Status · X · Legal & privacy · Home