Namespace Raises $42M Series B for Developer Infrastructure

A coding agent can generate another commit before the last one has finished testing. The impressive part is the speed of creation; the expensive part is everything required to prove the new code belongs in production.

Namespace has raised a $42M Series B to build more of that proving ground. Scale Venture Partners led the round, with NEA, 20VC, Essence, Burst Capital, Susa Ventures, and Datadog CEO Olivier Pomel participating. The financing brings Namespace's total funding to $65M and will support product development plus an expansion of the company's data-center footprint.

The transaction lands seven months after Namespace disclosed $23M across Seed and Series A financing. It also arrives while coding agents are multiplying the volume of software work that still has to be compiled, tested, secured, reproduced, and shipped on real machines.

What Happened

Namespace announced the Series B on October 5, 2026. The company said Scale Venture Partners led the $42M financing and that returning or participating investors included New Enterprise Associates, 20VC, Essence, Burst Capital, Susa Ventures, and Olivier Pomel. Axios also independently reported the round and identified Founder and CEO Hugo Santos as the source of the announcement.

The new financing follows Namespace's March 2026 Seed and Series A disclosure, when the company reported $23M led by NEA with Susa Ventures and burst.vc participating. Namespace now reports $65M in total funding. No valuation was disclosed, so the round should be read as fresh operating capital rather than an invitation to manufacture a paper-value milestone.

What Namespace Builds

Namespace provides coding, build, and test environments across Linux, Windows, and Mac. Its products include Devboxes for AI coding agents and a drop-in replacement for GitHub-hosted runners, while its broader platform supplies compute, storage, networking, caching, observability, and remote access around those workloads.

The distinction is that Namespace does not treat development work like a smaller version of a production cloud workload. Code builds and test runs arrive in bursts, require reproducible environments, and benefit from storage placed close to compute. Namespace designs and operates its own hardware, hypervisor, scheduler, and server racks to control more of that performance path.

This is a capital-intensive answer to a software problem. Owning the infrastructure can produce speed, reliability, and cross-platform consistency, but it also transfers the burden of capacity planning, utilization, hardware deployment, and operational discipline to Namespace.

Why Mac Infrastructure Matters

The Mac investment makes the strategy easier to see. An AI agent can write an iOS application's code on many systems, but compiling, signing, and testing that application still depends on Apple hardware and the macOS and Xcode toolchain. General-purpose infrastructure has often treated Mac capacity as a specialty product, even as agents make on-demand development environments more valuable.

Namespace says the Series B will help expand its data centers, including its Mac fleet. The bet is that developers and agents should receive the same fast, reproducible environment whether they are targeting Linux services, Windows software, or Apple platforms. That cross-platform promise becomes more difficult as the number of parallel agents grows, which is precisely why the company wants to own more of the underlying stack.

The Traction Behind the Round

Namespace reports that total revenue grew 8x over the prior 12 months and that more than 1,000 companies use the platform. Its customer materials name Ramp, Framer, Vanta, Warp, Zed, fal.ai, Sierra, Buildkite, DuckDB, ClassPass, and others. These are company-reported metrics and relationships, not independently audited market-share figures, but they show the kind of workload attracting capital.

The company's published case studies describe a 55% CI cost reduction for ClassPass, 3x faster CI queue times for Zed, more than 60% lower costs and sub-five-minute builds for Framer, and 10x faster builds for DuckDB. Those results come from Namespace's own customer stories and will vary by workload, yet the commercial message is consistent: customers buy shorter feedback cycles, not infrastructure for its own sake.

For an engineering organization, a slow build does more than delay one developer. It holds up reviewers, releases, customer fixes, and now potentially fleets of agents that can create work far faster than a human-paced pipeline was designed to absorb.

Why Investors Are Funding the Compute Layer for Code

Scale Venture Partners framed the investment around the tradeoffs broken by agent-driven software development. More generated code raises demand for speed and scalability, but enterprise buyers still expect reliability and security. Namespace is positioning specialized development compute as the layer that reconciles those demands.

That thesis also explains why NEA returned after leading the prior financing. In its Series A investment note, NEA argued that agents need on-demand computers rather than static, sequential pipelines. The Series B turns that argument into a larger infrastructure commitment only seven months later.

The competitive question is whether specialized development infrastructure becomes a durable category or a feature absorbed by hyperscalers, code-hosting platforms, and other developer-cloud providers. Namespace's defense is vertical integration and workload focus. Its risk is that hardware advantages must keep compounding while customers expect cloud-like simplicity and economics.

What the $42M Changes

The capital gives Namespace room to expand product development and deploy more data-center capacity before agent-driven demand settles into a predictable shape. Each new rack makes the company's thesis tangible, but it also creates an operating promise: the capacity has to be available, reliable, secure, and economically useful when customers need it.

Hugo Santos and the Namespace team are taking a lesson from Google's internal developer infrastructure and rebuilding it for companies that do not have Google's budget or systems staff. The next stage is less about demonstrating that faster builds feel good and more about proving that specialized development compute can become dependable infrastructure across companies, platforms, and increasingly autonomous software workflows.

The next 100 billion commits may arrive because software agents can produce them. Namespace is financing the part of the system that decides how many of those commits survive contact with real machines, real tests, and production expectations.