Cloud infrastructure / T Cloud Public (formerly Open Telekom Cloud) alternative

T Cloud Public alternative for Linux agents

Open Telekom Cloud became T Cloud Public in January 2026. Its ECS and EVS services provide full cloud machines and storage. Evaluate that infrastructure portfolio separately from the lifecycle interface needed by a returning Linux agent.

Start buildingCompare capabilities ↓

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

When T Cloud Public (formerly Open Telekom Cloud) fits

Choose T Cloud Public for its regional cloud infrastructure, identity, networking and managed services. A general agent runtime does not replace those services or promise the same enterprise requirements.

When to consider Sandbox0

Consider Sandbox0 when the central need is a compatible isolated Linux agent’s complete growing durable RootFS and supported paused files. Validate regional availability, kernel compatibility and required integrations.

Capabilities

T Cloud Public (formerly Open Telekom Cloud) and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeT Cloud Public (formerly Open Telekom Cloud)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 filesT Cloud Public (formerly Open Telekom Cloud)EVS provides the machine’s block storage.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFST Cloud Public (formerly Open Telekom Cloud)ECS has an OS with EVS storage.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 stateT Cloud Public (formerly Open Telekom Cloud)Verify the selected service lifecycle; arbitrary execution preservation is unestablished.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateT Cloud Public (formerly Open Telekom Cloud)No arbitrary memory checkpoint guarantee is established here.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.

EVS already permits OS-compatible online adjustment. Sandbox0 integrates low-space triggering and a managed durable agent RootFS lifecycle rather than uniquely providing volume growth.

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.

Retained cloud storage is different from a native interface for file reads and mutations throughout the original paused RootFS. Verify any helper/restore workflow and the compute it needs.

See paused file operations →

System storage and online changes already exist

ECS combines an OS with EVS block storage. EVS supports online volume adjustment when the OS supports it. Low-space-triggered RootFS automation is a separate requirement.

Source 1 ↗

Billing depends on flavor and commitment

Open Elastic meters seconds; selected local-disk flavors and dedicated hosts remain charged while shut down. Reserved capacity commitments can bill unused allowance.

Source 1 ↗

Use the current name and regional contract

The provider changed its name in January 2026. Its price calculator supplies an estimate; account terms, selected services and regional availability determine the actual infrastructure bill.

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.

T Cloud Public (formerly Open Telekom Cloud)

Pricing reviewed 2026-10-19

EU-DE s2.medium.1, open Linux
€0.014980 per instance-hour
1 vCPU/1 GiB; October 9, 2026 tariff.
Rate source ↗
EU-DE/EU-NL s9.medium.1, open Linux
€0.044573 per instance-hour
1 vCPU/1 GiB; separate storage/network resources.
Rate source ↗

Prices exclude tax. Reserved monthly/upfront columns have term commitments; retain EUR rather than importing converted directory prices. Confirm current flavor availability and total storage, IP, traffic and license costs.

Check current T Cloud Public (formerly Open Telekom Cloud) 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 T Cloud Public (formerly Open Telekom Cloud)

  1. Map legacy account naming, ECS flavor, EVS disks, region and commitment.
  2. Export consistent system/user state and configure compatible agent tools, retaining required cloud services.
  3. Test system persistence, growth, paused files and complete runtime/storage/network charges.

Common questions

Is Sandbox0 a drop-in T Cloud Public (formerly Open Telekom Cloud) 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 ↗www.t-cloud-public.com/_Resources/Persistent/5/b/4/9/5b49ccec9ceef6d52f461deff50098200b81665f/t-cloud-public-servicedescription.pdf ↗www.t-cloud-public.com/en/prices ↗Sandbox0 RootFS capacity →

Related comparisons

Akamai Cloud / Linode vs Sandbox0 →Alibaba Cloud ACK / Harbor backend vs Sandbox0 →Alibaba Cloud ECS vs Sandbox0 →Amazon Bedrock AgentCore vs Sandbox0 →AWS EC2 vs Sandbox0 →AWS Fargate vs Sandbox0 →