Network and edge platforms / Cloudflare Workers for Platforms alternative

Cloudflare Workers for Platforms alternative

Workers for Platforms lets a platform deploy and dispatch customer Workers. It combines request-based execution with Cloudflare storage and service bindings. That multi-tenant application platform serves a different layer from a persistent Linux computer with installed agent tools.

Start buildingCompare capabilities ↓

Reviewed 2026-10-19 · Published by the Sandbox0 team

When Cloudflare Workers for Platforms fits

Choose Workers for Platforms for customer-provided Worker code, dispatch isolation and access to the Cloudflare application ecosystem. Keep it for edge application and multi-tenant platform requirements.

When to consider Sandbox0

Consider Sandbox0 when agents need Linux commands, installed dependencies and a complete durable growing RootFS. Edge routing, customer script distribution and Cloudflare data bindings remain separate integrations.

Capabilities

Cloudflare Workers for Platforms and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeCloudflare Workers for PlatformsRequest wall time has no duration meter or limit on the price page, while CPU is capped at thirty seconds per invocation or fifteen minutes for Cron/Queue invocations.View evidence ↗Sandbox0ttl and hard_ttl default to 0 (disabled). Configure idle pause and deletion policies for the same persistent sandbox identity; an idle running sandbox still accrues compute charges.Read documentation →
Persistent filesCloudflare Workers for PlatformsStorage bindings retain selected service data; they are not a generic execution-disk contract.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSCloudflare Workers for PlatformsNo complete writable Linux RootFS contract is established for user Workers.View evidence ↗Sandbox0Persistence extends beyond /workspace to paths such as /usr/local, /etc, and /home. Runtime tmpfs and virtual filesystems are excluded.Read documentation →
Release compute, keep stateCloudflare Workers for PlatformsRequest lifetime does not establish arbitrary machine checkpoint/resume.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateCloudflare Workers for PlatformsDurable Object or service data is not a checkpoint of arbitrary Linux RAM.View evidence ↗Sandbox0Experimental memory checkpoints can preserve compatible process state. Use memory: true on both pause and resume on a compatible deployment. A filesystem checkpoint alone does not preserve running processes.Read documentation →

Online RootFS growth

On growth-enabled images, Sandbox0 automatically expands the writable RootFS as free space runs low, within a configured sparse logical ceiling up to 64 TiB. Agent processes keep running. Growth is enabled in the qualified Cloud region; confirm activation for other regions. Existing images and snapshots retain their captured storage geometry. The ceiling is logical capacity, not preallocated host disk.

Scaling a Worker fleet and its bound data services differs from growing a Linux agent’s whole writable RootFS online. Compare the actual code and persistence interfaces before choosing either execution layer.

Files while compute is paused

Sandbox0's Files API reads persistent files without resuming compute. Filesystem-only pauses also permit edits; retained-memory pauses are read-only and reject mutations with 409. SSH, SFTP, file watching, and runtime-only mounts require running compute.

Bound data services can remain accessible outside a request. That is independent application storage, rather than file operations across a paused Linux guest’s complete supported RootFS.

See paused file operations →

Bindings retain application data through separate services

User Workers can use service bindings, including storage products. Durable application data is valuable, but a binding does not establish retention of a complete mutable Linux operating-system filesystem or arbitrary native processes.

Source 1 ↗

Duration and CPU time have different meanings

The price page has no duration charge or duration limit under its meter, while CPU time is charged and capped: 30 seconds per invocation, or 15 minutes for Cron/Queue invocations. An open request’s wall time is not unlimited CPU execution or a retained process checkpoint.

Source 1 ↗

Unlimited script capacity still has a script charge

The limits page permits an unlimited number of scripts. The paid plan includes 1,000 scripts and charges for additional scripts. Capacity limits and included billing allowances are different controls; request, CPU and script meters must all be counted.

Source 1 ↗Source 2 ↗

Pricing

Compare billing models, then price your workload

CPU allocation, memory, billing minimums, disk, plan fees, and supported workload differ. These meters are not equal-performance machine quotes. Confirm region, resource units, and included allowances before estimating a total.

Cloudflare Workers for Platforms

Pricing reviewed 2026-10-19

Paid plan
$25/month
Includes 20M requests, 60M CPU milliseconds and 1,000 scripts.
Rate source ↗
Request overage
$0.30 per million requests
One request across dispatch → user → outbound Worker; subrequests are excluded as documented.
Rate source ↗
CPU overage
$0.02 per million CPU milliseconds
CPU time is summed across the Worker chain.
Rate source ↗
Additional scripts
$0.02 per script
Above the 1,000 included in the monthly plan.
Rate source ↗

Cloudflare storage/services have their own billing. Request duration is distinct from CPU time and from a continuously available Linux process. This comparison concerns Workers for Platforms; Cloudflare Sandbox is a separate product.

Check current Cloudflare Workers for Platforms pricing ↗

Sandbox0

$0.015/GiB-hour compute (billed by the second at approximately $0.000004167/GiB-second), plus $0.02/GiB-month of retained incremental RootFS and memory checkpoint data. Shared base images and platform recovery retention are excluded; paused sandboxes accrue storage charges only.

Compute / GiB-hour
$0.015
Retained data / GiB-month
$0.02
Paused compute
$0.00

A 4 GiB agent, 100 running hours

$6.00 compute

4 GiB × 100 hours, billed by the second. Keeping 20 GiB of billable incremental data for a full billing month adds $0.40. CPU is derived from memory by the platform; choose a tier that fits your workload.

Understand storage billing →

Before migrating from Cloudflare Workers for Platforms

  1. Inventory user Workers, dispatch/outbound chains, storage bindings, CPU caps and per-customer limits.
  2. Port Linux-dependent agent work to Sandbox0 while retaining necessary edge dispatch and storage integrations.
  3. Test tool compatibility, state retention, RootFS growth and total request, CPU, script, storage and runtime meters.

Common questions

Is Sandbox0 a drop-in Cloudflare Workers for Platforms replacement?

Evaluate API compatibility and product scope. These products serve different core workflows, so a change may require a different architecture.

Does keeping files also keep a running agent?

Filesystem state and volatile process state are separate. Sandbox0 requires explicit compatible memory checkpoints to preserve running processes; its default filesystem resume starts fresh processes.

Sources and review scope

The Boat team's Battleships directory is the discovery source. References below describe the product and plan discussed on this page. Check current availability, regional terms and billing units before migrating. Where the cited material does not establish a capability or price, the comparison identifies that uncertainty.

Battleships research record ↗developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/configuration/bindings/ ↗developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/reference/pricing/ ↗developers.cloudflare.com/cloudflare-for-platforms/workers-for-platforms/reference/limits/ ↗Sandbox0 RootFS capacity →

Related comparisons

Apoxy vs Sandbox0 →Agency Tool Company vs Sandbox0 →Agent 37 vs Sandbox0 →Agent Relay vs Sandbox0 →AgentComputer vs Sandbox0 →ainclave vs Sandbox0 →