Instant remote computers.

Persistent cloud computers that you can fork and share.
Access from any device, collaborate at scale.

Start now Read the docs

or run this →

user@boxd.sh

# Create a machine. That's it.

✓ Machine running at myapp.boxd.sh

# Fork it. Full state, instant clone.

✓ Forked → myapp-debug.boxd.sh

# SSH in. You're home.

✓ Connected to myapp · Ubuntu 24.04 · 2 vCPU · 8 GB

One machine. Two users.

Developers SSH in from anywhere. Agents run autonomously for hours. Both get persistent state, full isolation, and a public URL. The same machine works for both — because it's just a real Linux computer.

Access

Log in from any device

Your machine is always there. SSH in from your laptop, your phone, your tablet. Pick up exactly where you left off. It runs in the background whether you're connected or not.

MacBook Pro

myapp@boxd● connected

$ ssh myapp.boxd.sh

Connected · session a4f8c2

Last login: 2 min ago

myapp@boxd:~$ npm run dev

> Ready on :3000

myapp@boxd:~$

iPhone

myapp@boxd○ ready

$ ssh myapp.boxd.sh

Connected · session a4f8c2

Last login: 2 min ago

myapp@boxd:~$ npm run dev

> Ready on :3000

myapp@boxd:~$

iPad

myapp@boxd○ ready

$ ssh myapp.boxd.sh

Connected · session a4f8c2

Last login: 2 min ago

myapp@boxd:~$ npm run dev

> Ready on :3000

myapp@boxd:~$

Always on

Your agents' home. Always on.

Your machine keeps running after you disconnect. Long builds, background jobs, agent tasks — they all continue. Come back when they're done. No terminal babysitting.

Networking

Instant URLs, zero config

Every machine gets a public URL automatically. HTTPS certificates handled. DNS just works. Spin up as many subdomains as you need. No nginx, no Cloudflare, no fuss.

https://

MacBook Pro

myapp@boxd● connected

$ ssh myapp.boxd.sh

Connected · session a4f8c2

Last login: 2 min ago

myapp@boxd:~$ npm run dev

> Ready on :3000

myapp@boxd:~$

iPhone

myapp@boxd○ ready

$ ssh myapp.boxd.sh

Connected · session a4f8c2

Last login: 2 min ago

myapp@boxd:~$ npm run dev

> Ready on :3000

myapp@boxd:~$

iPad

myapp@boxd○ ready

$ ssh myapp.boxd.sh

Connected · session a4f8c2

Last login: 2 min ago

myapp@boxd:~$ npm run dev

> Ready on :3000

myapp@boxd:~$

Under the hood.
What makes it work.

The infrastructure behind boxd. Custom VMM, real isolation, zero external dependencies.

KVM isolation

Every machine has its own kernel. Not a container. Not a shared namespace. Real hardware-level isolation for untrusted code.

Isolation: KVM · Own kernel

SSH + --json

Every command works programmatically. No SDK to install, no API keys to manage. If it can open an SSH connection, it can control boxd.

$ ssh boxd.sh list --json

Pre-installed

Claude Code, Docker, Python 3, Go, Node, headless Chrome, ffmpeg, git — ready from the first boot. No apt-get ceremony.

claude, docker, python3, go ...

Scale to zero

Machines sleep when idle. You pay nothing while they're off. Resume in under a millisecond. No more forgetting to shut things down.

sleeping — $0/hr

Self-hostable

Run boxd on your own infrastructure. Any cloud, any KVM-capable server. European hosting by default. No vendor lock-in.

deploy · any KVM host

Ubuntu 24.04

Full unminimized Ubuntu with man pages, systemd, and everything you expect. Not an Alpine shell. A real Linux machine.

2 vCPU · 8 GB · 25 GB disk

Your agent gets a real machine.
Not a sandbox. Not a container.

Persistent across sessions

Your agent stops at 2am. Picks up at 9am. Files, packages, databases — everything is still there. No rebuilding context. No re-installing.

myapp@boxd

▸node server.js

▸postgresql:5432

◆142 files, 4.2 GB

◆12 env vars loaded

Full isolation

Every machine runs its own kernel. Not a shared namespace, not a container boundary. Real KVM isolation for untrusted agent-generated code.

<60ms fork time

Fork to explore. Agent branches the machine to try four approaches in parallel. Keep the winner, discard the rest.

mainsource

PR #42queued

PR #43queued

PR #44queued

PR #45queued

4/4 passed in parallel

Start now Read the docs

We own the whole stack.

Custom Rust VMM built on KVM. Not Firecracker. Not Docker. Zero external dependencies — everything is built into our solution. Self-host anywhere KVM runs.

Custom VMM

Rust + KVM

External dependencies

Everything built in

Schedulers

Raft consensus

∞

Self-host targets

Any KVM host

	boxd	E2B	Daytona	Modal
Cold boot	<200ms	~150ms	~27ms	~200ms
Resume	<1ms	—	—	—
Persistent state	Yes	No	Yes	No
Isolation	KVM	Firecracker	Container	gVisor
Own VMM	Yes	No	No	No
Self-hostable	Yes	No	Yes	No
Interface	SSH	SDK	CLI + SDK	SDK

Read the docs

A machine in seconds.
A home for agents.

Persistent, isolated, SSH-accessible. The simplest way to give developers and agents their own Linux machine.

Start now Read the docs

Instant remote computers.

One machine. Two users.

Log in from any device

Your agents' home. Always on.

Instant URLs, zero config

Under the hood.What makes it work.

KVM isolation

SSH + --json

Pre-installed

Scale to zero

Self-hostable

Ubuntu 24.04

Your agent gets a real machine. Not a sandbox. Not a container.

Persistent across sessions

Full isolation

<60ms fork time

We own the whole stack.

A machine in seconds.A home for agents.

Under the hood.
What makes it work.

Your agent gets a real machine.
Not a sandbox. Not a container.

A machine in seconds.
A home for agents.