What a machine can do
Each machine is an Ubuntu container in its own small VM, with up to 4 vCPU, 12 GiB of memory and a 20 GB disk. A Durable Object for each machine starts it, stops it and connects you to it.
- Shell
Connect over SSH, copy files with scp or rsync, and open the machine in your editor. The connection runs through your own account, not a public IP.
cloudex ssh cx-7f3a- In v0.1
- Preview links
Turn any port into an HTTPS link on a domain you own. Each link carries a secret token, so only people you share it with can open it.
cloudex host 3000- In v0.1
- Agents
Give Claude Code or Codex a task and watch it work, then reattach from any terminal. Or drive them from the SDKs: follow their events, send follow-ups, steer.
cloudex prompt "make the tests pass"- In v0.1
- Stop and resume
Stopping saves the disk, backs up your home directory to R2 and stops the bill. Resuming brings back your files, packages and agent history.
cloudex stop cx-7f3a- In v0.1
- Docker
Run containers inside the machine. They share the machine's network.
docker run --network host postgres- In v0.1
- Forks
Copy a machine and its disk to try several approaches at once.
cloudex fork cx-7f3a --count 3- In v0.1.5
- Desktop and browser
A Linux desktop with Chrome in your browser, for agents that need to see a page. Share it with a link, or keep it to your own computer.
cloudex desktop- In v0.1.2
- Keys stay outside
Model API keys are added to requests as they leave the machine, so the machine never stores them and a fork can't leak them.
cloudex keys set anthropic- In v0.1.7
- Your own hardware
Run machines on a Linux server or VPS of your own, with no 6-hour limit and as much CPU and memory as it has, under the same CLI and dashboard, with ssh straight to it from your own network or tailnet. You pay for the server, not container time.
cloudex new --on box- In v0.2.2
From install to a running machine
About three minutes on a fresh account, most of it in cloudex deploy.
Install the CLI
One binary for macOS, Linux and Windows.
curl -fsSL https://cloudex.build/install | sh Deploy to your account
Sets up a Worker, a Durable Object and container per machine, and a D1 database in your Cloudflare account. Needs the $5 Workers Paid plan.
cloudex deployStart a machine
A fresh Ubuntu machine with Node, Python, Docker, git, Claude Code, Codex and OpenCode.
cloudex new && cloudex sshStop it when you’re done
The disk is saved in your account and billing stops until you resume.
cloudex stop
Everything runs in your account
cloudex deploy sets up these pieces in your Cloudflare account. Your code, your keys and your bill stay with you.
There are no Cloudex servers and no Cloudex account. cloudex.build hosts this site, the installers and the docs.
Your Cloudflare account
You pay Cloudflare, not us
Cloudex is free. Cloudflare bills your account for the $5 Workers Paid plan and for the time your machines are awake. The $20 Pro plan isn’t needed. Machines on a server of your own cost you the server instead of container time.
Your Cloudflare bill
$7.79 a month
- Workers Paid plan
- $5.00
- Container memory
- $1.93
- Container CPU
- $0.70
- Container disk
- $0.15
- Saved disks (R2)
- $0.00
Uses Cloudflare's published rates on 28 October 2026, after the free allowances that come with the plan. Stopped machines cost nothing except their saved disks. Check the Containers pricing page before you rely on it.
What it can’t do
Cloudflare containers aren’t full virtual machines. If you need any of these today, a hosted VM service such as boat.dev or Fly.io is a better fit. Machines on a Linux server of your own have no 6-hour limit and can be bigger, but no forks or backups yet.
- No public IP addressReach a machine through cloudex ssh, with port forwarding, or preview links.
- Up to 4 vCPU and 12 GiBWith a 20 GB disk that includes the system image. No GPUs.
- Big disks resume slowerA machine with 15 GB of files can take about two minutes to come back.
- Docker on the host networkContainers can’t use bridge networks, and rootless Docker doesn’t start.
- Saved disks last 30 days unusedAfter that, resume restores your home directory from its R2 backup onto a fresh machine. Packages installed elsewhere need installing again.
Where it’s at
Version 0.2 is out. Follow along on GitHub.
- v0.0
Measuring
DoneTesting resume times, SSH over WebSockets, Docker and the desktop on real containers before writing product code.
- v0.1
A machine of your own
DoneThe CLI, cloudex deploy into your own account with nothing else to install, machines, the shell, preview links, agent sessions, stop and resume, backups to R2, the desktop, forks, provider keys that stay outside the machine, TypeScript and Python SDKs that drive agents, environment variables, files and repos for each machine, and docs.
- v0.2
The full kit
DoneA web dashboard with terminals and desktops in the browser, OpenCode, keys for more AI providers, access tokens with roles and sign-in by code, and nodes: machines on a Linux server of your own.
- v0.2.3
Faster nodes
Donessh and scp straight to a node on your own network or tailnet, with the Cloudflare path as the fallback, and forks of sandboxes on nodes.
- v0.3
Safe upgrades
NextOne-command upgrades that carry your sandboxes across versions. The rest is set by what people using Cloudex ask for.
Questions
Is there a hosted version?
No. Cloudex runs only in your Cloudflare account. There’s no Cloudex service to sign up for or pay.
Can you see my code or my keys?
No. Machines, files and keys live in your account. cloudex.build serves this site, the installers and the docs. Nothing else.
Why Cloudflare?
Many developers already have an account. Machines can run in the US, Europe, Asia-Pacific or South America, sleep to zero when idle, and sit next to your Workers, R2 buckets and AI Gateway.
How is it different from boat.dev?
boat.dev rents fast, inexpensive virtual machines on its own hardware in the EU, with public IPs and a 60 fps desktop. Cloudex gives up some of that to run entirely in your account, in more regions, under an open-source license.
What does the MIT license let me do?
Use, change and redistribute Cloudex, including in commercial work. Keep the copyright and license notice with your copy.
Start your first machine
Install the CLI, then run cloudex deploy.
curl -fsSL https://cloudex.build/install | sh