Webapp.io’s official announcement states the independent platform shut down on June 1, 2025 after joining Harness. Legacy marketing and prices are historical. Read the source ↗

CI and test infrastructure / webapp.io alternative

webapp.io alternative after shutdown

Webapp.io’s official announcement says the independent platform shut down on June 1, 2025 after joining Harness. Old pages still describe CI/CD and preview environments. A migration should preserve the build and preview workflow separately from any requirement for a returning agent’s whole Linux environment.

Start buildingCompare capabilities ↓

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

When webapp.io fits

The ended independent webapp.io service is not a current new-service option. Evaluate an active CI/preview platform, including the vendor’s stated Harness direction, under that provider’s current product and commercial terms.

When to consider Sandbox0

Consider Sandbox0 for an agent’s persistent Linux runtime, not as an automatic replacement for Layerfile builds, repository triggers, preview URLs or a CI dashboard. You implement or retain those application and orchestration features.

Capabilities

webapp.io and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimewebapp.ioNot established in this reviewSandbox0ttl 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 fileswebapp.ioLegacy documentation describes snapshots and reusable environments; the independent service has ended.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSwebapp.ioHistorical VM reuse is documented; the independent service has ended and no current complete writable-RootFS retention offer is established.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 statewebapp.ioHistorical VM auto-hibernation is documented; this is not a current service offer.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process statewebapp.ioThe introduction alone does not establish the exact arbitrary-RAM capture boundary.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.

Webapp.io historically documented VM snapshots and hibernation, but its independent service has shut down. Sandbox0’s whole writable RootFS lifecycle can support a returning agent, while preview/build pipeline orchestration remains separate.

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.

There is no active independent webapp.io paused-file service to promise. For an active replacement, distinguish access to preview artifacts from supported operations on the agent’s complete paused RootFS.

See paused file operations →

The vendor shutdown announcement governs availability

The February 2025 article gives June 1, 2025 as the shutdown date and explains the move toward Harness. An accessible old signup or pricing page does not override that notice. Do not treat old plan tables as a current quote for a service you can newly purchase.

Source 1 ↗Source 2 ↗

Legacy VM reuse was more than a package cache

The historical introduction describes automatically hibernating VMs, snapshots of build steps and duplicating a stack for parallel tests. The homepage also describes full-stack previews and VM copies. These retained technical materials explain the former environment-reuse workflow; they are not a current hosted-service durability promise.

Source 1 ↗Source 2 ↗

Preview deployment and agent state need separate migration plans

Layerfiles defined build steps, backgrounds and preview behavior tied to repository pushes. Preserve those workflows, domains, integrations and test artifacts when choosing a replacement. An agent runtime adds a different requirement: retaining installed software, configuration and accumulated files across its own lifecycle.

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.

webapp.io

Pricing reviewed 2026-10-18

Independent webapp.io platform
Ended June 1, 2025; no current service price
Retained legacy plan pages do not establish current purchasable capacity.
Rate source ↗
Replacement CI and previews
Use the active provider’s current quote
The vendor points toward Harness; plan, runner, artifact and preview terms need fresh evaluation.
Rate source ↗

No historic subscription amount is presented as an active webapp.io rate. Legacy snapshot and hibernation features are described with their historical scope. Export from repositories, external storage and retained artifacts you still control; an accessible documentation site is not proof that stopped workloads or old account data remain recoverable.

Check current webapp.io 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 webapp.io

  1. Inventory Layerfiles, triggers, previews/domains, external state, test reports and any artifacts that remain under your control.
  2. Choose an active CI/preview layer; use Sandbox0 explicitly for compatible returning-agent execution and rebuild needed workflow adapters.
  3. Verify full system-state retention, growing outputs, paused files, preview routing, secrets and complete replacement costs.

Common questions

Is Sandbox0 a drop-in webapp.io 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 ↗webapp.io/blog/webapp-io-is-shutting-down/index.html ↗webapp.io/pricing ↗docs.webapp.io/introduction ↗webapp.io/ ↗Sandbox0 RootFS capacity →

Related comparisons

Apple Xcode Cloud vs Sandbox0 →Artillery vs Sandbox0 →AWS CodeBuild vs Sandbox0 →Azure Pipelines vs Sandbox0 →Bitbucket Pipelines vs Sandbox0 →Blacksmith (GitHub Actions runners) vs Sandbox0 →