Providers / published pricing

Published rates, one explicit profile.

We captured official pricing for 12 sandbox providers and normalized the published unit rates to one fully busy vCPU plus 2 GiB of memory for one hour. 12 are in the current Wildflower Computer API contract.

A normalization, not an invoice forecast

This normalization is not an invoice forecast. A null amount means comparable public unit rates are unavailable; billing bases, selectable configurations, subscriptions, credits, storage, network, regions, and idle behavior differ.

Per-sandbox providerReported andinvoiceReconciled amounts remain separate and explicitly unavailable unless Wildflower integrates an authoritative provider signal. See the provider-by-provider coverage matrix, including Modal’s aggregate-only reporting gap and Smol’s unavailable normalized estimate.

Use the catalog from code

GET /v1/providersand each generated SDK’s client.providers.list() method return the comparison profile plus every provider’s stable provider ID,displayName, normalized pricing, and runtime capabilities. Use this endpoint for application decisions; the downloadable JSON below retains the fuller published-rate calculation and source list for review.

A sandbox created today retains this evidence snapshot for its future usage estimates. Refreshing the catalog changes new decisions, not historical estimates; old registry rows without a snapshot are labeledcurrent_catalog_fallback.

Providers in the current API contract

These rows follow contract order, not price order. “Busy hour” means 100% CPU utilization for the entire hour; providers that bill actual consumption can cost less when idle or suspended.

ProviderNormalized busy hourPublished billing basisImportant caveat
AWS AgentCore$0.1084001 vCPU + 2 GiBCPU $0.089500 + memory $0.018900Active CPU and peak memory consumptionThe estimate assumes one fully busy vCPU and 2 GiB of peak memory. AgentCore Code Interpreter exposes fixed session hardware and bills actual consumption, including system overhead.
Blaxel$0.0828001 vCPU + 2 GiBActive time by allocated memoryCPU is not billed separately. The estimate uses Blaxel's documented example in which 8 GB of memory receives 4 CPU cores; suspended time and snapshot storage are separate.
ASCII Box$0.0090001 vCPU + 2 GiBFixed VM time billed by the secondBox sells a fixed 4 vCPU / 8 GB VM bundle with an account minimum. The estimate divides the included VM time by four vCPUs; it is not the price of a separately selectable 1 vCPU machine.
Cloudflare Sandbox$0.0900001 vCPU + 2 GiBCPU $0.072000 + memory $0.018000Active CPU and provisioned memoryThis is a unit-rate estimate. Cloudflare's selectable 1 vCPU container currently includes 6 GiB, and Workers, Durable Objects, disk, logs, and included allowances are outside this number.
E2B$0.0828001 vCPU + 2 GiBCPU $0.050400 + memory $0.032400Allocated resources while runningUsage is billed per running second. Subscription charges, included credits, concurrency, storage, and plan-dependent custom-resource access are separate.
Novita Agent Sandbox$0.0583201 vCPU + 2 GiBCPU $0.035280 + memory $0.023040Allocated resources while runningThe estimate excludes storage, free credits, concurrency limits, and session-length differences between free and paid access.
Daytona$0.0828001 vCPU + 2 GiBCPU $0.050400 + memory $0.032400Reserved resources while runningThe estimate excludes disk and free credits. Daytona bills reserved CPU and memory during started and transitional lifecycle states.
Modal$0.1189801 vCPU + 2 GiBCPU $0.070956 + memory $0.048024Higher of requested or actual resourcesModal prices physical cores, where one physical core equals two vCPUs. The estimate therefore uses 0.5 physical core plus 2 GiB of memory.
Runloop$0.1584001 vCPU + 2 GiBCPU $0.108000 + memory $0.050400Devbox CPU and memory consumptionThe estimate covers published Devbox CPU and memory usage only. Storage, Blueprint builds, Axons, credits, and subscription features are separate.
Smol MachinesNot publicly comparable1 vCPU + 2 GiBCloud machine compute, storage, and egress usageSmol Cloud documents metered usage and per-machine cost reporting, but does not publish comparable CPU or memory unit rates. The normalized busy-hour estimate is therefore unavailable.
Fly.io Sprites$0.1575001 vCPU + 2 GiBCPU $0.070000 + memory $0.087500Actual CPU and memory usageSprites dynamically manages resources. The estimate assumes a continuously busy vCPU and 2 GiB of actual memory for the complete hour; storage and plan charges are separate.
Vercel Sandbox$0.1704001 vCPU + 2 GiBCPU $0.128000 + memory $0.042400Active CPU and provisioned memoryThe estimate assumes a fully active CPU for one hour. Included usage, plan charges, creation, network, snapshots, and regional or enterprise pricing are separate.

What the calculation includes

  • One vCPU-equivalent at 100% utilization for 3,600 seconds.
  • Two GiB of memory for the same complete hour.
  • Only rates that the provider publishes on the cited official pages.

Storage, network, snapshots, logs, subscription fees, included credits, regional differences, minimum configurations, and provider-specific idle behavior remain outside the normalized number unless a provider’s bundle makes them inseparable. Each row preserves the relevant exception.

Official sources

AWS AgentCore

Blaxel

ASCII Box

Cloudflare Sandbox

E2B

Novita Agent Sandbox

Daytona

Runloop

Smol Machines

Fly.io Sprites

Vercel Sandbox

Refresh and review

Run corepack pnpm pricing:refresh in the API repository to capture official pages and fail closed if an expected pricing statement moves. After that change lands, run pnpm docs:refresh here to synchronize the exact API-owned data into this page and the public JSON artifact, then run the full website gate. Neither command commits, pushes, deploys, or schedules itself.