CI Runnerscirunners.org
Runner profile · Managed runner service

Namespace

Answer in brief

Managed runners for GitHub Actions and Buildkite on the vendor’s own hardware, configured through profiles with persistent cache volumes. A managed runner platform for GitHub Actions and Buildkite on vendor-operated hardware, suited to teams that want per-job VMs, persistent cache volumes and all three operating systems.

By the CI Runners editors · Updated

Overview

Namespace runs CI jobs on a compute platform it operates on its own hardware. For GitHub Actions, a team connects its organization, defines runner profiles that fix the OS, architecture, machine shape and caching, and points runs-on at a profile label. Namespace says every job runs in its own virtual machine that is discarded when the job ends. The same platform provides ephemeral Buildkite agents, remote Docker builders, Bazel remote execution and Devboxes.

Caching is built around Cache Volumes that persist between runs and are shared by all jobs using a profile, with optional protection so only chosen branches can write. Usage is billed in unit minutes that scale with vCPU count and a platform multiplier, and plans set concurrency and instance-duration limits. Debugging options include a dashboard terminal, a breakpoint action and VNC or RDP sessions. Egress policies and stable egress IP ranges are documented; dedicated egress pools are for enterprise customers.

Notable

  • Namespace announced a $42M Series B led by Scale Venture Partners on 5 October 2026, bringing total funding to $65M.
  • The Series B post says the Series A, led by NEA, was raised seven months earlier.
  • Git Snapshots for GitHub Actions and Buildkite runners were announced on 30 September 2026.
  • A post dated 5 May 2026 describes Namespace’s security model: one VM per job, discarded when the job ends.

Namespace specifications

AttributeDetails
CI systemsGitHub Actions, Buildkite
Operating systemsLinux, macOS, Windows
Architecturesx64, arm64
DeploymentManaged runner service
IsolationEvery job runs in its own instance inside a virtual machine that is discarded when the job ends; the hypervisor is not named
Fresh environment per jobYes
HardwareNamespace says it deploys its own hardware in its own racks: AMD EPYC for Linux and Windows amd64, AmpereOne for Linux arm64 (Linux on Apple Silicon is in early access), and Apple M4 Pro and M5 Max for macOS.
Performance (vendor claim)Not documented
Runner sizesLinux up to 64 vCPU and 512 GB RAM, Windows up to 32 vCPU and 512 GB, macOS up to 16 vCPU and 56 GB; standard label shapes run from 2 vCPU / 4 GB to 32 vCPU / 64 GB, and instances over 64 GB RAM need special access
CachingCache Volumes persist data across runs; a runner profile can cache container images, toolchain downloads, action downloads and Git checkouts, and nscloud-cache-action replaces actions/cache. Docker builds go to Remote Builders with layer caching by default, and there are cache integrations for Bazel, Turborepo, Pants and Moonrepo.
Docker layer cachingYes
GPUNot documented
ConcurrencyPer plan: Developer 32 Linux vCPU and 12 macOS vCPU; Team 64 Linux, 24 macOS and 32 Windows vCPU; Business 160 Linux, 48 macOS and 80 Windows vCPU; custom on Enterprise
Job limitsMaximum instance duration is 3 hours on Developer, 5 hours on Team and up to 24 hours on Business and Enterprise
Static IPsYes
SSH into running jobsYes
ObservabilityPer-job CPU, memory, disk and network metrics correlated with steps, container and build logs, out-of-memory detection, crash dumps and queue-time insights.
SetupConnect a GitHub organization or personal account in the Namespace dashboard, create a runner profile (OS, architecture, shape and caching), then set runs-on to the profile label.
Example labelnscloud-ubuntu-22.04-amd64-4x8
PricingBilled in unit minutes (vCPU × minutes × platform multiplier: Linux 1, Windows 2, macOS 10), with a 1-minute minimum. Team is $100/month with 100,000 unit minutes and Business $250/month with 250,000; Developer is pay as you go. A 2 vCPU / 4 GB Linux runner is listed at $0.002/min prepaid and $0.003/min overage, 2 vCPU / 8 GB at $0.004 and $0.006, and macOS 6 vCPU / 14 GB at $0.06 and $0.09. Cache volume storage is $0.0048/GB-day on Developer, with free allowances on Team and Business.
Free tier30-day free trial of Developer plan features, no credit card required
ComplianceSOC 2 Type II
RegionsSpecific regions are not named; Namespace says it runs its own hardware at multiple sites, offers a regional preference on all plans and region-exclusive residency on enterprise plans
Open sourceNo
Company headquartersNot documented

