Prices read from Namespace's own pages on 1 October 2026
Namespace pricing: unit minutes, plans and runner rates
Namespace bills compute in unit minutes: one vCPU with 2 GB of RAM for one minute, multiplied by 2 for Windows and 10 for macOS. Each machine shape has two published prices, a prepaid rate for minutes covered by your plan and a higher overage rate for usage beyond it.
We run no affiliate links and earn nothing from Namespace. Every figure below is copied from Namespace's published pricing and links to its source; nothing is estimated. Read the methodology.
THE SHORT VERSION · 1 OCTOBER 2026
Plans
| Plan | Price | Unit minutes | Linux concurrency | macOS concurrency | Max job |
|---|---|---|---|---|---|
| Developer | $0, pay as you go | Pay per use | 32 vCPU | 12 vCPU | 3 hours[1] |
| Team | $100/month | 100,000 | 64 vCPU | 24 vCPU | 5 hours[1] |
| Business | $250/month | 250,000 | 160 vCPU | 48 vCPU | 24 hours[1] |
| Enterprise | Custom | Custom | Custom | Custom | 24 hours[1] |
Namespace's FAQ says Windows runners are included in the Team, Business and Business+ plans. Linux on Apple Silicon is not offered on Developer.
Runner rates by machine shape
Namespace publishes one Linux table that covers both AMD64 and ARM64 at a multiplier of 1. Prepaid is the effective cost of minutes in your plan; overage is the cost of usage beyond it.
| Platform | Shape | Unit minutes per minute | Prepaid | Overage |
|---|---|---|---|---|
| Linux | 1 vCPU, 2 GB | 1 | $0.001 | $0.0015[1] |
| Linux | 2 vCPU, 4 GB | 2 | $0.002 | $0.003[1] |
| Linux | 4 vCPU, 8 GB | 4 | $0.004 | $0.006[1] |
| Linux | 8 vCPU, 16 GB | 8 | $0.008 | $0.012[1] |
| Linux | 16 vCPU, 32 GB | 16 | $0.016 | $0.024[1] |
| Windows | 2 vCPU, 4 GB | 4 | $0.004 | $0.006[1] |
| macOS | 4 vCPU, 7 GB | 40 | $0.04 | $0.06[1] |
| macOS | 6 vCPU, 14 GB | 60 | $0.06 | $0.09[1] |
| macOS | 12 vCPU, 28 GB | 120 | $0.12 | $0.18[1] |
Shapes that are not 1 vCPU to 2 GB are charged on whichever is larger, vCPUs or GB of RAM divided by 2: a 2 vCPU, 8 GB Linux shape counts as 4 units ($0.004 prepaid). Linux on Apple Silicon has its own table at a multiplier of 7.
Namespace against GitHub-hosted runners
Namespace's prepaid rate applies to minutes inside a Team or Business plan. Both prepaid and overage rates are shown against GitHub's rate for the nearest runner.
| Runner | Namespace | GitHub-hosted | Difference |
|---|---|---|---|
| Linux x86, 2 vCPU (prepaid) | $0.002[1] | $0.006 (2-core)[3] | -67% |
| Linux x86, 2 vCPU (overage) | $0.003[1] | $0.006 (2-core)[3] | -50% |
| Linux ARM64, 2 vCPU (prepaid) | $0.002[1] | $0.005 (2-core arm64)[3] | -60% |
| Linux, 4 vCPU 8 GB (prepaid) | $0.004[1] | $0.012 (4-core)[3] | -67% |
| Windows, 2 vCPU (prepaid) | $0.004[1] | $0.010 (2-core)[3] | -60% |
| macOS 4 vCPU (prepaid) | $0.04[1] | $0.062 (3-4 core)[3] | -35% |
| macOS 4 vCPU (overage) | $0.06[1] | $0.062 (3-4 core)[3] | -3% |
Difference = Namespace rate against the GitHub-hosted rate in the same row; negative means Namespace is cheaper per minute. GitHub rates from our GitHub Actions pricing page, re-read from GitHub's docs on 1 October 2026. Shapes are not identical across vendors, so compare like with like where a row says so.
WORKED EXAMPLE: Linux minutes on the 2 vCPU, 4 GB shape (2 unit minutes per minute)
List prices only. The GitHub figures are before any minutes your GitHub plan includes. Below roughly 16,700 minutes a month on this shape, GitHub-hosted at $0.006 costs less than the $100 Team fee.
Inside a plan, Namespace's Linux and Windows rates sit well below GitHub-hosted. On the 2 vCPU Linux shape the $100 Team plan costs less than GitHub-hosted once you run more than about 16,700 minutes a month, and it covers up to 50,000 minutes before overage starts.
On macOS the overage rate for the smallest shape is within a few percent of GitHub's, so the saving on Mac work comes from staying inside plan minutes, which draw down at 10 units per vCPU-minute.
Billing details that change the bill
macOS consumes unit minutes at 10x and Windows at 2x, so 100,000 Team units cover 2,500 minutes on the 4 vCPU macOS shape.[1]
Billing has a one-minute minimum per job, then rounds: 30 seconds bills as 1 minute, 70 seconds as 1 minute, 150 seconds as 3 minutes.[1]
Shapes with more than 2 GB of RAM per vCPU are charged on memory: 2 vCPU with 8 GB counts as 4 units, double the 2 vCPU, 4 GB shape.[1]
Cache volumes are metered separately: on Developer, snapshots at $0.002 per GB-hour and storage at $0.0048 per GB-day, with free allowances on Team and Business.[1]
Frequently asked questions
How much does Namespace cost?+
What is a Namespace unit minute?+
Does Namespace have a free tier?+
Are Namespace ARM runners priced differently from x86?+
How much are Namespace macOS runners?+
SOURCES · ALL READ 1 OCTOBER 2026
- [1]Namespace pricing page: https://namespace.so/pricing, read 1 October 2026.
- [2]Namespace pricing, machine-readable version: https://namespace.so/pricing.md, read 1 October 2026.
- [3]GitHub Docs, Actions runner pricing: https://docs.github.com/en/billing/reference/actions-runner-pricing, read 1 October 2026.
Vendors change prices without notice. If a figure here no longer matches Namespace's page, the vendor page wins; tell us and we will re-read it.