Cloud dev boxes with Claude Code already on them. Sign in with Google, request a box, open the terminal in your browser — or hand a task to an agent and watch it work.
THE CARET BELOW BLINKS — EVERYTHING ELSE ON THIS SHEET HOLDS STILL
FIG. 0 — ONE WORKSPACE = ONE MACHINE + ONE VOLUMEfree during beta · APPROVAL REQUIRED · no card, no checkout
Specimen 01 · the browser terminalttyd 1.7.7 · tmux · composited for this sheet
$ git clone https://github.com/you/app.git
$ cd app && claude
> fix the failing tests in auth.spec.ts and explain what was wrong
reading auth.spec.ts…
SESSIONS LIVE IN TMUX · THEY SURVIVE THE TABNOTHING TO INSTALL
CHAPTER I · THE SERVICE
A workspace, observed.
Field note — every workspace was recorded to be exactly three things, no more. Where a brochure would enlarge, this sheet counts. Plates 1 and 2 follow.
PLATE 1
WHAT ONE WORKSPACE IS
SERVICE / A · counted: 3
A REAL MACHINE
one dedicated vm plus one persistent volume, created for you at request. your home directory lives on the volume — repos, credentials and claude's own state survive restarts and image updates.
1 / 3
A TERMINAL IN THE BROWSER
ttyd over tmux, opened from the portal or in its own tab. nothing to install; sessions persist when the tab closes and are there when you come back.
2 / 3
AGENTS IN ONE CLICK
pick a runtime, a model, a task and a repo in a short wizard. the run gets its own tmux window; watch it live in the terminal, see its exit recorded in the portal.
3 / 3
each pictogram = one property of every workspace · quantity shown by count of symbols, never by size · after O. Neurath
PLATE 2
SIZES, AS OFFERED
SERVICE / B · presets: 2 + custom
1 AGENT
PRESET 1/2
vCPU
MEM
sized for one claude code session. parks itself when idle; the 10 gb volume persists and it wakes on demand.
2 AGENTS
PRESET 2/2
vCPU
MEM
room for two parallel agents, or one plus a heavier build. stops when idle; starts from the portal in seconds.
CUSTOM
BY REQUEST
vCPU
MEM
up to 8 shared vcpu / 8 gb, drawn in outline because it is granted case by case, not picked from a menu.
each ▪ = 1 shared vcpu · each ● = 1 gb memory · counted, never scaled · no prices appear on this sheet — during the beta there are none
FREE DURING BETA — APPROVAL REQUIRED
CHAPTER II · THE MACHINERY
Drawn from the deployed configuration, not a whiteboard.
Field note — boxes run your code, so they are kept where your code can do no harm: an isolated private network the control plane can dial into and nothing can dial out of. Plates 3 and 4 follow.
PLATE 3
THE ARCHITECTURE
MACHINERY / A · tiers: 3
one machine + one persistent volume per workspace, created when you ask for it
the terminal is ttyd over tmux on the box; the browser reaches it through the control plane over a cookie-authenticated websocket
boxes run your code on their own private network — no public ips, no route back to the control plane or to anyone else's box
git and model tokens are stored aes-256-gcm encrypted and injected only into your own machines
idle boxes park; the volume persists; a parked box wakes from the portal
real architecture, drawn to count — the one-way arrow is the design · everything above runs in the eu (frankfurt) except the cloudflare edge, which is global
PLATE 4
THE AGENT BENCH
MACHINERY / B · counted: 5 · in beta: 2
01
CLAUDE CODE
interactive in the terminal, or headless on a task · your anthropic key or claude subscription token
IN BETA
02
OPENCODE
free openrouter models included in the picker · your own openrouter key
IN BETA
03
CODEX CLI
drawn in outline — planned, not yet on the bench
PLANNED
04
AIDER
drawn in outline — planned, not yet on the bench
PLANNED
05
GEMINI CLI
drawn in outline — planned, not yet on the bench
PLANNED
status is recorded as found: two runtimes ship with the beta; the planned three are drawn in outline and never filled in early · every run uses a key you bring — none is shared
FIELD PERMIT
The beta is open by request.
Sign in with Google, and a person approves the account before your first box. Free while the beta lasts — no card, no checkout, no tier table.