Namespace vs Ubicloud Runners
Namespace suits teams on GitHub Actions or Buildkite that want VM-isolated Linux, macOS and Windows runners with persistent cache volumes and fine-grained machine shapes. Ubicloud Runners suits teams on GitHub Actions that want low per-minute Linux runners in European data centers from a vendor whose cloud platform is open source. Namespace is a managed service hosted by the vendor for GitHub Actions and Buildkite, priced at $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB); Ubicloud Runners is a managed service hosted by the vendor for GitHub Actions, priced at $0.00125/min.
Key differences between Namespace and Ubicloud Runners
- CI systems: Only Namespace documents Buildkite.
- Operating systems: Only Namespace documents macOS and Windows.
- Isolation: Namespace: Virtual machine. Ubicloud Runners: KVM VM.
- Published price: $0.002/min prepaid, $0.003/min overage (2 vCPU / 4 GB) (Namespace) versus $0.00125/min (Ubicloud Runners).
- Largest runner: 64 vCPU / 512 GB (Namespace) versus 30 vCPU / 120 GB (Ubicloud Runners).
- Open source: Ubicloud Runners is open source (AGPL-3.0); Namespace is not.
- Self-hosting: Ubicloud Runners documents a self-hosted option; Namespace does not.
What they have in common
- Both are managed services hosted by the vendor.
- Both run GitHub Actions jobs.
- Both document Linux runners.
- Both document arm64 runners.
- Both use a virtual machine per runner.
- Both give every job a fresh environment.
- Both document Docker layer caching.
Namespace vs Ubicloud Runners at a glance
| Attribute | Namespace | Ubicloud Runners |
|---|---|---|
| What it is | Managed runners for GitHub Actions and Buildkite on the vendor’s own hardware, configured through profiles with persistent cache volumes. | Managed Linux runners for GitHub Actions from an open-source cloud platform that runs on leased bare metal. |
| Type | Managed runner service | Managed runner service |
| CI systems | GitHub Actions, Buildkite | GitHub Actions |
| Operating systems | Linux, macOS, Windows | Linux |
| Architectures | x64, arm64 | x64, arm64 |
| Isolation | 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 runs in a fresh virtual machine provisioned with Linux KVM, using Cloud Hypervisor as the virtual machine monitor; the VM and its block storage are destroyed when the job finishes |
| Fresh environment per job | Yes | Yes |
| Hardware | Namespace 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. | Standard x64 runners use AMD EPYC 9454P (two vCPUs per physical core), premium x64 runners use AMD Ryzen 9 7950X3D, and arm64 runners use Ampere Altra Q80-30 with one physical core per vCPU; all have NVMe SSDs. |
| Performance (vendor claim) | Not documented | Ubicloud says premium runners are around 2x faster on CPU-heavy workflows and that its cache gives 4x faster downloads and 3x faster uploads (vendor claims) |
| Runner sizes | Linux 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 | 2 to 30 vCPU with 8 to 120 GB RAM on x64; 2 to 30 vCPU with 6 to 90 GB on arm64 |
| Caching | 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. | A transparent cache backend serves actions/cache, setup-* package caching and Docker layer caching through type=gha without workflow changes. Each repository gets 30 GB free (100 GB with premium runners enabled), entries unused for seven days are removed, and extra storage is $0.04 per GB per month on request. |
| Docker layer caching | Yes | Yes |
| GPU | Not documented | Not documented |
| Concurrency | 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 | Not documented |
| Static IPs | Yes | Not documented |
| SSH into running jobs | Yes | Yes |
| Pricing | 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. | Standard x64 per minute: $0.00125 (2 vCPU), $0.0025 (4), $0.005 (8), $0.01 (16) and $0.01875 (30 vCPU). Premium x64: $0.002 (2 vCPU) to $0.03 (30 vCPU). arm64 is priced the same as standard x64. Billing is per minute, and new users get premium runners by default with fallback to standard runners when premium capacity is full. |
| Free tier | 30-day free trial of Developer plan features, no credit card required | $2.5/month credit, which Ubicloud equates to 1,250 runner minutes |
| Open source | No | Yes (AGPL-3.0) |
| Self-host / your cloud | No / Not documented | Yes / Not documented |
| Compliance | SOC 2 Type II | SOC 2 Type 2 report available through the Trust Center; GDPR data processing agreement offered |
| Regions | 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 | Europe by default: Hetzner (Falkenstein, Germany) as the primary fleet and Leaseweb (Frankfurt), with AWS eu-central-1 as overflow; US runners are used only on explicit request |
| Company headquarters | Not documented | San Francisco, California, United States |
| 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 | Teams on GitHub Actions that want low per-minute Linux runners in European data centers from a vendor whose cloud platform is open source |
Verified November 22, 2026 from each provider’s documentation. Performance figures are vendor claims, not our measurements.
Which should you choose?
Reasons to choose Namespace
- 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
Reasons to choose Ubicloud Runners
- You want Linux runners at $0.00125 per minute for 2 vCPU, on x64 or arm64
- You want the underlying cloud platform to be open source and self-hostable
- You need jobs to run in European data centers by default
- You want existing actions/cache and type=gha Docker layer caching to work without workflow changes
Trade-offs to check first
- Namespace: Concurrency is capped per plan, for example 32 Linux vCPU on Developer and 64 on Team
- Namespace: Maximum instance duration is 3 hours on Developer and 5 hours on Team
- Ubicloud Runners: Windows and macOS runners are not documented
- Ubicloud Runners: Runner prices were raised twice in 2026, in May and September
Run your slowest workflow on both before deciding. See the full Namespace profile and Ubicloud Runners profile, or the complete comparison.
More comparisons
- Blacksmith vs Namespace
- Depot GitHub Actions Runners vs Namespace
- GitHub-hosted runners vs Namespace
- Namespace vs WarpBuild
- Blacksmith vs Ubicloud Runners
- Depot GitHub Actions Runners vs Ubicloud Runners
- GitHub-hosted runners vs Ubicloud Runners
- TestFlows GitHub Hetzner Runners vs Ubicloud Runners
- Ubicloud Runners vs WarpBuild
Frequently asked questions
Is Namespace or Ubicloud Runners better?
What is the difference between Namespace and Ubicloud Runners?
Which is open source, Namespace or Ubicloud Runners?
How do Namespace and Ubicloud Runners isolate jobs?
How does Namespace pricing compare with Ubicloud Runners?
Is Namespace or Ubicloud Runners faster?
Do Namespace and Ubicloud Runners cache Docker layers?
Where do Namespace and Ubicloud Runners runners run?
Sources
- namespace.so/
- namespace.so/pricing
- namespace.so/docs/solutions/github-actions
- namespace.so/docs/reference/github-actions/runner-configuration
- ubicloud.com/use-cases/github-actions
- ubicloud.com/docs/about/pricing
- ubicloud.com/docs/github-actions-integration/quickstart
- ubicloud.com/docs/github-actions-integration/runner-types
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 vs Ubicloud Runners. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/compare/namespace-vs-ubicloud/