# Namespace Pricing

> Source: https://namespace.so/pricing
> Generated at: 2026-09-22T00:57:46.702Z

Namespace provides cloud compute infrastructure for CI/CD, Docker builds, and cloud dev environments.

---

## Plans

- **Developer**: $0 Pay as you go
- **Team**: $100 per month
- **Business**: $250 per month
- **Enterprise**: Custom Volume discounting

## Plan Comparison

### Compute

| | Developer | Team | Business | Enterprise |
|---|---|---|---|---|
| **Unit minutes** | Pay per use | 100,000 included | 250,000 included | Custom |
| **Managed GitHub Runners** | ✓ | ✓ | ✓ | ✓ |
| **Ephemeral environments** | ✓ | ✓ | ✓ | ✓ |
| **Linux AMD64 & ARM64** | ✓ | ✓ | ✓ | ✓ |
| **macOS on Apple Silicon** | ✓ | ✓ | ✓ | ✓ |
| **Windows runners** | ✗ | ✓ | ✓ | ✓ |
| **Linux on Apple Silicon** | ✗ | ✓ | ✓ | ✓ |
| **Max instance duration** | 3 hours | 5 hours | Up to 24 hours | Up to 24 hours |
| **Concurrency (Linux)** | 32 vCPU | 64 vCPU | 160 vCPU | Custom |
| **Concurrency (macOS)** | 12 vCPU | 24 vCPU | 48 vCPU | Custom |
| **Access to larger shapes** | ✗ | ✗ | ✓ | ✓ |
| **High-memory instances** | ✗ | ✗ | ✗ | ✓ |

### Docker Builds

| | Developer | Team | Business | Enterprise |
|---|---|---|---|---|
| **Included builds** | Pay per use | 1,000 | 2,500 | Custom |
| **Developer rate** | $0.05/build | — | — | — |
| **Extra builds rate** | — | $10 per 1,000 | $10 per 1,000 | Custom |
| **Cross-invocation caching** | ✓ | ✓ | ✓ | ✓ |
| **Larger Docker builders** | ✗ | ✗ | ✓ | ✓ |
| **Very high build concurrency** | ✗ | ✗ | ✗ | ✓ |

### Devboxes

| | Developer | Team | Business | Enterprise |
|---|---|---|---|---|
| **Cloud dev environments** | ✓ | ✓ | ✓ | ✓ |
| **Starting rate** | $0.004/min | $0.004/min | $0.004/min | Custom |
| **Sizes available** | S, M, L, XL | S, M, L, XL | S, M, L, XL | Custom |

### Bazel

| | Developer | Team | Business | Enterprise |
|---|---|---|---|---|
| **Cache hits** | $0.10 per 1,000 | $0.10 per 1,000 | $0.10 per 1,000 | Volume discount |
| **Remote execution time** | Usage based per minute | Usage based per minute | Usage based per minute | Volume discount |
| **CAS storage** | $0.20/GB-month | $0.20/GB-month | $0.20/GB-month | Volume discount |
| **CAS reads** | Included | Included | Included | Volume discount |

### Platform

| | Developer | Team | Business | Enterprise |
|---|---|---|---|---|
| **Cache volume snapshots** | $0.002/GB-hr | 5,000 GB-hr free | 15,000 GB-hr free | Custom |
| **Cache volume storage** | $0.0048/GB-day | 3,000 GB-day free | 9,000 GB-day free | Custom |
| **Container Registry** | $0.2/GB-mo | $0.2/GB-mo | $0.2/GB-mo | Custom |
| **Turborepo cache** | $0.2/GB-mo | $0.2/GB-mo | $0.2/GB-mo | Custom |
| **GitHub Artifacts** | $0.2/GB-mo | $0.2/GB-mo | $0.2/GB-mo | Custom |
| **Gradle cache** | $0.2/GB-mo | $0.2/GB-mo | $0.2/GB-mo | Custom |
| **Root & privileged access** | ✓ | ✓ | ✓ | ✓ |
| **GitHub Actions federation** | ✓ | ✓ | ✓ | ✓ |
| **Audit log retention** | 7 days | 7 days | 30 days | Custom |
| **Dedicated Slack channel** | ✗ | ✗ | ✓ | ✓ |
| **Role-based access control** | ✗ | ✗ | ✓ | ✓ |

