ZeroLog
Private preview

Isolation

Your workspace is its own container, not shared with any other user.

Isometric drawing of a glass cabinet inside a steel cabinet. Coins roll along a belt from a terminal to a gatehouse. Refused coins roll back, answered coins stay inside, and a few small coins leave through a narrow slot in the steel wall to the host machine.
Click or press Enter to send a calldemo tape: 24 calls · 4 refused · 20 answered inside · 5 reached the host
Each coin is one system call from your workspace. The gatehouse is gVisor's Sentry: it answers the call or refuses it. Only a few calls reach the host, through a narrow slot in the steel wall. The 24-call tape is a demo, not live traffic.
Figure as text
  1. Your workspace sits in a glass cabinet. The glass cabinet stands inside a steel cabinet that fences in the host process.
  2. 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.
  3. 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.
  4. The Sentry answers every other call itself. Most never leave the gatehouse.
  5. 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.
  6. 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.
Where a workspace runs and how traffic leaves itYour browser talks to the app server. The app server asks a filtered container API to start your workspace on a worker machine, either as a gVisor container or, on the Ultra plan, inside a Kata micro-VM. A workspace sits on an internal network with a single exit: the egress broker, which applies target and port rules. Calls that need a stored third-party key go on to a separate key service.Key service (separate VM)Worker machines, one workspace eachClass: vm (Ultra plan)Class: standardcreate, stoponly way outonly way outallowed targetshosts with a key profilereal key insertedstart, stopBrowser, CLI or appApp server (control plane)sign-in, chats, approvalsFiltered container APIno Docker socketin workspacesYour workspacegVisor user-space kernelall capabilities droppedinternal network onlyYour workspaceKata micro-VMown guest kernelinternal network onlyEgress brokerruns inside the app processtarget and port rulesPublic internetThird-party keys, encryptedmutual TLS from app host onlyThird-party APIs
A workspace has no network path to other workspaces; its only way out is the egress broker.
Diagram as text
  1. You reach the app server from the browser, the CLI or the app.
  2. The app server starts and stops workspaces only through a filtered container API; workspaces get no Docker socket.
  3. Standard class: the workspace is a container under gVisor, a user-space kernel, with all capabilities dropped, on an internal network.
  4. VM class (Ultra plan): the workspace runs in a Kata micro-VM with its own guest kernel.
  5. In both classes the only way out is the egress broker, which runs inside the app process and applies target and port rules.
  6. The broker passes allowed traffic to the public internet.
  7. 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.

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