Strict vs RunsOn: Local & Tailnet Fleets vs AWS EC2 Spot
Short answer: RunsOn spins up ephemeral AWS EC2 Spot Linux and Windows runners inside your AWS account; Strict orchestrates persistent Apple Silicon Macs and Linux hosts you already own or lease over Tailscale at $0/min compute and zero cloud infrastructure.
Compare Strict ($0/min spare Mac & Linux console behind Tailscale) against RunsOn (ephemeral AWS EC2 Spot runner orchestrator). Apple Silicon M4 support, AWS setup complexity, caching, and cost trade-offs.
Monthly CI cost & hardware payback baseline
Model published 2026 PAYG cloud runner rates against owning your own bare-metal Apple Silicon or Linux box running Strict at $0/min.
Monthly CI Compute Spend
macOS Apple Silicon · 30,000 min/mo
Calculator models published 2026 PAYG rates (GitHub Actions, Blacksmith, Namespace, WarpBuild) vs $799 Mac mini M4 and $500 Linux baselines. Providers priced via AWS bills, concurrency seats, or colocation leases are compared directly in the table below.
Side-by-side comparison: Strict vs RunsOn
| Dimension | Strict | RunsOn |
|---|---|---|
| Execution target | Spare Apple Silicon Macs & Linux hosts (office, home, or colocated) | Ephemeral AWS EC2 Linux & Windows Spot instances in your VPC |
| macOS support | First-class macOS 15+ Apple Silicon app, launchd service, Xcode drift checks | AWS EC2 Mac requires 24-hour dedicated host minimum lock-in |
| Pricing model | $0/min software in Standalone mode; you own your hardware | RunsOn annual license + per-second AWS EC2, EBS, S3 cache & NAT charges |
| Build cache warmth | Persistent local NVMe DerivedData/Docker + $0 Tailnet Build Cache | Fresh EBS boot + S3/EFS magic cache upload/download per job |
| Isolation model | Dedicated persistent hosts with pre-job drain barriers & Tier 1–7 cleanup | Single-use ephemeral EC2 VM destroyed after every workflow job |
| Infrastructure footprint | Zero-sudo user service + tailscale serve | CloudFormation stack, AppRunner/Lambda webhook server, IAM, VPC subnets |
1-line YAML migration
Run strict add-runner owner/repo on your Mac or Linux box, then switch runs-on in .github/workflows/ci.yml.
jobs:
build:
- runs-on: runs-on=${{ github.run_id }}/runner=4cpu-linux-x64
+ runs-on: [self-hosted, Linux, X64]
Honest trade-offs
Choose Strict when
- You need native macOS Apple Silicon (iOS/Xcode/Swift) without AWS's 24-hour EC2 Mac minimum
- You already own Macs or Linux boxes and want zero AWS VPC/IAM/EBS bills
- You prefer warm local NVMe DerivedData and Docker layers over S3 cache hydration
Choose RunsOn when
- You run Linux/Windows CI on AWS and want ephemeral per-job Spot VMs for elasticity
- Untrusted public-fork PR isolation requires destroying the entire VM after every job
- You want elastic scaling to 50+ concurrent Linux builds with zero physical hardware
Frequently asked questions
Can Strict run macOS workflows better than AWS-based runners?
Yes. Because AWS requires a 24-hour minimum dedicated host lease for EC2 Mac instances, spare M4 Mac minis controlled by Strict deliver faster 10-core Apple Silicon builds at $0/min without 24h cloud billing lock-in.
Do I need an AWS account or CloudFormation template for Strict?
No. Strict Standalone runs on any Mac or Linux host behind tailscale serve with zero AWS infrastructure, VPCs, or NAT gateways.
Can a team use Strict for Macs and RunsOn for burst Linux Spot jobs?
Yes. Both use standard GitHub Actions workflow labels, so macOS jobs can target [self-hosted, macOS, ARM64] on Strict while elastic Linux bursts stay on cloud VMs.
Try Strict on one spare Mac in under two minutes
Signed Apple Silicon app or single-line CLI · Zero accounts required