Cube vs exe.dev
exe.dev is excellent at many small VMs, fast. Cube is built around one computer for your agents, with an app on your Mac.
Published
The short version
exe.dev gives you many small, persistent VMs that start in under a second, sharing one pool of CPU, memory and disk on your plan. It’s great for spinning up a fresh machine per idea.
Cube gives your agents one Linux computer in the cloud and a Mac app to run it: repos synced from GitHub, a Git worktree per task, a sidebar of every session, and phone check-ins.
Side by side
| exe.dev | Cube | |
|---|---|---|
| Shape | Up to 50 VMs sharing one pool | One computer for your agents |
| Personal plan resources | 2 vCPU, 8 GB RAM, 100 GB disk, pooled | Pick the machine that suits you |
| Parallel work | A VM per idea | A worktree per task on one machine |
| Price | $20/month Personal, plus metered overages | Cube plan |
| Interface | SSH, web, Shelley agent | Mac app, phone, and SSH |
| Agents | Shelley, plus what you install | Claude Code, Codex, Gemini CLI, OpenCode and more from a list |
When to choose exe.dev
- You want many throwaway-but-persistent VMs, fast.
- You like its built-in agent and integrations.
When to choose Cube
- You’d rather size one machine for your agents than split a small pool across many VMs.
- You’d rather manage worktrees on one machine than many machines.
- You want a desktop app that shows every repo, worktree and session in one sidebar.
Questions
Do exe.dev VMs get their own CPU?
No. As of September 2026, the Personal plan pools 2 vCPU and 8 GB of RAM across all your VMs (up to 50), so busy VMs share the same resources.
What does exe.dev cost?
Personal is $20 a month, Team $25 per user per month, with metered overages for extra disk and data transfer. Its Shelley agent’s model usage is billed at provider rates.
When should I choose exe.dev?
When you want lots of lightweight VMs that start in under a second, or you like working through its Shelley agent and integrations.