
Why pay $19 per month for 50 box-hours when a $5 VPS runs all month? Because Boxes.dev gives every Claude Code or Codex task its own Linux computer, complete with its own ports, processes, and database state. That is valuable for parallel agent work, but it is a managed workflow premium, not a cheaper way to buy always-on compute.

The prices below were checked on November 14, 2026. Boxes.dev is also advertising three months of Pro free for new teams through November 21, 2026. The launch offer requires a card.
Option | Monthly base | Included limits | Extra costs | Root access | 36-month cash cost | Action |
|---|---|---|---|---|---|---|
Boxes.dev Starter | $19/user | 50 box-hours, 5 awake devboxes, 5 projects | $0.40 per extra standard box-hour | Full Linux devbox; access level not published | $684 plus model usage | |
Boxes.dev Pro | $99/user | 300 box-hours, 12 awake devboxes, 10 projects | $0.40 per extra standard box-hour | Full Linux devbox; access level not published | $3,564 plus model usage | |
Boxes.dev Max | $249/user | 750 box-hours, 25 awake devboxes | $0.40 per extra standard box-hour | Full Linux devbox; access level not published | $8,964 plus model usage | |
Hetzner Cloud | From €5.49/mo, excl. VAT | Always-on cloud server; resources vary by plan | Backups and add-ons separate | Self-managed root access | From €197.64 plus VAT | |
DigitalOcean Droplet | From $4/mo | 1 vCPU, 512 MiB RAM, 10 GiB SSD, 500 GiB transfer | Backups and snapshots separate | Self-managed root access | From $144 | |
Vultr Cloud Compute | From $5/mo | 1 vCPU, 1 GiB RAM, 25 GB storage, 1 TB bandwidth | Backups and add-ons separate | Self-managed root access | From $180 |
The 36-month figures multiply the published monthly base rate by 36. They exclude tax, model/API charges, backups, snapshots, and Boxes.dev overage. They are cash-cost comparisons only, not a performance ranking.
What the $19 Boxes.dev plan actually buys
Boxes.dev is closer to a managed agent workbench than a normal VPS. It gives each meaningful Claude Code or Codex task a fresh cloud devbox created from a snapshot of your prepared development environment.
A Git worktree creates another checkout on the same machine. A Boxes.dev devbox gets its own filesystem, processes, ports, and database state. That difference matters when five agents need to run the same application at once. They do not have to share one laptop's memory or fight over the same localhost ports.
The standard machine is 4 vCPU, 8 GiB of RAM, and 100 GB of disk. Boxes.dev bills while a machine is awake, by the second. Sleeping devboxes are free.
Machine size | Box-hours used per awake hour | Extra-hour equivalent |
|---|---|---|
4 vCPU / 8 GiB | 1 | $0.40 |
4 vCPU / 16 GiB | Approximately 1.39 | Approximately $0.56 |
8 vCPU / 16 GiB | 2 | $0.80 |
8 vCPU / 24 GiB | Approximately 2.39 | Approximately $0.96 |
8 vCPU / 32 GiB | Approximately 2.78 | Approximately $1.11 |
That accounting model is the catch. A standard devbox kept awake for 30 days consumes roughly 720 box-hours. Pro includes 300. Max includes 750 before larger-machine multipliers. Boxes.dev is designed for bursty parallel work, not for replacing a 24/7 application server.
Boxes.dev versus native Claude and Codex cloud tools
The model vendors already run coding sessions in the cloud. Boxes.dev has to justify charging separately for the computer around the agent.
Workflow | Where work runs | Machine billing | Main advantage | Main catch |
|---|---|---|---|---|
Boxes.dev | Separate Linux devbox per task | Awake box-hours; sleeping is free | Full copied environment, ports, previews, mobile and Slack/Linear triggers | You pay for the workspace and still pay Anthropic or OpenAI |
Claude Code cloud | Anthropic-managed cloud session or approved self-hosted environment | No separate VM charge; uses plan limits | Native Claude workflow continues after laptop closes | Environment and access model follow Anthropic's cloud setup |
Codex Cloud | Reusable OpenAI cloud environment with isolated task workspaces | Tied to Codex/ChatGPT access or API billing | Repository setup, dependency installation, and isolated tasks | Less useful if you need a copied local database and general Linux machine |
Self-managed VPS | Your own Linux VM | Fixed or usage-based server bill | Root control and persistent compute | You build agent isolation, snapshots, notifications, and secret handling |
Boxes.dev's strongest case is not raw CPU per dollar. It is the migration of a working local environment into repeatable machines that agents can use without colliding with one another. If you only need SSH, Docker, a database, or a long-running website, the VPS rows in the first table are the more rational purchase.
Bring your own model account, then secure it
Boxes.dev says it runs the unmodified Claude Code and Codex tools with your existing subscription or API key. Its plan does not include Anthropic usage, ChatGPT plan access, or OpenAI API credits.
That also means the model providers' rules still matter. Anthropic requires hosted products to run the unmodified Claude Code binary, avoid reselling or intermediating user usage, and let each user authenticate with their own subscription or API credentials. OpenAI's Codex documentation warns against exposing Codex execution in untrusted or public environments.
Treat the setup migration as a security decision. Use development, staging, or read-only credentials where possible. Do not upload production keys simply because the agent wants to run the full application. Rotate credentials when the remote machine no longer needs them.
Who should buy Boxes.dev?
Boxes.dev makes sense for developers who regularly run several Claude Code or Codex agents and need each agent to test a complete application. The Pro tier is the first plan aimed at daily parallel work, but its 300 standard box-hours still do not cover a full month of one always-awake box.
Starter is a reasonable trial for occasional parallel tasks. It becomes expensive if one devbox stays active for most of the month or if you use larger machines. Max is easier to justify when parallelism is the constraint and the work is genuinely bursty.
Skip it for a small website, a persistent database, a VPN, or a general-purpose server. Those workloads do not need a new cloud computer for every agent task.
The $5/mo DIY VPS escape hatch
If Boxes.dev's managed layer is the part you do not need, use a self-managed VPS instead. Lock In Hetzner Deal -> is the low-cost option for persistent cloud compute, with published Cloud plans starting from €5.49 per month before VAT. Check DigitalOcean Stock -> starts at $4 per month for a tiny Droplet that can handle a control node or small service. Check Vultr Compute -> starts at $5 per month for a 1 vCPU, 1 GiB instance with 25 GB storage and 1 TB bandwidth.
Those VPS offers provide more continuous server time per dollar. They do not give you Boxes.dev's per-agent snapshots, mobile workbench, public preview workflow, or Slack and Linear triggers. You will install Claude Code or Codex, configure SSH, isolate tasks, manage secrets, and keep the machine patched yourself.
The choice is simple. Buy Boxes.dev when the orchestration saves more time than the compute premium. Buy a VPS when you want root control and a server that stays up all month.
Is Boxes.dev a VPS provider?
No. It is a managed cloud development environment that provisions Linux devboxes for coding agents. It is not a fixed-price, always-on VPS plan.
Does the $19 Starter plan include Claude or Codex usage?
No. Boxes.dev provides the cloud machine time. You bring your Claude Code or Codex subscription or API key, and model usage is billed or limited separately.
What does one box-hour mean?
One box-hour is one hour with a standard 4 vCPU / 8 GiB box awake. An 8 vCPU / 16 GiB machine uses two box-hours per hour.
Is Boxes.dev cheaper than a regular VPS?
No, not for persistent compute. A VPS usually costs less over 36 months because it charges for one always-on server. Boxes.dev earns its premium through isolated machines, environment snapshots, agent triggers, previews, and remote controls.
What is the best Boxes.dev alternative?
Choose Hetzner, DigitalOcean, or Vultr when you want a persistent self-managed Linux server. Choose native Claude Code Cloud or Codex Cloud when you want the model vendor's own cloud session without a separate Boxes.dev machine charge.
0 comments
No comments yet
Leave a comment