### Enterprise Support Add-on

| | Developer | Team | Business | Enterprise |
|---|---|---|---|---|
| **Enterprise SSO** | ✗ | ✗ | ✗ | ✓ |
| **Custom log & metric sinks** | ✗ | ✗ | ✗ | ✓ |
| **Dedicated egress pools** | ✗ | ✗ | ✗ | ✓ |
| **Custom roles** | ✗ | ✗ | ✗ | ✓ |

---

## Compute Shape Pricing

A compute unit = 1 vCPU + 2 GB RAM for 1 minute × platform multiplier.

| Platform | Multiplier |
|---|---|
| Linux | 1x |
| Windows | 2x |
| macOS | 10x |
| Linux on Apple Silicon | 7x |

**Example**: 4 vCPU Linux instance for 5 min = 4 × 5 × 1 = 20 unit minutes.

### Linux

| vCPU | RAM | Multiplier | Prepaid | Overage |
|---|---|---|---|---|
| 1 | 2 GB | 1 | $0.001/min | $0.0015/min |
| 2 | 4 GB | 2 | $0.002/min | $0.003/min |
| 2 | 8 GB | 4 | $0.004/min | $0.006/min |
| 4 | 8 GB | 4 | $0.004/min | $0.006/min |
| 4 | 16 GB | 8 | $0.008/min | $0.012/min |
| 8 | 16 GB | 8 | $0.008/min | $0.012/min |
| 8 | 32 GB | 16 | $0.016/min | $0.024/min |
| 16 | 32 GB | 16 | $0.016/min | $0.024/min |
| 16 | 64 GB | 32 | $0.032/min | $0.048/min |
| 32 | 64 GB | 32 | $0.032/min | $0.048/min |
| 32 | 128 GB | 64 | $0.064/min | $0.096/min |
| 32 | 256 GB | 128 | $0.128/min | $0.192/min |
| 32 | 512 GB | 256 | $0.256/min | $0.384/min |
| 64 | 128 GB | 80 | $0.08/min | $0.12/min |
| 64 | 256 GB | 160 | $0.16/min | $0.24/min |
| 64 | 512 GB | 320 | $0.32/min | $0.48/min |

### Windows

| vCPU | RAM | Multiplier | Prepaid | Overage |
|---|---|---|---|---|
| 1 | 2 GB | 2 | $0.002/min | $0.003/min |
| 2 | 4 GB | 4 | $0.004/min | $0.006/min |
| 2 | 8 GB | 8 | $0.008/min | $0.012/min |
| 4 | 8 GB | 8 | $0.008/min | $0.012/min |
| 4 | 16 GB | 16 | $0.016/min | $0.024/min |
| 8 | 16 GB | 16 | $0.016/min | $0.024/min |
| 8 | 32 GB | 32 | $0.032/min | $0.048/min |
| 16 | 32 GB | 32 | $0.032/min | $0.048/min |
| 16 | 64 GB | 64 | $0.064/min | $0.096/min |
| 32 | 128 GB | 128 | $0.128/min | $0.192/min |
| 32 | 256 GB | 256 | $0.256/min | $0.384/min |
| 32 | 512 GB | 512 | $0.512/min | $0.768/min |

### macOS (Apple Silicon)

