Your Compute
Your Compute is where your agents keep working after you shut the laptop. One Compute runs every project you have. It holds a CPU and memory budget every terminal shares, one persistent disk for your projects and home folders, and a fresh Linux environment for each terminal.
Every terminal comes up with Docker, sudo, and Claude Code, Codex and OpenCode ready to run. Closing the browser leaves it running, so the night's work goes on without you. A terminal with no agent in it and nobody on it for 3 hours ends by itself and frees its slot. End a terminal and its environment goes; your projects and their home folders stay.
Sizes
| Plan | vCPU | RAM | Disk | Network | Terminals at once | Price a month |
|---|---|---|---|---|---|---|
| Start | 2 | 4 GB | 50 GB | 50 Mbit | 3 | $39 |
| Pro | 4 | 8 GB | 100 GB | 100 Mbit | 5 | $75 |
| Max | 8 | 16 GB | 200 GB | 200 Mbit | 8 | $169 |
| Business | 8 | 24 GB | 200 GB | 300 Mbit | 10 | $349 |
| Business Plus | 16 | 64 GB | 400 GB | 500 Mbit | 15 | $649 |
| Business Max | 24 | 128 GB | 500 GB | 1,000 Mbit | 20 | $985 |
| Business Ultra | 30 | 192 GB | 1,000 GB | 1,000 Mbit | 30 | $2,900 |
Your plan sets three things for all your terminals together: the CPU and memory they share, the account disk that holds your projects and home folders, and how many terminals run at once. The network speed applies to each terminal. Business plans add priority support and invoices made out to your company; Billing covers both.
Get your Compute
Open Compute, choose your plan and name, then continue to Stripe Checkout. Pay, and you land back in the dashboard with your Compute and no terminals yet. Create a project and put an agent to work in it, or open a shell.

Find your way around
The Compute page shows your plan and price, with Change plan to pick another size. It also counts the terminals running against your plan's limit, such as 3 of 5 terminals, with New terminal and View terminals beside the count. Live Resources cover CPU, memory, disk, processes and network, refreshed every 5 seconds. Billing shows the next billing date, with Cancel subscription and Delete Compute. Press C on any page to get here.

The resource meter in the top bar of every page shows the same CPU, memory and disk at a glance: CPU, memory and disk covers it, along with clearing caches and a full disk.
Start a terminal
Open Terminals and choose New terminal. Pick the project, the agent and what it runs on, then choose Launch; the same dialog creates a project or opens a shell. Every new terminal is a fresh environment, and a running job is one click away in the list.
A terminal whose agent runs keeps going until you end it. Close the browser, the laptop or the phone: its processes, tmux session and containers carry on, and the work is further along when you look again. End terminal removes its environment and frees its slot for the next one.
With no live terminals, no terminal containers run, but your account disk and Compute subscription stay: open a terminal and a fresh environment comes up on top of your saved data.
Change size
Open Compute and pick Change plan. Check the price and when it applies, then confirm. A bigger size applies at once, with no restart: running terminals keep working. A smaller size applies from the next period, if your saved data fits it at full size.
Until then the page names the plan that starts at the next billing period, with Keep current plan to call the change off.
Add a Compute
One Compute runs every project you have, and a new project on it costs $0. When a heavy project deserves its own CPU, memory and disk, give it a separate Compute: an account holds up to five Computes.
On the Compute page, pick Add a Compute, choose a plan and pay in Stripe Checkout. Each Compute is its own subscription at its plan's price; Billing covers what a second one costs.
Every project lives on the Compute you create it on and stays there. To work on it from another Compute, push it and clone it there. Deleting a Compute erases its own projects; your other Computes run on as before.
Your disk
Your disk counts your files at full size, the sizes ls -l shows. When it fills up, new writes stop until you free space or take a bigger size. CPU, memory and disk shows how to count a folder the same way and what to clear.
What stays for your next run
Your account disk keeps every project under /work: its code, the settings of its launches and the agent sessions they share. It also keeps each project's home folder, which that project's terminals see at /home/dev, so the shell setup, git keys, logins and tools you put there are waiting next time. Your shell terminals have a separate home folder of their own. One project's logins and configs never show up in another project's terminals.
Ending or restarting a terminal removes its system: apt packages, system services, cron jobs, running processes, Docker images, containers, volumes and build cache.
Ending the terminal also removes its preview addresses and shared file links. Restarting keeps those addresses and links; start the server again after it. For a link to work after restart, create it for a file in the project or the terminal’s home folder; pasted images and uploaded files are removed on restart.
Delete
Deleting a Compute ends its terminals and cancels its subscription. It also erases its disk with every project and home folder on it. Copy what you want to keep first, then pick Delete Compute and type delete to confirm.
Limits
| Limit | Value |
|---|---|
| Computes per account | Up to 5 of your own, each sized by its plan |
| Terminals at once | 3 on Start, 5 on Pro, 8 on Max, 10 on Business, 15 on Business Plus, 20 on Business Max, 30 on Business Ultra |
| Projects | As many as your disk holds, at $0 |
| Public preview ports | 20 per terminal |
| Live share links | 50 per terminal |
| Processes | 32,768 per terminal |
| Open support requests | 20 |
Need more power than Business Ultra? Enterprise sets up a node for your team, or puts your Compute on your own server.
Planned node reboots
Before planned maintenance on the node that runs your Compute, an email tells you when it starts. A node reboot stops running processes and tmux sessions. Your terminals come back by themselves with their apt packages, Docker images, volumes and uploads in place, and Docker containers with a restart: policy start again on their own. Each agent comes back on its last conversation by itself and waits for your next word. If an agent is not back, Restart terminal on this conversation starts it on that conversation again, in a fresh system.
Where it runs
Your Compute runs on our servers around the world, and more regions are connected on request. Each terminal is an unprivileged system container with Docker running inside, and your account disk mounts only into your own terminals. Private networks, our servers, other customers and outbound mail on port 25 are blocked; each terminal reaches the internet at your plan's speed. Details on /security.
See what happened
Activity in the sidebar tells you what happened while you were away: every plan change, terminal, project, launch, public port, file link, rotation move and sign-in on your account, with the exact time and who made each change. Activity log lists what it covers.