https://name.boxd.sh. Boots in ~30ms.
How it works
boxd machine new boots a KVM microVM with a 100 GB disk and a proxy mapping https://name.boxd.sh → port 8000 (TLS, HTTP→HTTPS, WebSockets — handled). Real unminimized Ubuntu; you land as boxd with passwordless sudo.
Use it
- CLI
- TypeScript
- Python
--json for a parseable response, useful in scripts:boxd machine new auto-syncs the myapp.boxd alias into ~/.ssh/config. Skip the name and boxd generates one like blue-river.
What’s already installed
Each box ships with a developer-ready Ubuntu 24.04:- Languages: Python 3 (with
uv,pipx), Go,build-essential, Node.js 24 via nvm - Agents: Claude Code (
claude), Codex (codex), pre-wired withAGENTS.mdcontext - Containers: Docker, Docker Compose, Buildx
- Web: nginx pre-installed on port 8000 (start it when you want it), headless Chrome
- Tools:
git,gh,jq,ripgrep,sqlite3,rsync,ffmpeg, ImageMagick,mitmproxy - Editors: vim, neovim, plus full SSH for Cursor/VS Code/Zed/JetBrains
Custom images
Every box boots fromcomputer:latest, a curated Ubuntu 24.04 image we maintain. The same image is kept warm across the fleet, which is how fresh boots stay around ~30ms.
Need something different? A different base distro, your own pre-installed toolchain, a specific CUDA stack, a slimmer surface area? Email contact@boxd.sh with what you want baked in. We package it and keep it warm across the fleet, so your boxes boot from your image with the same sub-second cold start as the default.
Recipes
Serve something instantly
name.boxd.sh to port 8000. Any HTTP server on 8000 is live.
Change the default port
--port=auto to let boxd detect whichever port your app started listening on.
Stop paying when idle
Boxes auto-hibernate after 4 hours of network idle by default — snapshot to disk, effectively free to keep, ~85ms wake on the next request. For tighter idle windows, enable auto-suspend: sub-millisecond resume.FAQ
How is this different from a container?
How is this different from a container?
Each box is a full KVM microVM with its own kernel, network stack, persistent disk, and public HTTPS domain.
systemd runs as PID 1, Docker works without nesting tricks, and the filesystem survives reboots.What happens to data when I reboot?
What happens to data when I reboot?
The 100 GB disk persists across reboots, suspends, and resumes. Only
boxd machine remove removes it.Where is the infrastructure?
Where is the infrastructure?
EU-hosted on sovereign infrastructure.
Next
Fork from a golden
Skip the install step. Warm copies of your app in ~160ms.
Live demos & share URLs
Every box has a real HTTPS URL the moment a port is open.