| vCPU | RAM | Multiplier | Prepaid | Overage |
|---|---|---|---|---|
| 4 | 7 GB | 40 | $0.04/min | $0.06/min |
| 6 | 14 GB | 60 | $0.06/min | $0.09/min |
| 6 | 28 GB | 75 | $0.075/min | $0.1125/min |
| 8 | 14 GB | 80 | $0.08/min | $0.12/min |
| 12 | 28 GB | 120 | $0.12/min | $0.18/min |
| 12 | 56 GB | 180 | $0.18/min | $0.27/min |
| 16 | 28 GB | 160 | $0.16/min | $0.24/min |
| 16 | 56 GB | 200 | $0.2/min | $0.3/min |

### Linux on Apple Silicon (shapes may differ during early access)

| vCPU | RAM | Multiplier | Prepaid | Overage |
|---|---|---|---|---|
| 6 | 14 GB | 49 | $0.049/min | $0.0735/min |
| 12 | 28 GB | 98 | $0.098/min | $0.147/min |
| 12 | 56 GB | 196 | $0.196/min | $0.294/min |

---

## Devbox Sizes

| Size | Max vCPU | RAM | Price/min |
|---|---|---|---|
| S | 4 | 8 GB | $0.004 |
| M | 8 | 16 GB | $0.008 |
| L | 16 | 32 GB | $0.016 |
| XL | 32 | 64 GB | $0.032 |

Auto-suspend after 15 minutes of inactivity. Timeout is configurable.

---

## Hardware

- **Linux/Windows AMD64**: AMD EPYC CPUs
- **Linux ARM64**: AmpereOne or Apple Silicon
- **macOS**: Apple M4 Pro (some on M2 Pro)

---

## FAQ

### Compute

**Q: What are unit minutes?**

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).

**Q: How are unit minutes calculated?**

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 minutes`

For 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 minutes`

For 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 minutes`

While 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.

**Q: What is a standard shape?**

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: `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 minutes`

**Q: How are Linux, Windows and macOS priced?**

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 |

**Q: What hardware are your workflows running on?**

We invest heavily in the best infrastructure. Linux and Windows amd64 workflows are running on high-performance **AMD EPYC CPUs**. Linux arm64 workloads are running on **AmpereOne** or **Apple Silicon**. For macOS, most workloads are running on **Apple M4 Pro** and some on **Apple M2 Pro**.

**Q: How can I understand my usage and improve performance / cost?**

Up-to-date usage reports are available in the Dashboard, and are calculated in real time. Check out your current usage at https://cloud.namespace.so/workspace/usage/.

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 at https://cloud.namespace.so/workspace/ghrunners/insights 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, 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 (support@namespace.so) is here to help you optimize your setup.

**Q: Which plans include Windows runners?**

Windows runners are generally available and included in our current standard Team, Business, and Business+ plans.

**Q: How can I join the early access to Linux runners on Apple Silicon?**

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. Some early customers report unmatched single-core performance for their workloads.

To get access, reach out to support@namespace.so.

### Devboxes

**Q: How many vCPUs does each Devbox shape boost to?**

| Size | Max vCPU |
|---|---|
| S | 4 |
| M | 8 |
| L | 16 |
| XL | 32 |

**Q: How many GB RAM are assigned to each Devbox shape?**

| Size | GB RAM |
|---|---|
| S | 8 |
| M | 16 |
| L | 32 |
| XL | 64 |

**Q: Does my Devbox shut down automatically?**

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.

**Q: How is Devbox usage billed?**

Devbox usage is billed per minute based on the shape you select. The per-minute pricing without any discount is as follows:

| Size | Price per minute |
|---|---|
| S | $0.004 |
| M | $0.008 |
| L | $0.016 |
| XL | $0.032 |

### Billing & Storage

**Q: How does caching help?**

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: https://namespace.so/docs/solutions/github-actions/caching

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.

**Q: How is storage billed?**

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 at https://cloud.namespace.so/workspace/usage?focus=storage.

**Q: How is the Cache Volume Snapshot Usage billed?**

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.

**Q: How can I enable Bazel and how is it billed?**

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.


---

## Links

- Sign up: https://cloud.namespace.so
- Documentation: https://namespace.so/docs
- Contact sales: sales@namespace.so
- Support: support@namespace.so