What does one serverless task cost?
Serverless compute is priced by the second, but vendors count different things. The table prices the same short agent task at each sandbox vendor with published rates, cheapest first. The row marked ours is rent.dev.
One agent loop task (30 min on 2 vCPU and 4 GiB) costs from $0.0346 on Northflank's cloud to $0.0828 on E2B's sandbox; on rent.dev's own sandboxes it costs $0.0452. Rates read .
rent.dev's price board prices longer tasks too, with the source of each vendor's rates linked.
One agent task, priced at each sandbox vendor
| Sandbox | Billed by | One task | Source | Rate read |
|---|---|---|---|---|
| Northflank cloud | Northflank | $0.0346 | northflank.com | |
| rent.dev sandbox (ours) | rent.dev | $0.0452 | rent.dev/prices | |
| Cloudflare containers | Cloudflare | $0.0452 | developers.cloudflare.com | |
| Fly.io sprites | Fly.io | $0.0508 | fly.io | |
| Vercel sandbox | Vercel | $0.0552 | vercel.com | |
| Modal sandbox | Modal | $0.0569 | modal.com | |
| Daytona sandbox | Daytona | $0.0828 | daytona.io | |
| E2B sandbox | E2B | $0.0828 | e2b.dev |
Why compare whole tasks
A serverless sandbox is a small machine that starts for one task and is thrown away. Vendors bill it for vCPU and memory by the second, yet two vendors with the same list rate can charge very different amounts for the same task. One counts the CPU you were given, another the CPU you used, and some add a fee per sandbox or a monthly plan. Pricing one whole task, start to stop, is the fair way to compare. rent.dev's own sandboxes bill by the second from one prepaid balance, on the memory they hold plus the CPU they use.
How to read the table
Each price is one whole task: the same length, CPU count and memory at every vendor, with the CPU busy for the same share of the time. The caption above the table gives the shape of the task.
Billed by names who charges you. The row marked ours is billed by rent.dev from your prepaid balance; every other row is that vendor's own product, and that vendor bills you for it.
Each source link opens the page the vendor's rates were read from, and the read date says when.
Why a cheap rate can cost more
A task that waits on a model most of the time leaves its CPU idle. A vendor that bills idle CPU at the full rate charges for that wait, and a vendor that bills only the CPU used does not. So the lowest rate on a pricing page is not always the cheapest task.
Read on: How serverless compute is priced, from the meter to the task.
Agents can start at rent.dev/llms.txt, which lists every route.