Company Spotlight: Namespace Builds Compute for Coding Agents

Namespace is building the compute layer underneath modern software development. The San Francisco developer-infrastructure company gives human developers and coding agents fast environments to write, build and test code across Linux, Windows and macOS.

Founder and CEO Hugo Santos started Namespace in 2022 after working on large-scale infrastructure at Google. The company began with a familiar frustration: software teams were spending too much of their day waiting for continuous-integration jobs, build systems and tests that had not kept pace with the codebases running through them.

That bottleneck is becoming more expensive as coding agents produce changes faster than human teams can validate them. Namespace is betting that the next generation of developer tooling needs more than a clever interface. It needs reproducible computers, available in seconds, with the performance and operating-system coverage required to turn generated code into working software.

About Namespace and Its Developer Platform

Namespace provides 2 products on a shared infrastructure foundation. Devboxes are development computers that coding agents and engineers can use for repositories, shell commands, file changes, builds and tests. Namespace's GitHub Actions product replaces standard hosted runners with faster, observable compute while preserving the workflow format teams already use.

The company supports Linux, Windows and macOS because software development is stubbornly multi-platform. An agent building an iOS application needs a Mac with the right developer tools. A team testing a Windows product cannot validate every change on Linux. A platform that skips those environments may look broad on a slide and narrow the moment real code arrives.

Namespace also supports Docker builds, remote caching and Bazel Remote Execution. The product is designed to meet teams inside existing toolchains instead of demanding a complete re-platform before the first performance gain appears.

Why Coding Agents Change the Infrastructure Equation

Traditional CI/CD systems were designed for a human-paced flow of pull requests. Coding agents change the volume. More branches, builds and tests can arrive in parallel, while every slow queue or cold cache is multiplied across automated work.

Namespace treats code workloads as their own infrastructure category. They are bursty, latency-sensitive, incremental, highly parallel and unusually dependent on reproducibility. General-purpose clouds can run them, but they were not necessarily designed around the feedback loop of an engineer or agent waiting for an answer.

The shift moves the constraint. Generating a change may take seconds. Proving that the change compiles, passes tests, behaves correctly and works across platforms can still take minutes or longer. Faster generation without faster validation is not velocity. It is a larger pile of unverified code.

Namespace Builds the Stack Below the Runner

Namespace's differentiation sits beneath the familiar developer interface. The company says it designs and operates custom hardware, a hypervisor, scheduling, storage and networking for code execution. Its compute nodes use high-throughput networking and NVMe-backed storage, while caches and build artifacts are placed close to the workloads that need them.

That vertical integration gives Namespace more control over cold starts, data placement and performance variance. It also gives the company more operational responsibility. Namespace has published detailed accounts of early rack designs that missed power budgets and a delayed deadlock in its tiered Bazel cache. Those stories are useful because infrastructure credibility is built through failure analysis, not adjectives.

The company began operating its own hardware in 2024. The new funding will support more data-center locations and a larger Mac fleet. The Mac investment matters because coding agents cannot build and test serious iOS or macOS software on pretend Apple hardware.

Customer Evidence Moves Beyond Faster CI

Namespace says more than 1,000 companies now use the platform, including Ramp, Framer, Vanta, Warp, Zed, fal.ai, DuckDB, LiveKit and Sierra. The company's public customer stories report 10x faster builds for DuckDB, 4x CI performance for Warp, 3x faster queue times for Zed and more than 60% cost reduction with sub-five-minute builds for Framer.

Those are company and customer-reported results, not standardized benchmarks. They still show the range of the problem. One team cares about Rust build latency. Another needs Mac capacity. Another needs thousands of sandboxes for cloud agents. Namespace is trying to turn those workloads into a common compute platform rather than a collection of isolated runner optimizations.

The clearest signal is not any single speed claim. It is that developer-tool companies such as Warp and Buildkite can use Namespace as infrastructure inside their own products. That moves Namespace from a tool purchased by engineering teams toward a layer that other developer platforms can build on.

Funding Turns Product Proof Into Capacity Work

Namespace announced a $42M Series B led by Scale Venture Partners on October 5, 2026. The round included 20VC, NEA, Essence, Burst Capital, Susa Ventures and Olivier Pomel, and brought total disclosed funding to $65M. Namespace also reports 8x revenue growth during the prior 12 months.

The capital arrives only seven months after the company's $23M Seed and Series A announcement. That tempo suggests demand is pulling Namespace deeper into physical infrastructure at the same time its software surface is expanding.

Capital does not remove the hard part. More locations and more Mac hardware create supply-chain, reliability and utilization challenges. Customers buying development infrastructure will judge Namespace on whether fast environments stay fast under load, whether failures are legible and whether the platform remains simpler than building an internal fleet.

Leadership and Hiring Show a Full-Stack Bet

Hugo Santos leads Namespace as Founder and CEO. Namespace's official company materials connect the product thesis to experience building Google's application platform, where internal infrastructure could multiply the output of many product teams.

Namespace's careers page listed 10 open roles when reviewed. Hiring covered engineering leadership, product engineering, infrastructure engineering, security, customer-facing engineering, technical project management, account management and sales across the San Francisco area, New York and several European markets.

The role mix mirrors the business. Namespace needs engineers who can work close to hardware and distributed systems, product builders who can make that complexity disappear, and customer-facing teams who can translate performance claims into production results. Hiring here is not generic growth theater. It is a map of where the platform is under pressure.

What Namespace Signals for Developer Infrastructure

Namespace represents a larger transition in software development. As agents make code abundant, execution capacity, test fidelity and fast feedback become scarce. The valuable platform may be the one that makes every generated change cheap to test, easy to inspect and difficult to fake.

That does not make CI/CD irrelevant. It changes the unit of infrastructure from a static pipeline to an available computer with the right state, tools and operating system. Namespace is building for that unit across the software lifecycle.

The bet is straightforward and expensive: the next 100 billion commits will need somewhere to run. Namespace wants to own the milliseconds, machines and hard lessons between generated code and software anyone should trust.