Facts from Namespace’s public documentation, verified November 22, 2026. Performance figures are vendor claims.

Strengths and trade-offs

Reasons to choose it

  • You want each job in its own virtual machine that is discarded when the job ends
  • You want cache volumes that persist container images, toolchains, action downloads and Git checkouts between runs
  • You need Linux, macOS and Windows runners, with Linux shapes up to 64 vCPU and 512 GB RAM
  • You run Buildkite as well as GitHub Actions and want one provider for both
  • You need stable egress IP ranges and egress policies for allowlisting and network control

Trade-offs

  • Concurrency is capped per plan, for example 32 Linux vCPU on Developer and 64 on Team
  • Maximum instance duration is 3 hours on Developer and 5 hours on Team
  • Windows runners are not available on the Developer plan
  • Native SSH to instances is not enabled by default and requires enrolment through support

Good fit for: Teams on GitHub Actions or Buildkite that want VM-isolated Linux, macOS and Windows runners with persistent cache volumes and fine-grained machine shapes.

Use cases Namespace fits

  • Faster builds: Cache Volumes keep container images, toolchains, action downloads and Git checkouts between runs, and Docker builds use Remote Builders with layer caching.
  • Docker builds: Docker builds on Namespace runners are sent to Remote Builders by default, with layer caching included.
  • ARM64 builds: Linux arm64 runners use AmpereOne processors, with Linux on Apple Silicon in early access.
  • macOS and iOS builds: macOS runners use Apple M4 Pro and M5 Max hardware with up to 16 vCPU and 56 GB RAM, with VNC remote display for debugging.
  • Windows builds: Windows amd64 runners on AMD EPYC are included in the Team and Business plans.
  • Security and compliance: Each job runs in its own discarded VM, and egress policies can restrict outbound traffic per runner profile; SOC 2 Type II is stated.

How Namespace compares

RunnerCI systemsRuns onDeploymentIsolationPriceLargest runnerDocker layer cacheGPUOpen sourceCompany HQ
NamespaceGitHub Actions, BuildkiteLinux, macOS, Windows, x64, arm64Vendor-hostedVirtual machine$0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB)64 vCPU / 512 GBYesNot documentedNoNot documented
BlacksmithGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedFirecracker microVM$0.004/min32 vCPU / 128 GBYesNot documentedNoUnited States
Depot GitHub Actions RunnersGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedSingle-tenant EC2 instance$0.006/min64 vCPU / 256 GBYesYesNoNot documented
WarpBuildGitHub ActionsLinux, macOS, Windows, x64, arm64Vendor-hostedEphemeral VM$0.004/min32 vCPU / 128 GBYesNot documentedNoNot documented
Ubicloud RunnersGitHub ActionsLinux, x64, arm64Vendor-hostedKVM VM$0.00125/min30 vCPU / 120 GBYesNot documentedYesUnited States
Buildkite hosted agentsBuildkiteLinux, macOS, Windows, x64, arm64Platform-hostedEphemeral virtualized environment$0.008/min64 vCPU / 256 GBYesNot documentedNoNot documented
GitHub-hosted runnersGitHub ActionsLinux, macOS, Windows, x64, arm64Platform-hostedFresh VM$0.006/min96 vCPU / 384 GBNot documentedYesNoUnited States

