Use casesCoding team
Claude Code is built for one person on one machine. For a team that means one machine per developer, each signed in with that developer's own account. Five providers ship it preinstalled and one sets it up in one click; the catch is how logins are kept.
Short answer: The cheapest machine that runs it as described is Boat at $28.80 a month, then Agent 37 ($33.78) and Lizard ($39.92). 12 of 16 providers run it without a catch. Machine cost only, before any AI model, at list prices checked 29 October 2026.
“Three to five of us want Claude Code running on cloud machines, each with our own login, without sharing one account.”
Claude Code is Anthropic's coding agent. A developer starts it in a repository and asks for a change; it reads and edits files and runs commands and tests on the machine where it runs.
Vercel's guide puts the hosting constraint plainly: Claude Code "isn't built to be safe for multiple tenants: it's a command-line tool for one user, it keeps its state on disk" (Vercel). A shared machine would hold one person's login and mix everyone's unfinished work, so the default is one machine each.
For a team, three things have to be decided together: where each copy runs, whose Claude account pays, and what survives when a machine is replaced. The machine does not need to stay on; it runs while people work.
From its own documentation, each line linked to the page it comes from
Anthropic asks for 4 GB of memory or more and gives no CPU or disk minimum. Its own cloud sessions allow 4 vCPU, 16 GB and 30 GB of disk. 4 vCPU / 8 GiB / 40 GiB per developer covers the agent, tests and a few containers, with room for their images.
No. Each machine runs during working hours: eight hours on 20 days is 160 hours each, or 800 for five developers. It can stop between sessions if its disk survives.
The repository and any work not yet pushed, and the login: on Linux, ~/.claude/.credentials.json. If the disk is thrown away, the developer signs in again and unpushed work is lost.
On Claude's Team plan, "team members install Claude Code and log in with their claude.ai accounts", so each machine holds its owner's login. Some platforms store one Claude login for the whole account, which every sandbox uses: convenient alone, wrong for a team that wants usage and access per person.
Mostly waiting on the model: about 3% CPU on average in Battleships' software-factory workload, with peaks near half the machine during builds and tests.
battleships.dev, built by the Boat team
Easiest first. “Without a terminal” means someone who does not type commands can get it running from the provider's website.
| Provider | How | Without a terminal? | What it involves |
|---|---|---|---|
| Agent 37 | One click | Yes | The agent37-claude-code template sets up one Claude Code instance on the developer's own Anthropic account. One instance each, so five developers means five; team management and roles are on the Max plan.Agent 37: templates ↗ |
| Boat | Preinstalled | Partly | Claude Code is one of seven coding agents on every sandbox. Create one per developer from the dashboard or command line, then run claude.Boat: harnesses and models ↗ |
| boxd | Preinstalled | Partly | Every machine ships with Claude Code, Codex and OpenCode, and the console opens a terminal or desktop. No shared login feature, so each developer signs in on their own machine.boxd: coding agents ↗ |
| InstaBox | Preinstalled | Partly | The default image includes Claude Code, Codex, Docker and a desktop. Open the machine's terminal from the dashboard. No Claude Code guide.InstaBox: limits and images ↗ |
| Lizard | Preinstalled | Partly | A claude template and a guide. But "credentials belong to your Lizard account, not to a project, and every sandbox you start can use them": five machines would still share one Claude login.Lizard: Claude Code ↗ |
| Sandboxer | Preinstalled | Partly | Claude Code is in the preinstalled agent list, Sandboxer publishes a Claude Code guide, and the dashboard has a Terminal tab.Sandboxer: machines ↗ |
| Blaxel | Official guide or template | No | A written tutorial for running Claude Code in a Blaxel sandbox against a codebase, with command-line and code steps.Blaxel: Claude Code ↗ |
| Cloudflare Sandbox | Official guide or template | No | An official guide: a Worker starts a sandbox where Claude Code edits a GitHub repository and returns the changes. Needs Workers and a container deployment.Cloudflare: Claude Code ↗ |
| Daytona | Official guide or template | Partly | An official command-line guide. The dashboard Playground opens a terminal in the browser, so nothing is installed locally, but setup is typed commands.Daytona: Claude Code ↗ |
| E2B | Official guide or template | No | A prebuilt claude template and a guide, made for a fresh sandbox per task started from code rather than each developer's own machine.E2B: Claude Code ↗ |
| Morph | Official guide or template | No | An official example installs Claude Code in a Devbox with Anthropic's installer. Nothing on teams or logins.Morph: Claude Code ↗ |
| Vercel Sandbox | Official guide or template | No | An official guide that gives each Claude Code session its own sandbox, built in code.Vercel: Claude Code ↗ |
| Runtime | By hand | No | A sandbox opens with a shell in the browser and can run it, but there is no Claude Code guide or template.Runtime: getting started ↗ |
| Sprites | By hand | No | Sprites documents Claude Managed Agents, a different Anthropic product, not Claude Code. Installing it in a Sprite is by hand.Sprites: Claude Managed Agents ↗ |
| Modal | Not documented | No | Not documented, and Modal sandboxes have no stopped state that keeps a developer's files. |
Read from each provider's documentation on 29 October 2026. A provider not listed as one click can still be the right home; it means someone has to follow its instructions.
Three starting points for different people, each with its catch
Claude Code preinstalled on a full virtual machine with Docker. Five 4 vCPU / 8 GB machines for 160 hours each come to about $29 of usage: the $20 plan plus about $9 from the wallet.
Catch: A stopped machine's disk is kept for only 14 days, so push work before a holiday. There is no free plan.
Claude Code preinstalled, an official guide, and a Terminal tab in the dashboard. The same five machines come to $40 a month.
Catch: Usage over the $20 plan is bought in $20 packs, and storage counts against an included quota: going over blocks new sandboxes.
One-click Claude Code on each developer's own Anthropic account, so logins stay separate.
Catch: One instance per developer: five Pro instances are about $150 a month, and team roles need the $99.99 Max plan. These plans are separate from the Cloud machines the calculator prices.
Beyond these providers. Anthropic runs Claude Code cloud sessions on its own machines for Claude subscribers, with no separate machine price. Claude Team is $25 per seat a month ($20 billed annually) for 2 to 150 people, with central billing, single sign-on and each member on their own login. Claude Enterprise starts at 20 seats, which is why a team of five starts on Team.
Compare these three head to head: features and cost side by side.
Five 4 vCPU / 8 GiB / 40 GiB machines, one per developer, eight hours a day on 20 working days (800 machine-hours), stopped otherwise with each repository and login kept. About 3% CPU on average. The model line is 20 requests a day per developer at 300,000 tokens each, at API prices; developers who sign in with Claude subscriptions pay per seat instead. Change any number; open a row for the arithmetic.
List prices only, excluding model tokens, egressData the machine sends out to the internet, such as downloads to a user or uploads to another service. Some providers charge per GB; most agents send very little., taxes and anything a provider does not publish. How the numbers are made.
Each page compares every provider, with a source for every row
Built-in agents — Some providers ship the machine with coding agents already installed and a way to prompt them. Others ship a computer and expect you to bring the agent.
Teams and accounts — Organisations, key scopes, spend limits, SSO, audit and residency. The features a team needs are rarely the ones a solo builder notices, and several providers only sell them on an enterprise tier.
Keys and secrets — Three different things are called “secrets”: a value in an environment variable, a file on disk, and a placeholder that a proxy swaps for the real key. Only the third keeps the key away from the agent.
Storage: disk, volumes and what persists — “Persistent” can mean the whole disk, one mounted folder, or fourteen days. It can also mean a separate volume that outlives the machine, which is a different product from the disk the machine boots with.
Lifecycle: stop, pause and sleep — Providers use seven words for four behaviours. The only question that matters is what is still running when the machine comes back.
Sizes, regions and hardware — A size is a bundle of CPU, memory and disk, and the bundle decides what you can run. A region decides how far away it is and whose laws it sits under. Neither is as flexible as the word “cloud” suggests.