Development environments / Tencent Cloud Studio alternative

Tencent Cloud Studio alternative

Tencent Cloud Studio combines a browser IDE, CPU/GPU choices, project collaboration and coding tools. Current guidance distinguishes the newer application experience from older workspaces. For unattended agents, examine IDE-driven billing and scheduled shutdown as well as which files and installed system tools remain durable.

Start buildingCompare capabilities ↓

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

When Tencent Cloud Studio fits

Cloud Studio fits developers, classrooms and teams wanting an integrated browser development environment, templates, collaboration and Tencent account billing. Keep its education, preview and IDE layer when those are core requirements.

When to consider Sandbox0

Consider Sandbox0 when your application controls the agent’s runtime, long-running policy and whole durable RootFS, including online growth and supported paused-file operations. You supply the IDE, classroom/collaboration layer, preview UX and model integration separately.

Capabilities

Tencent Cloud Studio and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeTencent Cloud StudioThe current editor timer supports up to 24 hours per setting and extension before expiry; no absolute 24-hour lifetime is inferred.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 filesTencent Cloud StudioThe API introduction explicitly keeps workspace storage across stop/hibernation; current version and inactive-space policies must be checked.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSTencent Cloud StudioStored workspace resources do not by themselves establish durability for all writable Linux system paths.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 stateTencent Cloud StudioStop/hibernation with retained workspace storage is documented; arbitrary process-memory restore is not established.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateTencent Cloud StudioScheduled shutdown documentation does not establish preservation of arbitrary running processes and RAM.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.

Cloud Studio retains workspace storage and offers resource choices, but the reviewed current guides do not establish automatic online expansion of the complete writable RootFS. A CPU/GPU switch, a project export and a disk-growth lifecycle are different operations. Sandbox0’s qualified RootFS growth keeps the agent executing.

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.

Current file instructions use the IDE project area for upload/download and a running terminal for directory ZIP export. These sources do not establish supported complete RootFS file operations while guest compute stays paused. Avoid treating access to an application’s project page as proof of that interface.

See paused file operations →

The shutdown timer is renewable, not an absolute lifetime

Current editor guidance enables a one-hour scheduled shutdown by default. One setting can extend to 24 hours; longer continuous work requires re-entering and extending it before expiry. At the deadline the workspace stops even if the user is active. This is an important unattended-work boundary, not proof that every Cloud Studio task must end permanently at 24 hours.

Source 1 ↗

Open IDE pages can keep the meter running

The machine-hour guide says edit/learn IDE pages consume compute even without an active debug process, including background or minimized tabs. Closing all relevant tabs releases capacity after about ten minutes; manual stop is separate. Exhausting a resource pack switches to pay-as-you-go instead of automatically stopping the application.

Source 1 ↗

Resource-pack units are weighted by the chosen shape

The August 2026 purchase guide prices CPU shapes in RMB/hour and gives a resource-pack deduction factor for each. For example, 1 core/2 G uses 0.1 pack units per hour and 8 cores/16 G uses 1. First account binding grants 20 pack units, not necessarily 20 physical hours on every configuration. Preserve the published CPU/G labels and currency.

Source 1 ↗

Storage retention and version migration need explicit scope

The API introduction says stopped/hibernating workspaces keep storage until deletion. It does not define every persistent system path. The version guide recommends moving to the newer product and warns old spaces inactive for over six months may be cleaned up. Migration docs describe repository or object-storage export; do not assume full environment or process-memory portability.

Source 1 ↗Source 2 ↗Source 3 ↗

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.

Tencent Cloud Studio

Pricing reviewed 2026-10-18

CPU 1 core /2 G
RMB 0.10/hour PAYG
Resource-pack deduction factor 0.1 unit per hour.
Rate source ↗
CPU 2 cores /4 G
RMB 0.25/hour PAYG
Factor 0.25 pack units per hour; keep vendor resource labels.
Rate source ↗
CPU 4 cores /8 G
RMB 0.50/hour PAYG
Factor 0.5 pack units per hour.
Rate source ↗
CPU 8 cores /16 G
RMB 1.00/hour PAYG
Factor 1 pack unit per hour.
Rate source ↗
Initial account binding
20 resource-pack units once
Weighted consumption varies by CPU/GPU shape; not a recurring allowance.
Rate source ↗

Amounts remain in RMB, with no stale exchange-rate conversion or equal-hardware savings claim. Resource-pack discounts depend on purchase size; the published bracket list leaves an intermediate range unspecified, so use the actual checkout quote rather than filling that gap. Pack exhaustion automatically falls back to PAYG, and billing displays can lag about two hours. The older API introduction has different free-allowance language; the current machine-hour purchase guide is used for these rows.

Check current Tencent Cloud Studio 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 Tencent Cloud Studio

  1. Identify old versus new Cloud Studio, export required code/data, inventory installed tools, timer settings, collaboration and account-billing mode.
  2. Port compatible tools and files to a Sandbox0 template, retaining or rebuilding IDE/preview/classroom workflows explicitly.
  3. Test unattended task policy, process restart behavior, system-package retention, RootFS growth, paused files and the actual resource/storage/model bill.

Common questions

Is Sandbox0 a drop-in Tencent Cloud Studio 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 ↗cloudstudio.net/docs/guide/code_editing/basic_operations/auto-shutdown/ ↗cloud.tencent.com/document/product/1039/131770 ↗cloud.tencent.cn/document/product/1039/131894 ↗cloud.tencent.com/document/product/1039/94098 ↗ide.cloud.tencent.com/docs/guide/product_updates/version_comparison/ ↗cloudstudio.net/docs/guide/product_updates/data_migration/ ↗Sandbox0 RootFS capacity →

Related comparisons

Agency Tool Company vs Sandbox0 →Amp Orbs vs Sandbox0 →Bitrise RDE vs Sandbox0 →boxes.dev vs Sandbox0 →Capy vs Sandbox0 →Claw 2 Agent vs Sandbox0 →