Cloud computers, instantly.
Persistent, isolated Linux machines in the cloud. Boot in under a second. Fork, share, and run anything.
Learn
What is boxd?
Real Linux machines in the cloud. Persistent, isolated, ready in under a second. SSH in and you have a computer.
ReadHow boxd Works
Your SSH key is your identity. Your terminal is your dashboard. A deep dive into the architecture.
ReadManifesto
- 01
The agent lives inside the machine.
Why every boxd decision — fork, hibernation, persistence, SSH — flows from one architectural bet: the agent lives inside the machine.
- 02
Persistence beats ephemeral.
E2B had the right primitive for 2023. 2026 is different. Why every sandbox provider is racing to ship persistence — and why retrofitting it isn't the same as being built for it.
- 03
A single Rust binary.
Zero external dependencies. No Postgres, no Redis, no Kubernetes. Why the simplicity isn't a gimmick — it's the moat.
Articles
- 01
The cloud for small software.
Bots, scrapers, internal tools and micro-SaaS are idle most of the day, keep state on disk, and have to stay up. Why serverless and a plain VPS both mis-fit, and what does fit.
- 02
Where to actually run your self-hosted apps.
Every self-hosting list tells you what to run, not where. The four real homes compared: a box at home, a VPS, Coolify on a VPS, and managed persistent machines.
- 03
Heroku alternatives for small apps.
Sorted by shape rather than by vendor. When Render, Railway or Fly.io is the right answer, when a plain Linux machine is, and how the current pricing actually compares.
- 04
How to run a Python script 24/7.
Why your laptop, nohup, GitHub Actions cron and serverless all fall over, and the working systemd setup that keeps a scraper or bot running through crashes and reboots.
- 05
Where to run an agent harness in production.
Anthropic and LangChain define what an agent harness is. This piece answers the question they don't: where does the harness actually live in production?
- 06
MCP server hosting: a complete guide.
Where do production MCP servers actually live? The four hosting patterns, what changes when MCP goes to production, and the five properties a remote MCP server host needs.
- 07
Running Anthropic computer use on a remote VM.
Computer use needs a desktop. The hard part isn't the API — it's where the desktop lives. What the workload actually needs from its host, and why most cloud primitives don't ship with a display.
- 08
Self-hosted agent execution for engineering teams.
Where does the agent actually execute? The compliance and engineering dimensions, what the substrate has to provide, and the EU sovereignty angle, honestly.
- 09
The cloud dev environment: a practical guide for 2026.
Why CDE is back in the conversation, the four shapes the category comes in this year, and what changed when AI agents joined the workload.
- 10
boxd vs exe.dev: persistent SSH VMs, compared honestly.
Two products in the same lane: persistent Linux VMs over SSH, batteries included. An honest comparison of the design choices that fall out of the shared thesis.
- 11
boxd vs sprites.dev: two bets on persistent agent compute.
Sprites and boxd agree on the architecture: persistent microVMs are the right primitive for AI agents. Where the two implementations diverge, honestly.
Use cases
Development Environments
Full Linux VMs your whole team can fork and share.
Full Linux VMs with complete isolation. No drift between developers or environments. Fork any machine, share it with a public URL.


Teams are shipping faster with boxdBackground Agents
Agents that work while your team sleeps.
Fork a fully-configured machine per agent. No time limits, real services, parallel exploration. Zero cost when idle.


Agents shipping while teams sleepAgent Sandboxes
Fastest in the category. Full VM isolation.
Run untrusted code safely at scale. KVM isolation, not containers. Every sandbox gets its own kernel. Built for platforms that execute user-generated and AI-generated code.


Platforms run sandboxes on boxdread the docs · boxd new