Cloud infrastructure / NAVER Cloud Platform Server alternative

NAVER Cloud alternative for returning Linux agents

NAVER Cloud Platform provides full servers with OS disks, not just an agent workspace. Eligible stopped servers receive compute discounts while disk and attached-resource costs remain. A returning agent must also fit the documented stop-duration limits and the exact server family.

Start buildingCompare capabilities ↓

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

When NAVER Cloud Platform Server fits

Choose NAVER Cloud when its regions, full VMs and wider cloud services meet application requirements. Keep the actual VPC/Classic generation, OS, disk and attached-service configuration in the comparison.

When to consider Sandbox0

Consider Sandbox0 for compatible Linux agents needing a durable whole writable RootFS, automatic online growth and supported paused-file access. Verify regional and gVisor requirements and retain NAVER-specific application services where needed.

Capabilities

NAVER Cloud Platform Server and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeNAVER Cloud Platform ServerNot 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 filesNAVER Cloud Platform ServerEligible stopped servers retain a billed OS disk, subject to family and stop-duration limits.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSNAVER Cloud Platform ServerServer configurations include an installed OS disk rather than only a designated workspace volume.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 stateNAVER Cloud Platform ServerEligible server stop/start retains disk with a stop discount; duration limits apply and RAM continuity 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 stateNAVER Cloud Platform ServerThe stop billing/retention policy does not establish arbitrary running-memory restoration.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.

NAVER servers already preserve a complete OS disk during a supported retained lifecycle. The pricing and stop policy do not establish integrated automatic online low-space growth of that RootFS; verify disk and guest-filesystem expansion for the chosen generation.

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.

A stopped billed OS disk is retained data. The cited server policy does not specify a native API for reading and mutating arbitrary OS files with guest compute remaining off; application-level object storage is a separate scope.

See paused file operations →

A stop discount depends on the family

The FAQ lists eligible VPC and Classic families where stopping reduces the server charge to the basic OS disk. Other families, including listed GPU and Micro configurations, do not receive that treatment. Public IPs, load balancers and extra disks keep their normal charges.

Source 1 ↗

Stopped retention has explicit time limits

Discounted stopped servers cannot remain stopped beyond 90 days continuously or 180 days cumulatively in twelve months. The FAQ says NAVER notifies customers and returns over-limit servers, after which recovery is unavailable. Do not treat the stop feature as indefinite archive storage.

Source 1 ↗

Match the displayed disk and price period

The Korean Server VPC table lists Standard-g2 with 2 vCPU, 8 GB and either a 50 GB or 100 GB disk. Each disk choice has its own hourly/monthly amount. SSD Server and newer-generation tables are separate configurations, not interchangeable discounts on this quote.

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.

NAVER Cloud Platform Server

Pricing reviewed 2026-10-19

Korea Standard-g2 / 50 GB disk reference
KRW 119/hour; KRW 85,120/month
Server VPC table: 2 vCPU / 8 GB; VAT excluded.
Rate source ↗
Same Standard-g2 / 100 GB disk reference
KRW 123/hour; KRW 88,000/month
A different included disk option, not a separate additive disk charge.
Rate source ↗
Eligible stopped server
Basic OS disk plus retained attached resources
Discount and maximum stopped duration depend on family/generation.
Rate source ↗

Use the selected Korean region, Server table, OS and disk option. Monthly and hourly tariffs are separate choices, and retained disks/IPs/load balancers add charges. Rates exclude VAT. Back up needed data before any retention limit; the current FAQ does not promise recovery after a returned server.

Check current NAVER Cloud Platform Server 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 NAVER Cloud Platform Server

  1. Record VPC/Classic generation, OS/disk selection, stop-discount eligibility, accumulated stop days and attached resource costs.
  2. Export consistent required system/user state and port compatible tools, credentials and networking while retaining necessary NAVER services.
  3. Test repeated tasks, growing RootFS, paused file operations and total compute, retained disk, IP, traffic and VAT costs.

Common questions

Is Sandbox0 a drop-in NAVER Cloud Platform Server 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.ncloud.com/support/faq/all/223 ↗www.ncloud.com/charge/region/ko ↗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 →