Namespace Raises $42M—Revenue Grew Eightfold in 12 Months

In its October 5, 2026 announcement, Namespace said it had closed a $42 million Series B led by Scale Venture Partners, bringing total funding to $65 million. It reported eightfold revenue growth over the preceding 12 months and said it serves more than 1,000 companies. NEA, 20VC, Essence, Burst Capital and Susa Ventures participated, alongside angel investors including Datadog CEO Olivier Pomel; the planned uses of the money include product development and expanded data-center capacity, particularly Mac hardware.

The EU-Startups report places Zurich-based Namespace’s Series B seven months after an NEA-led Series A and describes plans for offices in San Francisco and New York City. Based on the announced totals, the new round represents roughly 65% of all funding raised to date. That short interval and large addition point to a capacity-building phase, while the revenue multiple remains a company-reported figure without a disclosed starting base.

The Series B will fund more than software features

Namespace sells infrastructure for work that happens while software is being written and checked. Its Devboxes provide development environments for coding agents, while its GitHub Actions product runs automated jobs; the platform also supports Docker, Bazel, Turbo and Nix workflows. A useful environment must have code, dependencies and computing resources ready when a job starts, then return a build or test result quickly enough for development to continue.

The company designs and deploys its own server racks and runs a stack that includes a hypervisor and scheduler. That gives it control over how jobs reach machines and where reusable build data sits. It also makes expansion capital intensive: equipment and data-center space have to be available before a surge of customer jobs arrives. The financing therefore supports both the products developers use and the physical capacity needed to deliver them.

Coding agents put different demands on the machines

In Scale Venture Partners’ investment note, partner Javier Redondo describes agents launching concurrent work in isolated environments and writes that “every slow build or test delays the next iteration.” Each environment needs the relevant repository and toolchain, controlled access to credentials and a way to preserve useful state. Build and test speed matters because an agent may need the result before deciding what to change next.

A conventional production service is generally provisioned to stay available for user requests. Development jobs have a different rhythm: environments start, compile or test a change, and may release capacity until the next run. Several agents working on the same codebase can create a burst of jobs followed by a quieter period. Fast startup, caching and predictable execution time address repeated waiting within that cycle, rather than only the speed of an individual machine.

Those patterns explain the appeal of infrastructure tuned for building and testing. Processors, NVMe storage and networking affect how quickly jobs run; placing work near cached dependencies and artifacts can reduce repeated setup. The commercial question is whether customers generate enough recurring work to keep dedicated capacity productive. Namespace’s revenue claim establishes growth across its business, but the figures released with the round do not separate agent-generated demand from other development and continuous-integration work.

Mac capacity makes the expansion more specific

Mac hardware is a distinct part of the announced data-center plan because iOS and macOS builds need Apple development tools and a suitable macOS environment. Adding Mac capacity alongside Windows and Linux environments lets Namespace serve more of the work involved in developing Apple-platform software. For an agent, access has to be available at the moment a change is ready to build or test; waiting for a machine can delay the next decision.

That requirement also sharpens the economics of expansion. Mac machines must be ready for bursts of jobs, but idle time still costs money. Demand spread across many customers and repeated throughout the day would make that fleet easier to use efficiently than demand concentrated in a few build windows. The announced investment increases the importance of utilization as Namespace adds hardware ahead of future workloads.

Growth leaves the durability question open

Eightfold revenue growth is substantial, but a multiple alone does not show the starting revenue base, how spending is distributed among customers or what it costs to serve them. The reported company count indicates reach without showing whether a small group accounts for most usage. Those details matter for infrastructure built to absorb peaks: concentrated demand can leave expensive machines underused between bursts, even when total job volume is rising.

Namespace has several sources of potential repeat work, including agent environments, continuous integration and Apple-platform testing. The decisive evidence will be whether customers keep using the expanded fleet consistently as it comes online and whether that usage supports the cost of operating it. For developers, the immediate consequence is a larger planned supply of build and test environments; for the business, sustained utilization will determine whether the surge becomes a durable infrastructure market.