Namespace Raises $23M to Build a Compute Layer Purpose-Built for Code
Every engineering team hits that moment when the pipeline stalls and the room goes quiet. Not dramatic, not loud, just enough friction to kill momentum. Minutes stretch, context fades, and suddenly the cost isn’t compute, it’s focus. Namespace just raised $23M like they’ve been waiting for that exact pause to make their entrance.
Namespace, out of Zürich, is building what most clouds politely ignored: a compute layer designed specifically for code. Not generic workloads. Not “good enough” runners. Code. The kind that demands speed, precision, and zero patience for latency theater. Hugo Santos saw this firsthand after nearly a decade inside Google, shaping systems behind Search, Play, Photos, and Assistant. You don’t leave that room unless you’ve seen where the bodies are buried. Now he’s building infrastructure that doesn’t pretend code and compute are the same conversation.
New Enterprise Associates leaned in to lead, with Madison Faulkner, Aaron Jacobson, Lila Tretikov, Hilarie Koplow-McAdams, Thomas Joshi, and Ashley Jepson backing the thesis. Susa Ventures and Burst Capital joined the table, with Kivu Ventures already in the story. Smart capital doesn’t chase noise. It follows inevitability. And right now, faster code execution isn’t a luxury, it’s oxygen.
The numbers don’t whisper. They land. Teams are seeing 2x to 10x faster pipelines. One case drops from 11 minutes and 38 seconds to 1 minute and 36 seconds. That’s not optimization, that’s a different clock. Costs fall up to 70% while performance climbs. No maintenance overhead. Just clean, repeatable execution. Mitchell Hashimoto is already paying attention, which tells you this isn’t theory dressed up as product.
Under the hood, Namespace owns the full stack. Custom hardware. Low-latency storage. Remote caching across Docker, Bazel, Nix, Turbo. AMD64, ARM64, and Apple Silicon with M4 Pro in play. Ephemeral environments spin up like they’ve got somewhere to be. AI coding agents get isolated Devboxes so they can work without stepping on human toes. It’s infrastructure that understands developers don’t want more tools, they want less waiting.
The angle most people will miss is simple. AI didn’t just increase code output, it exposed how fragile the compute layer really is. More code, faster cycles, higher expectations. The old pipes weren’t built for this pressure. Namespace didn’t patch the leak. They rebuilt the plumbing.
Congratulations to Hugo Santos and the Namespace team for turning a universal frustration into a product that actually respects time. This isn’t about faster builds. It’s about restoring flow to the people writing the future, one pipeline at a time.
