Windows GitHub Actions runners that don’t crawl.
Windows Server 2025 jobs on bare-metal NVMe, single-tenant, billed by the second. The same one-line runs-on swap, half of GitHub’s Windows minute, without the slow shared runner and its network disk.
Same actions, same PowerShell, same MSVC. On bare-metal NVMe instead of a shared cloud VM.
Faster because
the hardware is faster.
Windows CI is disk- and I/O-bound, and GitHub’s Windows runners sit on network storage. Local NVMe is where most of this gap comes from. Medians on public repositories.
Workload Test Comparison
Pick it in the workflow file.
Windows Server 2025 (preview). RAM scales at 4 GB per core; disk is 150 GB on local NVMe. Developer Mode and Hyper-V are enabled.
Disk that keeps up.
Windows builds live or die on I/O. Job disks are on host NVMe at 3.1 GB/s, not a network volume, which is where the win over GitHub’s Windows runners comes from.
A fresh Windows every job.
Each job boots its own VM and is destroyed at teardown. No shared runner state, no leftover installs from the last build, no reuse.
Windows without the tax.
GitHub bills Windows at twice a Linux minute. Ours carries the licence cost, not a margin, a fraction of a cent per minute, billed by the second.
Half of GitHub’s Windows minute.
Windows carries a licence cost and a larger base image, that is what the gap against Linux pays for, not margin. Billed by the second.
GitHub-hosted Windows is $0.016/min for 2 cores. Sandal bills wall-clock seconds on bare metal. All runners, every OS →
One balance. Every machine you run.
Runners draw from the same credit pool as your sandboxes, simulators and Xcode builds, billed by the second at one published rate card.
Starter
For a solo build or a first agent in production.
$20 of usage credits
≈ 550 VM-hours or 33,000 CI minutes
- 20 concurrent machines
- Committed in-plan rates on every product
- Linux & Windows, sandboxes, VMs, runners
- Per-second billing, paused is free
- Full API, SDKs, CLI & MCP server
- Unlimited seats
- Community support
Team
Apple silicon unlocked, and a balance that rolls over.
$100 of usage credits
≈ 2,700 VM-hours or 10,000 Mac build minutes
- 100 concurrent machines
- Everything in Starter, plus:
- macOS, iOS/Android simulators & Xcode builds
- Unused credits roll over one month
- Usage exports & per-second line items
- Email support
Business
Higher ceilings for a team leaning on the fleet daily.
$250 of usage credits
≈ 6,900 VM-hours or 25,000 Mac build minutes
- 300 concurrent machines
- Everything in Team, plus:
- Raised concurrency & start rate
- Priority support & shared Slack channel
- Single sign-on (SAML / OIDC)
- Volume credit rate
Enterprise
Dedicated capacity, your compliance surface, one invoice.
Committed volume rate
Committed volume rate, negotiated per account
- Reserved bare-metal capacity
- BYOC or self-host the control plane
- SSO & SCIM, audit logs, data residency
- Annual invoicing, MSA, DPA
- Support SLA & solutions engineering
- Custom regions on request
Every plan spends its credit pool first, then usage keeps flowing and bills per second at your committed in-plan rate, no hard stop mid-run, no forced upgrade. Without a plan you pay the on-demand rate instead. Prices are illustrative pending final list pricing; the per-second billing model is final.
The runner rate card.
Linux
Windows
macOS · Apple silicon
Linux runners are the VM ladder priced per minute; Windows is 2x. macOS runners are dedicated Apple-silicon Mac minis. On-demand is 1.5× the in-plan rate. All usage bills by the second; paused machines are not billed.
Give your AI agents somewhere to run today.
Your agents get their own machines across Linux, macOS, Windows, iOS and Xcode in milliseconds, and you stop paying for idle.