Compute → Fast workspace

Containers

Open Compute, choose Fast workspace, set a name and pick a system. The system is chosen when you create it. Free accounts have no container; every paid plan includes one.

Life of a workspaceA workspace is created from the Compute page, runs, and can be paused, snapshotted, rebuilt or deleted. Pausing moves the files to network storage and frees cores and RAM; starting brings them back. A plan downgrade pauses workspaces that no longer fit instead of deleting them.PauseStartSnapshotRestoreRebuildDelete1. CreateCompute, Fast workspacename and system2. Runningfiles persistchats attachPausedby you, or over quotaafter a plan downgradefiles on network storagecores and RAM freedSnapshotsaved stateof the filesRebuildsnapshot firstruntime reset/work is keptDeletedyou type the nameto confirm
A workspace moves between running and paused; pausing keeps the files and frees the cores and RAM.
Diagram as text
  1. Create a workspace from Compute with Fast workspace: give it a name and pick a system.
  2. While it runs, files persist across restarts and chats, and chats can attach to it.
  3. Pause moves the workspace to network storage and frees its cores and RAM. Start brings it back.
  4. If a plan downgrade leaves you over quota, the workspaces that no longer fit are paused, never deleted.
  5. A snapshot saves the state of the files; restore returns to it.
  6. Rebuild resets the runtime to the base image and keeps /work. A snapshot is taken first.
  7. Delete removes the workspace; you type its name to confirm.
System
  • Ubuntu 24.04 with ZeroLog toolchain
  • Ubuntu 24.04, plain
  • Debian 12 slim, Node.js 22
  • Alpine 3.20
  • Alpine, Python 3.12

Windows is not a container. It runs as a virtual machine. Available systems and resource limits depend on your plan.

Build in your workspace

  • apt install
  • Compile
  • Run a database
  • Start a service

Install packages, compile code, run a database or start a service inside your workspace.

Your isolated workspace

It outlives the chat

Files persist across restarts and across chats. The container is the durable thing; a chat is not.

Attach a container to a chat so the AI works there. Attach the same container to several chats and they share one filesystem.

Chat Chat Chat Restart One filesystem
Chats attach and end above it, the restart passes behind it, and the files stay where they are.

A sketch of the relationship, not a timeline.

Open in editor

Press Open in editor in the container overview or in the chat context bar. ZeroLog starts VS Code in your browser, which takes about 8 seconds, and opens it in a new tab.

The editor comes with Mini and higher. On Free the app points you to the plans.

Pause when idle

Pause a workspace while it is idle. Start it again when you need it.

KeptYour files, on network storage
FreedThe cores and RAM

Snapshots

Save a known-good state before a risky change. Mini keeps 1 snapshot, Pro 2, Max 3, and Ultra up to 20 with daily automatic ones.

Known-good state

The risky change

Resize, rebuild, export

Under Advanced you can change cores, RAM and disk within your plan. Rebuild resets the runtime to the base image and keeps your code in /work; a snapshot is taken first and packages installed outside /work are lost. Export produces a ZIP with a Dockerfile, a compose file and your source.

What a plan gives one container

Mini 1 vCPU, 4 GB RAM, 10 GB disk. Pro 2 vCPU, 8 GB, 15 GB. Max 4 vCPU, 12 GB, 25 GB. Ultra runs up to three containers that share 12 vCPU, 48 GB RAM and 150 GB disk. If a plan change leaves you over quota, the workspaces that no longer fit are paused, never deleted.

What each plan includes, with current prices: Pricing.