The official lakeFS notice confirms tilde.run shut down as a separate product; work shifted to lakeFS Mount. Published July 1, 2026, updated September 17, 2026. Read the source ↗

Agent sandboxes / Tilde.run (discontinued) alternative

A tilde.run alternative after the standalone service shut down

The official lakeFS announcement confirms that tilde.run ended as a separate product and its lessons now inform lakeFS Mount. A replacement decision should reconstruct the execution environment and required saved state rather than apply the old directory’s sandbox price to a currently available service.

Start buildingCompare capabilities ↓

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

When Tilde.run (discontinued) fits

Evaluate lakeFS Mount when versioned filesystem access, branching and governed data are central to your workload. It is a different product boundary from a hosted agent computer; confirm its present supported integrations and commercial terms separately.

When to consider Sandbox0

Consider Sandbox0 for a hosted Linux computer that retains the whole writable RootFS, expands it online on enabled templates, and supports persistent-file access while compute is paused. Restore only the data, configuration and artifacts you actually retained from the former service.

Capabilities

Tilde.run (discontinued) and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeTilde.run (discontinued)Not 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 filesTilde.run (discontinued)The shutdown notice does not establish current tilde.run storage availability or access to former customer data.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSTilde.run (discontinued)The transition notice does not establish a current complete-RootFS retention contract; the standalone service has ended.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 stateTilde.run (discontinued)No current standalone tilde.run pause/resume service is offered by this notice.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateTilde.run (discontinued)The notice does not verify a current execution-memory restoration feature.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.

A filesystem/data layer’s branching capabilities are distinct from automatic online expansion of a continuing agent computer’s complete writable RootFS. Evaluate the replacement runtime and data layer together where both are required.

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 →

The official notice establishes the service transition

The announcement was published July 1, 2026 and later updated September 17. It says the team stopped tilde.run as a separate product and focused on lakeFS Mount. Confirm the successor data layer’s scope separately from replacement Linux compute.

Source 1 ↗

A data filesystem and an agent runtime solve different parts of the workflow

The notice describes Mount in terms of filesystem access, versioning, branching and governance for agent data. Those capabilities may remain useful, but the announcement does not establish a new rented Linux machine, process-memory checkpoint contract or direct drop-in replacement for the retired service.

Source 1 ↗

Historical prices do not establish a current purchasable offer

A shutdown announcement is not a current sandbox rate card. Price the chosen successor data layer and replacement compute separately, including retained storage and data transfer, instead of presenting a legacy tilde.run rate as available today.

Source 1 ↗

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.

Tilde.run (discontinued)

Pricing reviewed 2026-10-18

Current standalone tilde.run service
Unavailable: separate product shut down
Rate source ↗
Historical tilde.run rates
Not presented as a current offer
Rate source ↗
lakeFS Mount and replacement compute
Separate products; confirm their current commercial terms
Rate source ↗

No current numerical legacy bill or migration savings percentage can be derived from the shutdown notice. Service closure does not prove that a former account’s data is recoverable; verify your own exports and backups.

Check current Tilde.run (discontinued) 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 Tilde.run (discontinued)

  1. Locate exports, Git changes, artifacts and external backups, and record the old tool, credential, storage and process assumptions.
  2. Reconstruct compatible tools in a Sandbox0 template and attach or integrate any separately required versioned data service.
  3. Validate whole-system reuse, growing RootFS data, paused file access, restart/process requirements and current compute plus data-service pricing.

Common questions

Is Sandbox0 a drop-in Tilde.run (discontinued) 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 ↗lakefs.io/blog/we-recently-shut-down-tilde-run/ ↗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 →