Koyeb Sandboxes is documented as public preview. Verify effective account and region support before planning a production migration. Read the source ↗

Agent sandboxes / Koyeb Sandboxes alternative

A Koyeb sandbox alternative for retained agent environments

Koyeb Sandboxes is a public-preview execution product on a broader compute platform. Its sandbox idle and deletion settings, service volumes, and volume snapshots are different concepts; verify which state survives the lifecycle your agent will use.

Start buildingCompare capabilities ↓

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

When Koyeb Sandboxes fits

Koyeb fits teams deploying sandbox execution beside services, inference, and other Koyeb workloads. The SDK supports image-based creation, command and file operations, and configurable idle and deletion behavior.

When to consider Sandbox0

Consider Sandbox0 when a long-lived agent should keep installed software, configuration, and user data together in one durable writable RootFS, expand it online, and access persistent files while compute is paused.

Capabilities

Koyeb Sandboxes and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeKoyeb SandboxesIdle and deletion delays are configurable; these timers should not be interpreted as a universal active-runtime cap.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 filesKoyeb SandboxesSandbox execution is described as ephemeral. General Koyeb Volume retention is a separate documented feature.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSKoyeb SandboxesWhole writable-RootFS retention through the sandbox lifecycle is not established in this review.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 stateKoyeb SandboxesThe lifecycle documents scale-to-zero and wake; verify saved state and idle-deletion policy for the selected setup.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateKoyeb SandboxesNot established in this reviewSandbox0Experimental 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.

Koyeb instance families publish local disk capacities. Neither the reviewed sandbox lifecycle nor the general volume-snapshot docs establish automatic online growth of a sandbox’s whole writable root disk.

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 →

Idle timeout and deletion have separate timers

Koyeb documents scaling a sandbox to zero on inactivity, then optionally deleting it after a further inactivity delay. A delay from creation is another independent policy. Configure these deliberately so a reusable environment is not deleted while the application expects to reconnect.

Source 1 ↗

Volume snapshots do not prove root-disk retention

Koyeb Volumes provides persistent block storage across service deployments, and its snapshot product backs up those volumes. Those docs do not establish that every sandbox root-filesystem path or process image is captured. Verify the actual sandbox and mount workflow before relying on retained system changes.

Source 1 ↗Source 2 ↗Source 3 ↗

Combine the selected instance with the account plan

Koyeb prices compute by instance size and running time, while paid plans add workspace features and included compute credit. The instance catalogue is a capacity and price reference; confirm the chosen region, instance family, and preview availability for the sandbox you deploy.

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.

Koyeb Sandboxes

Pricing reviewed 2026-10-18

Small compute-catalogue instance
$0.0144/hour
Published catalogue shape: 1 vCPU, 1 GB RAM, 10 GB local SSD. Confirm availability for the selected sandbox and region.
Rate source ↗
Pro plan
$29/month plus compute
Includes $10 of compute credit.
Rate source ↗
Scale plan
$299/month plus compute
Includes $100 of compute credit.
Rate source ↗

Koyeb bills compute by the second. These catalogue and plan rows are not an equal-performance quote; storage products, instance family, region, scale-to-zero behavior, and preview access determine the actual bill.

Check current Koyeb Sandboxes 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 Koyeb Sandboxes

  1. Record sandbox idle and deletion policies, image, selected instance, and every retained data source before removing anything.
  2. Export required files and reproduce packages, service startup, secrets, and network rules in a Sandbox0 template.
  3. Test reconnect and pause semantics with real system changes, a growing dataset, and persistent file access while Sandbox0 compute remains paused.

Common questions

Is Sandbox0 a drop-in Koyeb Sandboxes replacement?

Evaluate API compatibility and product scope. A shared sandbox category does not make SDKs, lifecycle semantics, or limits interchangeable.

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 ↗www.koyeb.com/docs/sandboxes/sandbox-lifecycle ↗www.koyeb.com/docs/reference/volumes ↗www.koyeb.com/docs/reference/snapshots ↗www.koyeb.com/docs/sandboxes ↗www.koyeb.com/docs/reference/instances ↗www.koyeb.com/pricing ↗Sandbox0 RootFS capacity →

Related comparisons

Agent 37 vs Sandbox0 →AgentComputer vs Sandbox0 →ainclave vs Sandbox0 →Alibaba Cloud Agent Sandbox / FC / AgentRun vs Sandbox0 →Alibaba Cloud AgentBay vs Sandbox0 →Amika vs Sandbox0 →