When Does Daytona Cost Less Than Vercel Sandbox?

Price Daytona’s reserved resources and Vercel Pro’s active CPU from the same pilot, then calculate the CPU usage at which Daytona becomes cheaper.

Reconcile Daytona charges against completed state changes

Export state timestamps for a small cohort with identical resource allocations. For each sandbox, start the full-rate clock at creation and include the time spent creating, starting, stopping, or pausing. Put time into the disk-only column once a retained sandbox reaches the confirmed stopped or paused state. An illustrative two-vCPU, four-GiB sandbox accrues $0.1656 per full-rate hour for CPU and RAM at the supplied rates. If 1,000 stop requests each take an illustrative 12 seconds to settle, an estimate that ends compute billing at request time misses 3.33 full-rate hours, or about $0.55 in CPU and RAM alone. Compare that transition subtotal with the invoice discrepancy before investigating resource sizing. Track disk through confirmed removal and reconcile storage discounts at the scope shown on your bill.

Billing | Daytona

Measure waiting time and short runs separately

Replay two representative job classes on Vercel Sandbox: one that waits on a model response and one that compiles locally. Capture active CPU hours and billed provisioned memory hours independently. At the supplied Vercel Pro rates for iad1, an illustrative hour with four GB of provisioned memory and 0.02 active vCPU-hours incurs about $0.0874 for CPU and memory. At one active vCPU-hour, the same memory allocation brings that subtotal to $0.2128. Run the comparison on successful jobs and include their failed attempts in the usage totals. Keep short jobs in a separate bucket because Vercel’s one-minute minimum for provisioned memory can materially change their cost. Compare the memory sizes that meet the same workload target on each platform and record each meter in its own units, GiB or GB.

Vercel Sandbox pricing and quotas

What the meter actually charges

Daytona uses pay-as-you-go billing based on the resources reserved for your sandboxes: vCPU, RAM, and disk. The billing unit is the reserved resource, not measured CPU load, so an idle started sandbox costs the same as a busy one of identical shape.

The primary pricing page lists $0.0504 per vCPU-hour, $0.0162 per GiB-hour for memory, and $0.000108 per GiB-hour for storage after the first 5 free GiB. Billing is calculated per second. Windows and GPU sandboxes carry separate rates. Before estimating, confirm which platform and rate card you were quoted, because the meter page and the pricing page are separate sources that can change independently.

A practical implication: shrinking an underused sandbox saves money, but leaving one running idle does not. Track running time, not CPU utilization, as the cost driver.

Daytona - Secure Infrastructure for Running AI-Generated Code

Lifecycle states change the bill

The billing documentation distinguishes resource states. Started sandboxes bill for all reserved vCPU, RAM, and disk. Creating, starting, stopping, and pausing bill the same as started, because resources remain reserved during transitions, so reduced billing applies only once the sandbox reaches the stopped or paused state, not when the operation begins.

Stopped and paused sandboxes bill for reserved disk only. The preserved memory state of a paused VM sandbox is not billed, and pausing is supported for VM sandboxes only. Archived and deleted sandboxes are not billed, though snapshots created from a sandbox remain billed for storage.

Ephemeral sandboxes and GPU sandboxes are automatically deleted when stopped, so stopped billing does not apply to them. For a workload that idles overnight, stopping a container sandbox or pausing a VM sandbox is the lever that cuts spend.

Billing | Daytona

Worked monthly estimate

Illustrative inputs only: a container sandbox with 2 vCPU, 4 GiB RAM, and 4 GiB disk, running 730 hours in a month. Compute: 2 x $0.0504 x 730 = $73.58. Memory: 4 x $0.0162 x 730 = $47.30. Disk: 4 GiB falls within the first 5 free GiB, so $0. Total roughly $120.88, near the usage-based example figure of $120.89 for the same shape.

Now the same sandbox runs 200 hours and stops for the remaining 530. Running: (2 x $0.0504 + 4 x $0.0162) x 200 = $33.12. Stopped: disk only, $0 because 4 GiB is free. Total about $33.12, a 73 percent reduction. This is illustrative arithmetic, not a measured invoice. Verify current rates before committing a budget, and confirm whether the 5 GiB disk allowance applies to your account.

Daytona - Secure Infrastructure for Running AI-Generated Code

Troubleshooting the gap between estimate and invoice

Two sources of surprise are documented. First, transition time bills at full rate: a sandbox that spends long periods creating, stopping, or pausing is charged as if started, so the reduced stopped rate may not arrive when expected. Second, disk billing and disk quota are separate, so a sandbox can be billed for reserved disk without counting against your organization's storage limit.

After cancellation, Daytona sends a final billing summary within 5 business days, itemizing charges posted during a 48-hour settlement window. If a post-cancellation charge looks wrong, disputes can be sent to support@daytona.io within 30 days, with detailed usage records provided on request.

Check the billing state table before assuming an idle sandbox is free. If your estimate and invoice diverge, separate transition time, reserved disk, and snapshot storage in the reconciliation.

Billing | Daytona

Sources