Spawn.
One POST. You get a sandbox with persistent state, full Linux, full root,
no 15-minute timeouts. Deploy your agent on it.
A sandbox for every background agent you ship. Spawn one with a curl, your code runs.
Same sandbox. Persistent or ephemeral.
Have questions? Book a call →
# spawn a sandbox $ curl -X POST https://api.orbcloud.dev/v1/computers \ -H "Authorization: Bearer $ORB_KEY" \ -d '{"name":"my-agent","runtime_mb":1024}'
Deploy [your agent name] on ORB. Docs: https://docs.orbcloud.dev/llm.txtpaste in Claude Code, Cursor, Codex — any agent
Ephemeral when you want it gone. Stateful when you want it to persist. Both, in the same API.
One POST. You get a sandbox with persistent state, full Linux, full root,
no 15-minute timeouts. Deploy your agent on it.
Run for hours, days, weeks. Memory, files, env, LLM context, all survive restarts, redeploys, and crashes. State is the default.
Idle sandboxes snapshot to NVMe. Wake on the next event in ~0.6s, same
memory, same files, same context. Or DELETE when done.
Same primitives, one sandbox or many. Read the docs →
No tiers, no add-ons, no upsells. Same spec on every Orb sandbox.
Ubuntu 24.04 LTS · kernel 6.8 · full root{id}.orbcloud.dev127.0.0.1:8080 · forwards to your provider · buffers across sleep/wakepython 3.12 · node 22 · bun 1.2 · git · curl · jq · tmux · vim · gccSame primitives, same proxy, same metal. The plan just sets the ceiling.
Live case studies first. Generic patterns below.
Swarm of Codex shards reviewing a repo on a cron. Each replica sleeps between runs, paid only when reviewing.
LIVEAlways-on PR reviewer. Sleeps on LLM waits, resumes mid-diff when the response lands.
LIVEOvernight literature sweep, protein-structure runs. Computers alive for days.
LIVECycles NASA TESS target stars, scoring candidate signals between sleeps. Computers alive for weeks.
Claude Code, Codex, Aider. Give each their own computer. Deploy hundreds in parallel.
CrewAI, LangChain, Composio pipelines. Each gets its own isolated computer.
Overnight crawling, summarization, analysis. Computers run 24/7 for pennies.
Playwright, browser-use at scale. Dedicated IP per computer.
Multi-day campaigns. Agents that personalize, track, and follow up over days.
Multi-turn customer support with persistent memory. Resume the same thread weeks later, context intact.
DELETE /v1/computers/$ID when done. Fire-and-forget works fine. You only pay for what ran.Solo or small team? Sign in with GitHub and start. Bigger team, custom needs, or want to talk first? Drop your email below.