# Namespace vs WarpBuild: prices, plans and limits (Nov 2026)

Namespace and WarpBuild side by side for ci runners: 8 terms differ. Every value links to the provider's own page.

## CI runners

| Term | Namespace | WarpBuild |
|---|---|---|
| Lowest price | $0.0015 /min (nscloud-ubuntu-24.04-amd64-1x2) | $0.003 /min (warp-ubuntu-latest-arm64-2x) |
| 5-min job | $0.015 (Linux x64, 2 vCPU · rank 7 of 16) | $0.02 (Linux x64, 2 vCPU · rank 11 of 16) |
| Billed | Per minute (metered: usage billed afterwards) | Per minute (metered: usage billed afterwards) |
| Sizes | 38 sizes (Linux, Windows, macOS · 1–32 vCPU) | 18 sizes (Linux, Windows, macOS · 2–32 vCPU) |
| Billing: Payment | Metered: usage billed afterwards [1] | Metered: usage billed afterwards [2] |
| Billing: Plan minimum | None [1] | None [2] |
| Billing: Billing increment | Per minute (rounded up) [1] | Per minute (rounded up) [2] |
| Billing: Minimum charge | 60 s [1] | 60 s [2] |
| Billing: Per-job fee | None [1] | None [2] |
| Limits: vCPU | unknown (Machine-shape and pricing pages do not say whether vCPUs are dedicated; only the site's llms.txt summary says 'dedicated compute, no shared tenancy') [3] | unknown (Docs say runners are ephemeral VMs; the x86-64 product page claims 'dedicated hardware resources' and 'baremetal' without stating whether vCPUs are dedicated) [4] |
| Limits: Concurrent jobs | unknown (Concurrency is capped in vCPU and RAM, not jobs: Developer plan 32 vCPU / 64 GB RAM for Linux, 12 vCPU / 28 GB for macOS) [3] | Unlimited [4] |
| Limits: Max job length | 3 h [3] | unknown (No job time limit on cloud runner docs, pricing or FAQ) [4] |
| Setup: Setup billed | No [3] | No [4] |
| Setup: Billed setup per job | 0 s [3] | 0 s [4] |
| Platform: CI systems | GitHub Actions, Buildkite [5] | GitHub Actions [6] |
| Platform: Hosting | Managed [5] | Managed [6] |
| Platform: Regions | unknown (Docs list no runner regions; API endpoints are per region 'such as us or eu') [5] | US, EU [6] |
| Free allowance: Minutes a month | None [7] | None [8] |
| Free allowance: Credit a month | None [7] | None [8] |
| Free allowance: One-time credit | unknown (30-day free trial of compute and GitHub runners; no dollar or minute amount published) [7] | $10 [8] |
| Cache: Included | None [7] | None [9] |
| Cache: Extra storage | unknown (Cache volumes are priced per GB-day ($0.0048) for storage plus $0.002 per GB-hour of snapshot use; no per-GB-month price published) [7] | $0.2 per GB-month [9] |
| Cache: Docker layer cache | Yes [7] | No [9] |
| Cache: Persistent disks | Yes [7] | Yes [9] |
| Features: SSH debugging | Yes [10] | Yes [11] |
| Features: Static IPs | Yes [10] | No [11] |
| Features: GPU runners | No [10] | No [11] |
| Features: SOC 2 | Yes [10] | Yes [11] |

### Namespace: plans and limits

- Developer: Free; at once ?, included 0 min, max job 3 h [12]
- Team: $100 /month; at once ?, included 100,000 min, max job 5 h [12]
- Business: $250 /month; at once ?, included 250,000 min, max job 24 h [12]
- Enterprise: unknown; at once ?, included ?, max job 24 h [12]

## Sources

[1] https://namespace.so/docs/architecture/compute/machine-shapes (checked 31 Oct 2026)
[2] https://www.warpbuild.com/pricing (checked 31 Oct 2026)
[3] https://namespace.so/docs/architecture/compute/resource-limits (checked 31 Oct 2026)
[4] https://www.warpbuild.com/answers/do-i-pay-for-queue-time-on-github-actions-runners (checked 31 Oct 2026)
[5] https://namespace.so/docs/reference/api (checked 31 Oct 2026)
[6] https://www.warpbuild.com/answers/can-i-keep-builds-in-the-eu-only (checked 31 Oct 2026)
[7] https://namespace.so/pricing (checked 31 Oct 2026)
[8] https://www.warpbuild.com/answers/what-happens-when-my-free-credits-run-out (checked 31 Oct 2026)
[9] https://www.warpbuild.com/docs/ci/features/caching (checked 31 Oct 2026)
[10] https://namespace.so/docs/workspaces/security (checked 31 Oct 2026)
[11] https://www.warpbuild.com/docs/ci/feature-matrix (checked 31 Oct 2026)
[12] https://namespace.so/pricing (checked 1 Nov 2026)