Cloud infrastructure / netcup VPS alternative

netcup VPS alternative for persistent Linux agents

netcup VPS retains a full installed virtual server and offers offline disk snapshots plus online server-state snapshots. Its contract period, billing period and snapshot type matter for returning agents. A reserved VPS is a different operating model from a managed per-agent runtime.

Start buildingCompare capabilities ↓

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

When netcup VPS fits

Choose netcup for VM administration, its included server controls and contract-priced infrastructure. VPS, Root Server and ARM plans have different CPU and product terms; select the actual plan rather than treating every vCore as dedicated.

When to consider Sandbox0

Consider Sandbox0 for compatible Linux agents with low-space-triggered online whole-RootFS growth and supported paused-file operations. Preserve needed VM/kernel features and netcup network integrations.

Capabilities

netcup VPS and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimenetcup VPSNot 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 filesnetcup VPSOffline snapshots retain full server disk state and can be exported/restored.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSnetcup VPSThe installed server environment is captured, beyond a workspace directory.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 statenetcup VPSOnline snapshots can restore running server state; this does not establish compute-free pause billing.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process statenetcup VPSOnline snapshots retain the documented running server state, with export/LBS and consistency limits.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.

netcup already retains full system disks and can snapshot running server state. Whole-plan upgrades and separate Local Block Storage differ from automatically expanding the complete durable RootFS online as an agent runs low on space.

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.

An offline snapshot can be exported and restored to a compatible server, while rescue/guest file tools need running compute. Exported disk copies do not establish direct file operations throughout the original stopped RootFS without booting a guest.

See paused file operations →

Offline and online snapshots have different guarantees

Offline snapshots require a powered-off server and can be exported or imported to another server with sufficient disk space. Online snapshots preserve the running server state but cannot be exported, can temporarily make the VM unresponsive and are unavailable with Local Block Storage. Concurrent file changes during capture can risk data loss.

Source 1 ↗

Storage expansion is not the same as a bigger boot filesystem

netcup offers complete-plan upgrades and Local Block Storage; the selected VPS 1000 plan lists up to 8 TB of Local Block Storage. That is an additional-storage entitlement, not proof that the complete boot RootFS automatically expands when free space is low. Individual component upgrades and downgrades have separate restrictions.

Source 1 ↗Source 2 ↗

A monthly displayed amount can have a multi-year bill

The selected VPS 1000 G12.5 reference has a 24-month minimum and 24-month billing period. Region and IPv4 choices change its price, and VAT follows the selected country. Compare the contract cash commitment, not only the displayed monthly equivalent.

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.

netcup VPS

Pricing reviewed 2026-10-19

VPS 1000 G12.5 selected reference
€12.32 per month equivalent, including 19% VAT
4 vCore/8 GB/128 GB SSD; 24-month contract and billing period, no-preference Europe, IPv4+IPv6.
Rate source ↗
Selected setup fee
€0 setup
Configuration-specific reference, not every netcup offer.
Rate source ↗
Location / network options
Selected location and IP affect the amount
IPv6-only and location choices have their own adjustments.
Rate source ↗

Verify current generation, promotion, country/VAT, minimum term, billing period, setup and cancellation rules. The selected plan has traffic policy and LBS/snapshot conditions; a subscription and online snapshot are not evidence of a compute-free stopped tariff.

Check current netcup VPS 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 netcup VPS

  1. Inventory generation/CPU type, contract and billing periods, root versus Local Block Storage, snapshot type and required process state.
  2. Export consistent supported state and configure compatible agent tools on Sandbox0 while preserving required netcup services.
  3. Test installed tools, online growth, memory continuity requirements, paused files and total contract, storage, IP and network costs.

Common questions

Is Sandbox0 a drop-in netcup VPS 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.netcup.com/de/helpcenter/dokumentation/server/medien ↗www.netcup.com/de/helpcenter/dokumentation/general/tarif-upgrade ↗www.netcup.com/en/server/vps/vps-1000-g12.5-iv-24m-eu ↗www.netcup.com/en/server/vps ↗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 →