Short answer
Namespace was not measured in CI Bench v1, so the speed and cost-per-job figures below are each option's result against GitHub-hosted (ubuntu-latest), not against Namespace. Measured managed options: Vitko Runners (warm starts + test splitting) 2.3x faster at 84% lower cost per job; Vitko Runners 1.7x faster at 84% lower cost per job; Blacksmith 1.6x faster at 52% lower cost per job; Ubicloud 1.1x faster at 83% lower cost per job. Maintained by Vitko, Inc., which sells one of the products measured.
What Namespace publishes
Not yet measured in CI Bench v1 (Namespace joins in the next result set), so there is no measured speed or cost-per-job figure for Namespace.
| Topic | What its page says | Source |
|---|---|---|
| Price | Billed in unit minutes (1 vCPU and 2 GB for a minute). Linux 2 vCPU 4 GB $0.002 a minute prepaid, $0.003 overage; 2 vCPU 8 GB $0.004 / $0.006; 4 vCPU 16 GB $0.008 / $0.012. | Namespace pricing, read 2026-10-27 |
| Plans | Developer: pay as you go; Team $100 a month with 100,000 unit minutes; Business $250 a month with 250,000. | Namespace pricing, read 2026-10-27 |
| Billing granularity | A minimum of 1 minute, then usage is rounded down to the nearest 15 seconds, per its FAQ. | Namespace pricing, read 2026-10-27 |
| Platforms it lists | Managed GitHub runners for Linux AMD64 and ARM64, macOS on Apple Silicon, and Windows. | Namespace pricing, read 2026-10-27 |
Alternatives measured on 12 real CI workloads
| Configuration | Type | Speed vs GitHub-hosted (ubuntu-latest) | Cost per job vs GitHub-hosted (ubuntu-latest), 10,000 jobs a month | List $ per minute (2 vCPU) |
|---|---|---|---|---|
| Vitko Runners (warm starts + test splitting)Vitko | Managed | 2.3x faster | 84% lower | $0.002 |
| Vitko RunnersVitko | Managed | 1.7x faster | 84% lower | $0.002 |
| GitHub-hosted larger runner (4 vCPU) | Managed | 1.6x faster | 39% higher | $0.012 |
| Blacksmith | Managed | 1.6x faster | 52% lower | $0.004 |
| Self-hosted runners on Google Cloud | Self-hosted | 1.5x faster | 59% lower | your cloud bill |
| RunsOn | Self-hosted | 1.2x faster | 75% lower | your cloud bill |
| Self-hosted runners on AWS (one VM per job) | Self-hosted | 1.2x faster | 60% lower | your cloud bill |
| Ubicloud | Managed | 1.1x faster | 83% lower | $0.00125 |
Speed and cost are the indexes in results.json (geometric mean over 12 workloads, each against GitHub-hosted (ubuntu-latest)); list prices dated 2026-10-05. List price per minute is not cost per job; faster runners finish sooner. Self-hosted options spread fixed monthly costs over the volume.
Other providers, published facts only
- Depot: Not measured in v2: Depot runners were assigned but did not start jobs for our account during the test window (checks on 2026-10-01 and 2026-10-24). List price $0.006 a minute (2 vCPU).
- WarpBuild: Not benchmarked List price $0.004 a minute (2 vCPU).
- BuildJet: Shut down (per its own docs, read 2026-10-24). List price $0.004 a minute (2 vCPU).
- Sengi: Not measured. List price $0.003 a minute (2 vCPU).
- CRACI: Not measured. List price $0.004 a minute (2 vCPU).
When another option may fit better
- If you need macOS or Windows runners: Namespace lists them; Vitko Runners does not.
- If you want one subscription that also covers Docker builds: Namespace plans share unit minutes across CI and remote builds, per its pricing page.
- If you want per-second billing with no minimum: check each provider’s granularity in the table.
More: 12 options compared · ranked by speed · ranked by cost per job · price per minute, 2 and 4 vCPU · list prices · free minutes. Alternatives to: Blacksmith · Depot · RunsOn · Ubicloud · WarpBuild · Namespace · BuildJet.
Namespace's pages may have changed since October 27, 2026; they are the authority. Method: how the runs were made; data: results.json; every raw record: the repository. Maintained by Vitko, Inc., which sells one of the products measured. Page dated October 27, 2026.