Shuttle is ceasing operations. The published Pro project stop date was January 16, 2026; Community migration was due at the beginning of 2026. Growth customers have individual schedules, and post-shutdown data recovery is time-limited. Read the source ↗

Application platforms / Shuttle Rust Hosting alternative

A Shuttle Rust alternative for a durable agent execution layer

Shuttle’s official documentation says it is ceasing operations. Community users were told to migrate by the beginning of 2026, and Pro projects were scheduled to stop on January 16, 2026. Growth customers have individual timelines. Treat the remaining Rust framework and hosting documentation as migration context rather than a new hosted-service offer.

Start buildingCompare capabilities ↓

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

When Shuttle Rust Hosting fits

Use Shuttle’s surviving source and documentation to understand an existing Rust service and migration requirements. Current hosted onboarding, project availability and data retention must be confirmed with the provider under its shutdown process.

When to consider Sandbox0

Consider Sandbox0 for the compatible Linux agent execution part of the migration, with whole writable RootFS persistence, automatic online growth and supported paused files. Recreate required web serving, databases, domains and other application services separately.

Capabilities

Shuttle Rust Hosting and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeShuttle Rust HostingNot 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 filesShuttle Rust HostingExisting project/database recovery is subject to shutdown retention and actual provider access, not a verified new hosted disk offer.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSShuttle Rust HostingHistorical app deployment documentation does not establish current full mutable OS filesystem retention.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 stateShuttle Rust HostingScheduled project stopping during shutdown is not a durable resumable agent-machine service.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateShuttle Rust HostingThe reviewed app runtime and shutdown guide do not establish persisted guest RAM/process snapshots.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.

The hosted shutdown and historical app resource configuration do not establish an available automatic RootFS growth contract. Size the migrated app services separately from a persistent Linux agent.

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.

See paused file operations →

Published shutdown dates supersede the marketing homepage

The shutdown guide gives a January 16, 2026 stop date for Pro projects and says deletion occurs later. Growth customers receive individual notice with at least one month to migrate and possible flexibility. A still-readable homepage is not evidence that the former hosted offering is open for new production use.

Source 1 ↗

Data availability after shutdown is limited, not guaranteed

The provider says data may be retained for a limited period and asks users to contact it for recovery. Its Shared Postgres migration guide explains the database export path. Verify actual access and exports before planning a move; no universal final deletion date is specified for every tier.

Source 1 ↗Source 2 ↗

Historical app deployment is distinct from a returning agent OS

The deployment guide describes Rust apps on AWS ECS/Fargate and rolling replacement after health checks. That application runtime description does not establish a current full writable RootFS or RAM checkpoint product, and its former resource defaults should not be used as a current price quote.

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.

Shuttle Rust Hosting

Pricing reviewed 2026-10-19

Hosted subscription collection
Paused during shutdown
This does not mean a currently available free hosted service.
Rate source ↗
Former hosted compute plans
No current new-service tariff established
Rate source ↗
Growth migration arrangements
Individual provider communication
Rate source ↗

Historical Pro or Growth subscription prices are not current onboarding quotes. Confirm data access, any remaining commitments and the destination application’s complete hosting costs.

Check current Shuttle Rust Hosting 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 Shuttle Rust Hosting

  1. Confirm the project’s actual shutdown timeline and whether application code, secrets and Shared Postgres data remain accessible.
  2. Export and verify recoverable data, then replace app hosting, database provisioning and domain integrations as needed.
  3. Port compatible Linux agent tooling to Sandbox0 and test system retention, growth, paused files and the replacement application separately.

Common questions

Is Sandbox0 a drop-in Shuttle Rust Hosting 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 ↗docs.shuttle.dev/docs/shuttle-shutdown.md ↗docs.shuttle.dev/guides/migrate-shared-postgres.md ↗docs.shuttle.dev/docs/deployment-environment.md ↗Sandbox0 RootFS capacity →

Related comparisons

Aptible vs Sandbox0 →Azure Container Apps vs Sandbox0 →Clever Cloud vs Sandbox0 →Dockup vs Sandbox0 →Fly.io Machines vs Sandbox0 →Google Cloud Run vs Sandbox0 →