CI and test infrastructure / Apple Xcode Cloud alternative

Apple Xcode Cloud alternative for portable agent stages

Xcode Cloud is Apple’s integrated build, test and delivery service for Apple developers. Its build environments are destroyed after the build, while reports and delivery workflows remain available through Apple tooling. Portable Linux agent work is a separate stage from native Xcode compilation and signing.

Start buildingCompare capabilities ↓

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

When Apple Xcode Cloud fits

Choose Xcode Cloud for native Apple application builds, parallel tests and integration with Xcode, App Store Connect and TestFlight. Keep the required Apple toolchain, signing and native test environment on suitable Apple services.

When to consider Sandbox0

Consider Sandbox0 for returning Linux agents that edit repositories, prepare assets or run compatible tools while retaining their system state. Its growing durable RootFS and paused-file operations serve that agent stage, rather than replacing Xcode Cloud’s native Apple delivery workflow.

Capabilities

Apple Xcode Cloud and Sandbox0: what persists?

Feature comparison with documentation and verification status
Environment and runtime lifetimeApple Xcode CloudNot 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 filesApple Xcode CloudEphemeral build environments are destroyed after build completion; outputs/reports have a separate lifetime.View evidence ↗Sandbox0The writable RootFS survives successful checkpoints, including software, system configuration, dependencies, and user data.Read documentation →
Whole RootFSApple Xcode CloudThe next task does not inherit a retained complete writable worker OS disk.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 stateApple Xcode CloudA build workflow and artifact history do not establish a returning-machine pause/resume contract.View evidence ↗Sandbox0Pause compute between tasks; resume on available capacity. Default resume starts fresh processes from the saved filesystem.Read documentation →
Memory and process stateApple Xcode CloudThe cited service does not establish arbitrary user-controlled build-process RAM checkpoints.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.

Xcode Cloud uses temporary build environments and workflow outputs. Those are distinct from retaining and automatically expanding a whole writable agent RootFS across tasks; native Apple build requirements still need the appropriate toolchain.

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.

Build reports and stored outputs expose selected results, not arbitrary read/write access throughout a paused previous worker’s entire OS filesystem.

See paused file operations →

The build machine is intentionally temporary

Apple says ephemeral build environments are destroyed when a build finishes. Stored results and app-delivery integrations are useful outputs, but they do not mean the same worker’s installed tools and arbitrary OS changes survive for the next task.

Source 1 ↗Source 2 ↗

Compute hours aggregate parallel work

A compute hour measures time spent executing a task. Parallel test and build work contributes separately, so a fast wall-clock completion can still consume several task-hours. Model the workflow’s combined action time rather than reading the allowance as uninterrupted access to one Mac.

Source 1 ↗

Membership and allowance are separate requirements

Apple Developer Program membership is required and includes 25 compute hours monthly. Larger monthly Xcode Cloud subscriptions increase the allowance; they are not a general-purpose Mac server rental. Confirm current region/currency and organization terms for the selected subscription.

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.

Apple Xcode Cloud

Pricing reviewed 2026-10-19

Included monthly compute
25 compute hours with Developer Program membership
Membership is required separately; not 25 hours of unrestricted Mac rental.
Rate source ↗
100 compute-hour subscription
US$49.99/month
Aggregate task compute allowance, not a hardware reservation.
Rate source ↗
250 compute-hour subscription
US$99.99/month
Rate source ↗
1,000 compute-hour subscription
US$399.99/month
Rate source ↗

Use Apple’s subscription allowance and aggregate task meter. Parallel actions can consume more compute hours than elapsed workflow time. Membership, local pricing/tax and required native delivery services remain separate from a compatible Linux agent’s runtime bill.

Check current Apple Xcode 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 Apple Xcode Cloud

  1. Inventory Xcode workflows, native toolchain, signing, TestFlight/App Store integrations, stored outputs and aggregate task-hour use.
  2. Move compatible repository/agent preparation to Linux while retaining native Apple build, test and delivery stages.
  3. Test artifact handoff, durable tools, online RootFS growth, paused files and combined Apple membership/allowance plus Linux runtime/storage costs.

Common questions

Is Sandbox0 a drop-in Apple Xcode 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 ↗developer.apple.com/xcode-cloud/ ↗developer.apple.com/xcode-cloud/security/ ↗Sandbox0 RootFS capacity →

Related comparisons

Artillery vs Sandbox0 →AWS CodeBuild vs Sandbox0 →Azure Pipelines vs Sandbox0 →Bitbucket Pipelines vs Sandbox0 →Blacksmith (GitHub Actions runners) vs Sandbox0 →Buildkite hosted agents vs Sandbox0 →