macOS compute / Veertu Anka Build Cloud alternative

Veertu Anka Build Cloud alternative for portable agent work

Anka Build Cloud orchestrates macOS VMs on Apple hardware, with templates, a registry and CI integrations. Those VMs can preserve complete installed Mac environments. A Linux runtime can take compatible agent work, while Xcode, Apple SDKs and native signing still need a suitable Mac stage.

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

When Veertu Anka Build Cloud fits

Choose Anka for private macOS VM fleets, Apple development tools and integration with an existing Mac-host/CI estate. Template distribution and dedicated control of the underlying Macs are central parts of that model.

When to consider Sandbox0

Consider Sandbox0 for portable Linux orchestration, repository work and agent tools needing a durable growing RootFS and supported paused files. Keep native macOS builds, Apple signing and simulator stages on Anka or other suitable Apple infrastructure.

Capabilities

Veertu Anka Build Cloud and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeVeertu Anka Build CloudVM duration follows the Mac fleet and CI lifecycle. Suspend behavior differs between Apple Silicon CLI and GUI; a portable suspended-process contract is not implied.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 filesVeertu Anka Build CloudVM disks and templates can retain the installed macOS environment; ephemeral CI disposal is a separate lifecycle choice.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSVeertu Anka Build CloudVirtual-disk state covers the installed Mac system rather than only a repository mount.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 stateVeertu Anka Build CloudGUI suspend exists with Apple Silicon host restrictions; ARM CLI suspend currently performs a stop.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateVeertu Anka Build CloudGUI suspend can preserve execution state, but Apple Silicon suspended VMs cannot move between hosts; CLI behavior differs.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.

Anka already retains complete macOS virtual disks. Enlargement changes virtual-disk configuration, can break clone image sharing and needs APFS expansion; that differs from Sandbox0’s automatic online growth for a supported Linux RootFS.

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.

Anka host mounts and VM tooling have their own data-transfer scope. The cited guides do not establish native arbitrary whole-filesystem operations on a paused VM with its guest compute remaining stopped; retain checkpoint consistency when using host-side tools.

See paused file operations →

Suspend depends on architecture and interface

The modification guide says Apple Silicon CLI suspend currently stops the VM despite displaying suspended. GUI suspend preserves state, but that suspended VM cannot move to another host. Do not assume the status label means a portable running-process checkpoint.

Disk growth has a template and APFS workflow

Anka permits explicit virtual-disk enlargement, then APFS expansion inside the VM. Resizing a clone breaks its shared image chain, so the guide recommends changing the source template first. These are controlled image/storage operations, rather than automatic low-space RootFS growth.

Licensing is separate from Mac capacity

Anka Build commercial licenses are annual subscriptions. Apple Silicon pricing depends on host count and model; Intel licensing is core-based. Obtain an edition-specific quote and include the physical or hosted Macs, storage and fleet operations rather than treating the software license as included hardware runtime.

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.

Veertu Anka Build Cloud

Pricing reviewed 2026-10-19

Anka Build on Apple Silicon
Annual host/model-based license quote
Software licensing, not a per-second hosted Mac compute quote.
Rate source ↗
Anka Build on Intel
Annual core-based license quote
Edition and host configuration affect terms.
Rate source ↗
Evaluation
30-day trial
Underlying Apple hardware or hosting remains a separate requirement.
Rate source ↗

Numeric commercial license rates require a quote. Include the selected edition, Apple hosts, registry/storage, CI infrastructure and support requirements. Anka Develop and Flow have different licensing scope and must not be substituted for a Build Cloud entitlement.

Check current Veertu Anka Build 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 Veertu Anka Build Cloud

  1. Inventory Intel versus Apple Silicon hosts, template chains, GUI versus CLI suspend, licensing and native macOS dependencies.
  2. Move only compatible Linux agent stages and export needed files/tool configuration; keep Apple builds, signing and simulators on suitable Macs.
  3. Test cross-stage artifacts, system retention, low-space growth, paused files and combined Mac licenses/hosts plus Linux runtime costs.

Common questions

Is Sandbox0 a drop-in Veertu Anka Build 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.

Related comparisons