Your Compute
One Compute per account: a shared CPU/RAM budget, one persistent disk for projects and home, and a fresh Linux environment for each terminal.
Every terminal starts with a fresh Linux environment, Docker and sudo. Closing the browser leaves it running. End the terminal to remove its environment; your projects and home folder stay.
Sizes
| Plan | vCPU | RAM | Disk | Network | Terminals at once | Price a month |
|---|---|---|---|---|---|---|
| Start | 2 | 4 GB | 50 GB | 50 Mbit | 3 | $19 |
| Pro | 4 | 8 GB | 100 GB | 100 Mbit | 5 | $35 |
| Max | 8 | 16 GB | 200 GB | 200 Mbit | 8 | $59 |
| Business | 8 | 16 GB | 300 GB | 300 Mbit | 10 | $149 |
| Business Plus | 16 | 32 GB | 600 GB | 500 Mbit | 15 | $299 |
The plan sets three things every terminal shares: the CPU and memory they all draw on, the account disk that holds your projects and home folder, and how many terminals run at once. Business plans add priority support and invoices to your company; Billing covers both.
Get your Compute
Open Compute, choose your plan and name, then continue to Stripe Checkout. Pay and return to the dashboard. Your account has one Compute and no terminals yet; create a project and launch an agent in it, or open a Shell.

Find your way around
The Compute page shows your plan and its price, the terminals running against your size's limit with a link to them, live Resources (CPU, memory, disk, processes and network, refreshed every 5 seconds), and Billing with the next billing date, Manage subscription and Delete Compute.

Start a terminal
Open Terminals and choose New terminal. Pick the project, the agent and what it runs on and choose Launch, create a project or open a Shell. Every choice starts a fresh environment; choose an existing terminal to return to a running job.
A terminal keeps running until you end it. Close the browser, the laptop or the phone, and its processes, tmux session and containers carry on. End terminal removes its environment and frees its slot for the next one.
With no live terminals, no terminal containers run. Your account disk and Compute subscription stay. Open a terminal to start a fresh environment on your saved data.
Change size
Open Compute and pick the new size. Review the price and when it applies, then confirm. An upgrade applies now; a smaller size applies next period if your saved data fits it at full size.
How your disk is counted
Your disk holds your files at full size, the sizes ls -l shows: 50 GB on Start is 50 GB of your projects and home folder, byte for byte. Resources on the Compute page shows how much of it you use.
When your files reach your size, new writes stop. The Compute page shows the disk full, and an email tells you. Delete what you no longer need, or change to a bigger size: writes pick up at once, and a bigger size lands with no restart.
Inside a terminal, plain du -sh and df count blocks after compression and show less than your files take. Count a folder the way your size does with --apparent-size:
du -sh --apparent-size ~/* /work/* | sort -h
What stays for your next run
- Stays on the account disk: every project under
/workwith its code, the settings of its launches and the agent sessions they share, and your home folder/home/devwith your shell setup, git keys and the tools you install there. - Ends with its terminal: apt packages, system services, cron jobs, running processes, Docker images, containers, volumes and build cache, and the terminal's previews and shared links.
Delete
Deleting Compute ends its terminals, cancels the subscription and erases the account disk, every project and home folder included. Copy the data you want to keep before confirming.
Limits
| Limit | Value |
|---|---|
| Compute per account | 1, sized by your plan |
| Terminals at once | 3 on Start, 5 on Pro, 8 on Max, 10 on Business, 15 on Business Plus |
| Projects | As many as your disk holds, at $0 |
| Public preview ports | 20 |
| Live share links | 50 |
| Processes | 4,000 |
| Open support requests | 20 |
Need more power than Business Plus? Enterprise sets up a node for your team.
Planned node reboots
A node reboot interrupts terminal processes and tmux sessions. Your account disk keeps the projects and home folder. Open the project with any of its launches and the agent continues the project's latest session.
Where it runs
Your Compute runs in Kazakhstan, on our own hardware. Each terminal is an unprivileged system container with Docker running inside, and your account disk mounts only into your own terminals. Private networks and outbound mail on port 25 are blocked; the internet runs at your plan's speed. Details on /security.
See what happened
Activity in the sidebar lists every plan change, project, saved launch, public port and shared file link on your account, with exact times.