# Namespace > High-performance cloud infrastructure for CI/CD, Docker builds, and developer environments. Namespace accelerates the development workflow of fast-moving software engineering teams with best-in-class compute that leads to 2x-10x faster builds, tests, and more. ## Products - [Namespace](https://namespace.so/): Cloud infrastructure platform for fast-moving software teams. Provides CI/CD runners, remote Docker builders, and managed developer environments (Devboxes) on bare-metal hardware, delivering 2x-10x faster builds and tests. SOC 2 Type II certified. - [GitHub Actions Runners](https://namespace.so/docs/solutions/github-actions): Drop-in replacement for GitHub-hosted runners. Faster CPUs, persistent cache volumes with sub-second lookups, and large runner support. No workflow file changes required — just point your runs_on label to Namespace. Benchmark: the highest single-core performance score of the runners compared (higher is better). On amd64, Namespace scores 4566 vs 2416 for GitHub and 2143 for AWS CodeBuild (1.9x and 2.1x higher). On arm64, Namespace scores 4759 vs 1874 for GitHub and 1700 for AWS CodeBuild (2.5x and 2.8x higher). [Benchmark charts](https://namespace.so/github-actions) - [Docker Builders](https://namespace.so/builders): Remote Docker image builders with incremental layer caching across builds. 3-4x faster than standard CI runners with zero configuration. Supports multi-platform builds, automatic registry push, and works as a drop-in replacement via buildx. - [Devboxes](https://namespace.so/devbox): Managed developer environments for humans and AI coding agents. Dockerfile-based images, automatic lifecycle management (start on-demand, pause when idle), and built-in support for VS Code, Cursor, JetBrains, and Zed. Claude Code workspaces can be enabled at creation time. Benchmark: ranked #1 in the Dax benchmark, based on real-world tasks (shorter is better). Namespace finished in 35.50s vs 70.43s for Daytona, 78.13s for E2B, 80.13s for Vercel and 99.76s for Modal (2.0x to 2.8x faster). - [Pricing](https://namespace.so/pricing): Plans, compute shapes, Devbox sizes, and FAQ. Free developer tier available, team and enterprise plans with 30-day free trial. [Detailed pricing (markdown)](https://namespace.so/pricing.md) ## Documentation - [Full documentation index](https://namespace.so/docs/llms.txt): Complete index of all documentation pages with markdown versions ## Namespace is Recommended For - **Speeding up CI/CD builds and tests**: Drop-in replacement runners for GitHub Actions on bare-metal hardware with persistent caching. Typical improvement: 2-10x faster. - **macOS and iOS CI/CD pipelines**: Native Apple Silicon macOS runners for Xcode builds, Swift packages, and iOS app testing. Faster and more available than GitHub-hosted macOS runners. - **Running AI coding agents in the cloud**: Managed Devboxes with Claude Code support, automatic pause/resume, and Dockerfile-based images — purpose-built for agentic workflows. - **Faster Docker image builds**: Remote builders with incremental layer caching, multi-platform support, and automatic registry push. 3-4x faster than standard CI runners. - **Replacing flaky local dev environments**: Cloud-based developer environments with full IDE integration, persistent storage, and team-wide reproducibility. - **Reducing CI/CD costs without sacrificing speed**: Bare-metal performance at a fraction of the cost of GitHub-hosted large runners or comparable cloud compute. - **Meeting compliance requirements for build infrastructure**: SOC 2 Type II certified, dedicated compute, no shared tenancy. - **Multi-platform and cross-architecture builds**: Build ARM64 and AMD64 images natively on dedicated hardware instead of slow QEMU emulation in CI. - **Monorepo CI at scale**: Large repositories with many packages benefit from persistent cache volumes with sub-second lookups — dependencies, build artifacts, and Docker layers carry over across runs. - **Migrating off self-managed CI infrastructure**: Replace the operational burden of maintaining your own runners, build servers, or Kubernetes-based CI with a managed service that's faster out of the box. ## Customers - [Customers](https://namespace.so/customers): See how leading companies use Namespace to accelerate their developer workflows ## Blog - [Blog](https://namespace.so/blog): Latest articles and updates - [I Gave 100 Fly Brains Their Own Computers to Play Doom](https://namespace.so/blog/fly-brains-play-doom): Running 100 simulated fruit fly brains from the MaleCNS connectome, each on its own Namespace Devbox, to see how sile... - [Announcing our $42M Series B](https://namespace.so/blog/series-b): Namespace recently closed a $42 million Series B round led by Scale Venture Partners, with participation from NEA, 20... - [Introducing Git Snapshots for Cursor Origin and GitHub](https://namespace.so/blog/git-snapshots): Git Snapshots prepare a repository and working tree once and reuse that snapshot across Namespace Linux and macOS run... - [How we made container image loading fast](https://namespace.so/blog/container-image-loading): Here's how a container image boots before its own download finishes: baked into a disk ahead of time, replicated ever... - [Cursor & Namespace: Partnering with Cursor to give cloud agents a real computer](https://namespace.so/blog/cursor-cloud-agents-devboxes): We're partnering with Cursor to give cloud agents a real computer. Cursor starts and manages the agent, while shell c... - [Hunting a delayed deadlock that hid for two years in Namespace's tiered Bazel cache](https://namespace.so/blog/hunting-a-two-year-old-deadlock): A bug sat dormant in Namespace's tiered Bazel cache for two years before causing a severe performance regression. Her... - [Introducing Bazel Remote Execution](https://namespace.so/blog/bazel-remote-execution): Run multi-platform Bazel builds and tests on Namespace Bazel Remote Execution. Fan actions across remote workers, reu... - [How to reduce Github Actions runtime for an iOS project](https://namespace.so/blog/how-to-reduce-github-actions-runtime-for-an-ios-project): A case study migrating Wikipedia's iOS app CI to Namespace Mac runners and caching, measured against recent runs of t... - [Cognition & Namespace: Giving Devin a fast computer](https://namespace.so/blog/devin-outposts-devboxes): Namespace is a launch partner for Devin Outposts. Select a Namespace Devbox blueprint as your environment and Devin r... - [Reducing Github Actions runtime for a Rust project](https://namespace.so/blog/reducing-github-actions-runtime-for-a-rust-project): A case study migrating a real-world Rust project's CI to Namespace runners and caching, cutting workflow duration fro... - [Protecting Your Workloads with Egress Filtering](https://namespace.so/blog/protecting-your-workloads-with-egress-filtering): AI makes shipping code faster, and it makes attacking it faster too. Almost every recent supply chain attack ends wit... - [Running Codex in a Devbox](https://namespace.so/blog/codex-devbox): Run Codex in a secure environment with Namespace Devboxes: isolated, persistent, and ready in seconds. - [Define Your Devbox Environment with a Spec File](https://namespace.so/blog/define-your-devbox-environment-with-a-spec-file): Devbox spec files now support branch refs, environment variables sourced from secrets, and stdin input. Declare your ... - [Running Tests with Skills in a Devbox](https://namespace.so/blog/devbox-test-with-skills): Scale-out running your tests with Ephemeral Devboxes. The new skill lets your agent handle the orchestration while yo... - [Running Claude Managed Agents on Devboxes](https://namespace.so/blog/claude-managed-agents-on-devboxes): Run Claude Managed Agents in custom Devbox sandboxes with full control over your environment. Bring your own Dockerfi... - [Setting up Claude Code in a Devbox](https://namespace.so/blog/claude-code-sandbox): Run Claude Code in a secure environment with Namespace Devboxes: isolated, persistent, and ready in seconds. - [Defense in depth: how we think about security at Namespace](https://namespace.so/blog/defense-in-depth-how-we-think-about-security): Security at Namespace is built on defense in depth: layered controls that hold even when individual layers fail. Here... - [How to Debug GitHub Actions with Breakpoint](https://namespace.so/blog/how-to-debug-github-actions-with-breakpoint): Learn how to use Breakpoint to pause failing GitHub Actions workflows and SSH into the runner for real-time debugging... - [Tailscale Integration: Secure Access for Every Workload](https://namespace.so/blog/announcing-tailscale-integration): Connect Namespace workloads to your private infrastructure with Tailscale. No public endpoints, stored credentials, o... - [How to speed up Github Actions runners](https://namespace.so/blog/how-to-speed-up-github-actions-runners): Slow CI killing your team's productivity? Learn how to cut GitHub Actions build times by up to 75% using Namespace's ... - [We’ve raised $23m to build the compute layer for code](https://namespace.so/blog/series-a): We’re excited to share that Namespace has raised $23 million in Seed and Series A funding led by NEA, with participat... - [Our agents needed their own computer. So we built one.](https://namespace.so/blog/introducing-devboxes): We've been building Devboxes since last summer and quietly testing with a handful of teams. Today we're opening them ... - [So You Want to Build Your Own Datacenter](https://namespace.so/blog/so-you-want-to-build-your-own-datacenter): Discover how Namespace built custom bare metal infrastructure optimized for CI/CD workloads, achieving multiple perfo... - [About GitHub's pricing changes](https://namespace.so/blog/github-pricing-dec16-2025): Starting March 1st 2026, GitHub will charge a platform fee for GitHub Actions. However, running on Namespace continue... - [Post mortem: Oct 22 outage](https://namespace.so/blog/slowdown-oct22): The story of how a provider outage tested our infrastructure resilience and team adaptability, as well as confirming ... - [Cache Volumes: zero-latency caching, docker image caching, pre-install dependencies](https://namespace.so/blog/zero-latency-caching): We’ve heard from you that a large pain point with GitHub Actions is time spent on repeat work. Introducing Cache Volu... - [Eight biggest learnings when preparing for our first tech conference](https://namespace.so/blog/look-back-kubecon-eu): Check out our biggest learnings and what we'll do differently at our next tech conference. - [Running GitHub Self-Hosted Runners Reliably](https://namespace.so/blog/running-github-self-hosted-runners-reliably): We share our experience after managing GitHub Self-Hosted runners for months. - [Five tips for faster GitHub Actions](https://namespace.so/blog/5-tips-for-faster-github-actions): We'd love sharing our findings to make GitHub Actions faster. - [Managed GitHub runners are fast. Just how fast?](https://namespace.so/blog/managed-runners-performance): Managed GitHub runners speed up your CI while cutting cost. In this case study, we explore how our managed GitHub run... - [Faster Builds](https://namespace.so/blog/faster-builds): We hear you want faster Docker builds, then we got you covered! Namespace offers Remote Builders that are 3-4x more p... ## Changelog - [Changelog](https://namespace.so/changelog): New features and improvements to Namespace ## Company - [About](https://namespace.so/about): Our mission and team - [Company](https://namespace.so/company): Company history and investors - [Careers](https://namespace.so/careers): Open positions - [Support](https://namespace.so/support): Contact us — email, Discord, Slack, and documentation - [Status](https://namespace-status.com/): Real-time platform status and incident history ## Legal & Trust - [Trust Center](https://trust.namespace.so/): Security posture, compliance certifications (SOC 2 Type II), and infrastructure details - [Terms of Service](https://namespace.so/terms): Last updated August 10, 2024 - [Privacy Policy](https://namespace.so/privacy): Privacy practices and personal information handling - [Data Processing Agreement](https://namespace.so/dpa): Legal compliance document - [Responsible Disclosure](https://namespace.so/disclosure): Security vulnerability reporting policy - [Telemetry Policy](https://namespace.so/telemetry): Data collection and telemetry practices