Head-to-head: Blacksmith vs Namespace · Depot GitHub Actions Runners vs Namespace · GitHub-hosted runners vs Namespace · Namespace vs Ubicloud Runners · Namespace vs WarpBuild

See all Namespace alternatives →

Frequently asked questions

What is Namespace?
Managed runners for GitHub Actions and Buildkite on the vendor’s own hardware, configured through profiles with persistent cache volumes. A managed runner platform for GitHub Actions and Buildkite on vendor-operated hardware, suited to teams that want per-job VMs, persistent cache volumes and all three operating systems.
Which CI systems does Namespace work with?
Namespace runs jobs for GitHub Actions and Buildkite, on Linux, macOS, Windows, x64 and arm64.
How does Namespace isolate jobs?
Namespace documents its isolation as: Every job runs in its own instance inside a virtual machine that is discarded when the job ends; the hypervisor is not named. Each job gets a fresh environment that is discarded afterwards.
Is Namespace open source?
No, Namespace is not open source.
How much does Namespace cost?
Billed in unit minutes (vCPU × minutes × platform multiplier: Linux 1, Windows 2, macOS 10), with a 1-minute minimum. Team is $100/month with 100,000 unit minutes and Business $250/month with 250,000; Developer is pay as you go. A 2 vCPU / 4 GB Linux runner is listed at $0.002/min prepaid and $0.003/min overage, 2 vCPU / 8 GB at $0.004 and $0.006, and macOS 6 vCPU / 14 GB at $0.06 and $0.09. Cache volume storage is $0.0048/GB-day on Developer, with free allowances on Team and Business. Check the official pricing page for current rates.
How do I switch from GitHub-hosted runners to Namespace?
Connect a GitHub organization or personal account in the Namespace dashboard, create a runner profile (OS, architecture, shape and caching), then set runs-on to the profile label. An example label is nscloud-ubuntu-22.04-amd64-4x8.
Does Namespace have a free tier?
30-day free trial of Developer plan features, no credit card required.
Does Namespace support ARM64 runners?
Yes, Namespace documents arm64 runners (Linux, macOS and Windows).
Does Namespace offer macOS runners?
Yes, Namespace documents macOS runners alongside Linux and Windows.
Does Namespace cache Docker layers?
Cache Volumes persist data across runs; a runner profile can cache container images, toolchain downloads, action downloads and Git checkouts, and nscloud-cache-action replaces actions/cache. Docker builds go to Remote Builders with layer caching by default, and there are cache integrations for Bazel, Turborepo, Pants and Moonrepo.
How many jobs can run at once on Namespace?
Per plan: Developer 32 Linux vCPU and 12 macOS vCPU; Team 64 Linux, 24 macOS and 32 Windows vCPU; Business 160 Linux, 48 macOS and 80 Windows vCPU; custom on Enterprise.
Where do Namespace runners run?
Specific regions are not named; Namespace says it runs its own hardware at multiple sites, offers a regional preference on all plans and region-exclusive residency on enterprise plans.
What compliance certifications does Namespace have?
SOC 2 Type II.
What are the alternatives to Namespace?

Sources

  1. namespace.so/
  2. namespace.so/pricing
  3. namespace.so/docs/solutions/github-actions
  4. namespace.so/docs/reference/github-actions/runner-configuration
  5. namespace.so/docs/solutions/github-actions/docker-builds
  6. namespace.so/docs/solutions/github-actions/debugging/interactive-access
  7. namespace.so/docs/architecture/compute
  8. namespace.so/docs/architecture/compute/resource-limits
  9. namespace.so/docs/architecture/networking/security
  10. namespace.so/docs/security/egress-policy
  11. namespace.so/docs/workspaces/data-residency
  12. namespace.so/docs/workspaces/security
  13. namespace.so/docs/solutions/buildkite-agents
  14. namespace.so/blog/defense-in-depth-how-we-think-about-security
  15. namespace.so/blog/series-b
  16. namespace.so/blog
  17. namespace.so/terms

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

CI Runners. (2026). Namespace. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/runners/namespace/