Strict Compare
vs Namespace Updated November 2026

Strict vs Namespace

Skip $100/month Team commitments and unit-minute multipliers by running Strict directly on your own Macs and Linux hosts.

Namespace offers fast microVMs and remote cache volumes priced via unit-minutes. At 30,000 macOS minutes/month, Namespace’s 40 u-min/min multiplier equals 1.2M unit-minutes ($1,750/mo)—more than two brand-new Mac mini M4 machines every single month.

Base subscription $0 vs $100/mo Strict standalone has zero accounts
macOS effective rate $0 vs $0.060/min 40 unit-min/min overage rate
Payback @ 30k 14 days $799 Mac mini vs $1,750/mo
Cache egress $0 Tailnet Local NVMe + shared Actions cache

Unit-minute cost breakdown vs Strict

Namespace Team includes 100,000 unit-minutes in its $100/mo fee and bills $0.0015 per additional unit-minute (40 u-min/min for 4-vCPU macOS; 4 u-min/min for 4-vCPU Linux).

Strict vs Namespace Monthly Bill

macOS Apple Silicon · 30,000 min/mo

Save $1,750/mo
30,000 min / mo

Notice that at 10,000 Linux 4-vCPU min/mo (40k u-min), Namespace fits inside its $100/mo Team minimum while macOS builds burn the included 100k pool in 2,500 minutes.

Feature comparison

Dimension Strict Namespace
Control plane Single Bun server behind tailscale serve (or optional Worker/DO) Hosted SaaS platform ($100/mo Team minimum)
macOS compute Native bare-metal M1–M4 hardware 4-vCPU macOS instances (40 u-min/min)
Shared caching ACTIONS_CACHE_URL over Tailscale + local NVMe Namespace Cache Volumes & Bazel/Docker remote cache
Load balancing Supply-side slot draining across your hosts per repo pool Cloud scheduler across Namespace fleet
Toolchain safety Cross-host Xcode/Swift drift detection + 9 doctor checks Immutable VM base images

Switch from Namespace labels in one line

.github/workflows/ci.yml
jobs:
  build:
-   runs-on: namespace-profile-macos-arm64
+   runs-on: [self-hosted, macOS, ARM64]

Honest trade-offs

Choose Strict when

  • You run macOS/iOS CI regularly and want $0/min on 10+ native cores instead of unit-minute overages.
  • You prefer owning your build fleet behind Tailscale without monthly SaaS base fees.

Choose Namespace when

  • You specifically rely on Namespace’s remote Bazel/Gradle CAS or ephemeral multi-tenant microVM APIs outside GitHub Actions.
  • You have no desire to plug in any dedicated Mac or Linux hardware.

Frequently asked questions

How does Strict compare to Namespace unit-minute billing?

Namespace Team charges $100/month (including 100k unit-minutes) plus $0.0015 per additional unit-minute at 40 unit-min/min for macOS ($1,750/month at 30k macOS minutes), while Strict charges $0 base fee and $0/min on your own hardware.

Do I need to configure remote cache volumes with Strict?

No. Your machines retain warm local NVMe DerivedData, Cargo, Bun, and Docker layers automatically, plus zero-egress Tailnet cache sharing across peers.

When should teams keep Namespace?

Keep Namespace if you rely on its managed remote Bazel/Gradle CAS APIs or want ephemeral multi-tenant microVMs without plugging in local hardware.