three machines · three kernels · one host
Kernel-level isolation
Every agent runs in its own KVM microVM with its own kernel. A crash or an exploit stays in that machine.
Self-hosting
Run boxd on your own infrastructure.
The same machines, CLI, SDKs and console as boxd cloud, in your own AWS or Google Cloud account, or on any KVM host. Free up to 16 vCPUs.
Runs on
- AWSAutomated
- GCPAutomated
- HetznerSoon
- AzureSoon
- Any other KVM hostManual deployment
Free tier
16 vCPUs
Free, with no licence key and no sign-up.
- Simple to configure
- One config file, cluster.toml, for the whole cluster
- 20 to 40 min
- Apply builds the cluster, unattended
- Your tools
- Optional Composio integrations, with your own API key
Install
From clone to first machinein about an hour.
- 01
Clone and sign in
Clone the repo and sign in to Google Cloud or AWS through the installer. Docker is the only thing to install.
- 02
Write cluster.toml
Copy the example and fill in the name, DNS zone, project and region. Validate checks the file.
- 03
Apply it
20 to 40 minutes, unattended. It downloads a signed release bundle and builds the cluster.
- 04
Delegate DNS and sign in
Add the DNS records apply prints, sign in, and install the CLI your cluster serves.
Security
Agents run untrusted code.Each one in its own machine.
Every control below is enforced on the host, outside the machine, and works the same on boxd cloud, BYOC and self-hosted clusters.
listed hosts pass · everything else is dropped
Egress
Allow outbound traffic per machine by domain or IP range. The host enforces it, so the agent can't change it.
placeholder inside · real key outside
Secrets
The machine only sees a placeholder. The real value is added on the way out, to the domains you choose.
tagged machines share a network
Networks
Choose which machines in your org can reach each other. Everything else stays apart.
DPA · SOC 2 · ISO 27001
Compliance
DPA available today. SOC 2 Type II and ISO 27001 are in progress.
Free to start. A licence when you grow.
Free
Up to 16 worker vCPUs
- The full product, same release as boxd cloud
- No licence key, no sign-up
- Telemetry stays on: one hourly report, counts only
Licence
Sized to your cluster
- No vCPU limit
- Telemetry opt-out
- Support from the engineers who build it
- BYOC and air-gapped installs on request
FAQ
About self-hosting
Yes, up to 16 worker vCPUs: the logical CPUs of your worker hosts, added up. You don't need a licence key or an account. A cluster over the limit keeps its machines running but won't start new ones until it's back under, or has a key.
Docker on the machine you install from, a Google Cloud project or AWS account, and a DNS zone you can delegate. Workers need nested virtualization: N2 on Google Cloud, C/M/R 7i or 8i or any .metal type on AWS. Without a key, the installer picks a 16-vCPU worker for you.
Yes. Forking, snapshots, resume, per-machine HTTPS and SSH, the console, the CLI and the SDKs. A self-hosted cluster runs the same release as boxd cloud, from a signed bundle the installer verifies before it unpacks anything.
One usage report an hour, with counts only: no names, emails, machine names, zone or IP addresses. On the free tier it's always on. A licence key with telemetry opt-out lets you switch it off.
Follow the latest release, or pin the cluster to an exact version. Running apply again rolls the upgrade out, and services restart only where something changed.
Yes. With BYOC we operate the cluster inside your own cloud account. The machines and the data stay in your account. We can also help with air-gapped installs. Talk to us about either.
Self-host boxd for free.
Up to 16 vCPUs, no licence key. Clone the repo, write cluster.toml and run apply.