Find the plan that best fits your needs
30-day free trial of Compute, Devboxes, Github Runners, and more
Developer
Pay as you go
Get started with:
On demand compute
On demand Docker builds
Devboxes
Managed GitHub runners
Cloud image building
Cross-invocation caching
Get started
No credit card required
Team
$100per month
Everything from Developer, plus:
100,000 unit minutes
Shared across CI and remote builds
1,000 Docker builds
Devboxes
Pay as you go, billed separately
Increased concurrency
Email support
Get started
No credit card required
Business
Most Popular
$250per month
Everything from Team, plus:
250,000 unit minutes
Shared across CI and remote builds
2,500 Docker builds
Devboxes
Pay as you go, billed separately
High concurrency
Very large jobs and builds
Dedicated Slack channel
Get started
No credit card required
Enterprise
Custom
Everything from Business, plus:
Compute
Docker builds
Devboxes
Audit log export
Enterprise SSO
Custom log & metric sinks
Very high build concurrency
Contact us
Customized plan for higher demand
A closer look at each plan
Compute
Docker Builds
Devboxes
Bazel
Platform
Enterprise Support Add-on
Frequently asked questions
Have any question? Contact us.
Compute
Namespace accounts usage based on "compute units". A compute unit represents using 1 vCPU and 2GB of RAM for a minute times the platform multiplier (i.e. 1 for Linux).
For Linux, if you run an instance that has 4 vCPU and 8GB RAM for 5 minutes, then that's:
4 (vCPU) x 5 (minutes) x 1 (Linux multiplier) = 20 unit minutesFor Windows, running an instance with 2 vCPU and 4GB RAM for 6 minutes is:
2 (vCPU) x 6 (minutes) x 2 (Windows multiplier) = 24 unit minutesFor Mac, an instance with 6 vCPU and 14GB RAM running for 3 minutes is:
6 (vCPU) x 3 (minutes) x 10 (Mac multiplier) = 180 unit minutesWhile we account for a minimum of 1 minute, we always round the next 15 seconds down. For example, 30 seconds of usage is 1 billable minute, 70 seconds is 1 billable minute, and 150 seconds are billed as 3 minutes.
Unit minutes usage per shape can be found under "What is the unit minutes usage and price for each shape?" below.
For Linux and Windows, our standard shapes are multiples of 1 vCPU and 2GB RAM.
For shapes with a different ratio (i.e., 1 vCPU, 4GB RAM), compute units are calculated as:
For shapes with a different ratio (i.e., 1 vCPU, 4GB RAM), compute units are calculated as:
max(vCPU count, GB RAM divided by 2)For example, running a Linux instance on 8 vCPU and 32GB RAM for 2 minutes will be:
16 (32GB RAM / 2) x 2 (minutes) x 1 (Linux multiplier) = 32 unit minutesUnit minutes usage per shape can be found under "What is the unit minutes usage and price for each shape?" below.
Jobs that run on Windows or macOS consume minutes at a higher rate than jobs on Linux, they consume 2x and 10x the rate respectively.
| Platform | Multiplier |
|---|---|
| Linux | 1 |
| Windows | 2 |
| macOS | 10 |
| Linux on Apple Silicon | 7 |
Below is a breakdown of the cost of each machine shape per platform. Prepaid cost is the effective cost of minutes in your plan, overage is the cost of any usage that exceeds your plan.
| vCPU | RAM | Machine shape | Multiplier | Prepaid | Overage |
|---|---|---|---|---|---|
1 vCPU2 GB | $0.001 / min | $0.0015 / min | |||
2 vCPU4 GB | $0.002 / min | $0.003 / min | |||
2 vCPU8 GB | $0.004 / min | $0.006 / min | |||
4 vCPU8 GB | $0.004 / min | $0.006 / min | |||
4 vCPU16 GB | $0.008 / min | $0.012 / min | |||
8 vCPU16 GB | $0.008 / min | $0.012 / min | |||
8 vCPU32 GB | $0.016 / min | $0.024 / min | |||
16 vCPU32 GB | $0.016 / min | $0.024 / min | |||
16 vCPU64 GB | $0.032 / min | $0.048 / min | |||
32 vCPU64 GB | $0.032 / min | $0.048 / min | |||
32 vCPU128 GB | $0.064 / min | $0.096 / min | |||
32 vCPU256 GB | $0.128 / min | $0.192 / min | |||
32 vCPU512 GB | $0.256 / min | $0.384 / min | |||
64 vCPU128 GB | $0.08 / min | $0.12 / min | |||
64 vCPU256 GB | $0.16 / min | $0.24 / min | |||
64 vCPU512 GB | $0.32 / min | $0.48 / min |
| vCPU | RAM | Machine shape | Multiplier | Prepaid | Overage |
|---|---|---|---|---|---|
1 vCPU2 GB | $0.002 / min | $0.003 / min | |||
2 vCPU4 GB | $0.004 / min | $0.006 / min | |||
2 vCPU8 GB | $0.008 / min | $0.012 / min | |||
4 vCPU8 GB | $0.008 / min | $0.012 / min | |||
4 vCPU16 GB | $0.016 / min | $0.024 / min | |||
8 vCPU16 GB | $0.016 / min | $0.024 / min | |||
8 vCPU32 GB | $0.032 / min | $0.048 / min | |||
16 vCPU32 GB | $0.032 / min | $0.048 / min | |||
16 vCPU64 GB | $0.064 / min | $0.096 / min | |||
32 vCPU128 GB | $0.128 / min | $0.192 / min | |||
32 vCPU256 GB | $0.256 / min | $0.384 / min | |||
32 vCPU512 GB | $0.512 / min | $0.768 / min |
| vCPU | RAM | Machine shape | Multiplier | Prepaid | Overage |
|---|---|---|---|---|---|
4 vCPU7 GB | $0.04 / min | $0.06 / min | |||
6 vCPU14 GB | $0.06 / min | $0.09 / min | |||
6 vCPU28 GB | $0.075 / min | $0.1125 / min | |||
8 vCPU14 GB | $0.08 / min | $0.12 / min | |||
12 vCPU28 GB | $0.12 / min | $0.18 / min | |||
12 vCPU56 GB | $0.18 / min | $0.27 / min | |||
16 vCPU28 GB | $0.16 / min | $0.24 / min | |||
16 vCPU56 GB | $0.2 / min | $0.3 / min |
| vCPU | RAM | Machine shape | Multiplier | Prepaid | Overage |
|---|---|---|---|---|---|
2 vCPU4 GB | $0.014 / min | $0.021 / min | |||
2 vCPU8 GB | $0.028 / min | $0.042 / min | |||
4 vCPU8 GB | $0.028 / min | $0.042 / min | |||
4 vCPU12 GB | $0.042 / min | $0.063 / min | |||
4 vCPU16 GB | $0.056 / min | $0.084 / min | |||
6 vCPU12 GB | $0.042 / min | $0.063 / min | |||
6 vCPU14 GB | $0.049 / min | $0.0735 / min | |||
8 vCPU16 GB | $0.056 / min | $0.084 / min | |||
8 vCPU32 GB | $0.112 / min | $0.168 / min | |||
12 vCPU16 GB | $0.084 / min | $0.126 / min | |||
12 vCPU24 GB | $0.084 / min | $0.126 / min | |||
12 vCPU32 GB | $0.112 / min | $0.168 / min | |||
12 vCPU56 GB | $0.196 / min | $0.294 / min | |||
16 vCPU32 GB | $0.112 / min | $0.168 / min | |||
16 vCPU56 GB | $0.196 / min | $0.294 / min |
We invest heavily in the best infrastructure. Something we care deeply about. We deploy our own hardware across various sites which allows us to offer fantastic performance and price.
Linux and Windows amd64 workflows are running on high-performance AMD EPYC CPUs.
Linux arm64 workloads are running on AmpereOne or on Apple Silicon.
For macOS, most of your workloads are running on Apple M5 Max and some on Apple M4 Pro.
Up-to-date usage reports are available in the Dashboard, and are calculated in real time. Check out your current usage here.
To better understand your usage, click on the ‘Explore’ button on the Usage page to break down and filter usage (per platform, shape, GitHub Repository, etc.).
For GitHub jobs, you can check out the Insights page to look at the Duration or Queue time of all GitHub workloads run on Namespace, with breakdowns and filters.
To improve your performance and cost, you can consider:
- Are you using the right shape for your workflows?
Larger may be faster, smaller may be cheaper if your runner is oversized. - Are you running on Namespace standard shapes (ratio of 1vCPU : 2GB RAM)?
This will give you the best price for your usage. - Are you using cache effectively?
Our support team is here to help you optimize your setup.
Windows runners are generally available and included in our current standard Team, Business, and Business+ plans.
You can now run your Linux arm64 workflows on Apple Silicon! This feature is still in early access and not all Namespace features may be available yet. The list of available instance shapes is not final yet. Having said that - some of our early customers report unmatched single-core performance for their workloads.
To get access, reach out to support@namespace.so
Devboxes
The tables below show how many vCPUs each devbox shape can boost to and how much RAM it has.
| Size | Max vCPU | RAM (GB) |
|---|---|---|
| S | 4 | 8 |
| M | 8 | 16 |
| L | 16 | 32 |
| XL | 32 | 64 |
| Size | Max vCPU | RAM (GB) |
|---|---|---|
| M | 6 | 14 |
| L | 12 | 28 |
You pay for two things: the Devbox Minutes your Devboxes consume and the persistent storage they use.
Devbox Minutes
Devbox Minutes cost $0.004 each. Larger shapes consume more Devbox Minutes per minute of actual usage. For example, a medium Linux Devbox uses 2 Devbox Minutes per minute.
| Size | Devbox Minutes |
|---|---|
| S | 1 |
| M | 2 |
| L | 4 |
| XL | 8 |
| Size | Devbox Minutes |
|---|---|
| M | 15 |
| L | 30 |
Persistent Storage
Persistent storage is billed for the storage used at $0.20 per GB-month. You are not charged for the provisioned volume size. For example, a Devbox with a 100 GB volume that holds 20 GB of data is billed for 20 GB.
No, Devbox usage is billed separately in Devbox Minutes and follows a pay-as-you-go model by default. Reach out for a custom plan with included usage at a volume discount.
If you're no longer using your devbox, it will automatically shut down after 15 minutes. You can adjust the default timeout or manually stop your devbox at any time.
Each user and each workspace can have a limited number of Devboxes at a time.
| Plan | Per user | Per workspace |
|---|---|---|
| Developer | 1 | 3 |
| Team | 3 | 30 |
| Business | 5 | 50 |
| Devbox Plus | 5 | 50 |
| Custom | custom | custom |
The limit counts both running and stopped Devboxes.
If you need higher limits, reach out to support@namespacelabs.com.
Billing & Storage
When you sign up, you get access to the Developer plan for 30 days. This includes:
- On-demand compute
- Docker builds
- Devboxes
- Cross-invocation caching
- Managed GitHub runners
If you need higher limits during your trial, contact us.
Namespace offers a host of high-performance caching solutions that lead to major speed-ups during test setup and hence lower your usage in terms of unit minutes. Since our caches are backed by high-performance local storage, they are even faster. Our integrated caching solutions (e.g. Bazel, Turborepo) seamlessly integrate with your tooling and provide very high cache hit ratios ensuring consistently fast workflows. Get started.
To use cache volumes effectively, you’ll need to run some workloads for the cache to be filled and widely available. The more regularly you use your cache volumes, the higher the probability of a cache hit and the higher the savings on compute time.
Namespace uses storage to offer high-performance caching solutions and a built-in private container registry. Storage usage is accounted in blocks of 100 GB. You can also see storage usage and cache hit ratios on your usage page.
When you attach a cache volume to an instance, we calculate the cost based on two factors: how long your instance was running and the total storage capacity of the cache volume.
This gives us a measurement in GB-hours. For example, if your instance runs for one hour with a 100 GB cache volume attached, you'll be charged for 100 GB-hours.
If you run an instance for 3 hours with a 50 GB cache volume attached, the calculation would be 50 GB × 3 hours = 150 GB-hours.
Bazel is available on Developer, Team, and Business plans. Cache hits cost $0.10 per 1,000 hits. Remote execution is powered by high-performance Namespace compute co-located with the cache and is billed per minute based on compute and storage time. CAS storage costs $0.20 / GB-month. Most workspaces pay $0 for CAS reads. Included traffic is the greater of 100 GB or 2 GB per 1,000 Action Cache hits, and additional traffic costs $100 / TB. Enterprise contracts can include volume discounts.