Apply💙!!
Really proud of this program.
Building in the open? Apply for Namespace for OSS 💙
namespace.so/opensource
Aaron retweeted
The logo wall never looked better.
Welcome, @mercury.
The fintech more than 450K ambitious companies and entrepreneurs trust with their finances, now running builds on Namespace.
Aaron retweeted
Within 24 hours, we shipped changes that removed the eMudhra attack vector for all our customers.
In particular:
- GitHub Actions jobs no longer trust the compromised certificates.
- Devboxes now receive a patch when they wake up, so the mitigation is applied automatically.
These changes apply across Linux, macOS, and Windows.
Aaron retweeted
What's new in Namespace
0:00 Intro
0:06 Namespace MCP Server
0:32 Multi-repo Devboxes
0:53 Devbox Services
1:08 iPhone Duo and Xcode 27.1 RC
1:28 Outro
Check out @nicolasdular's walkthrough!
Aaron retweeted
Spinning up 100 Namespace Devboxes, each simulating a 166,700-neuron male fruit fly connectome playing DOOM.
I selectively silenced neurons across the connectome to test how targeted lesions alter motor output and survival. 100 fly brains, 100 neural perturbations, One last fly standing.
Full write-up in the comments.
So excited to listen to this one! New favorite podcast (:
First episode of Once In The Trenches (OITT) with the Co-Founder of Amp, @thorstenball.
What does it mean to build for the frontier? Does knowing how software works still matter? When should you kill a feature? We talked about all this and more.
Timestamps:
00:00 Intro
00:48 Writing interpreter and compiler books
02:00 Still worth learning interpreters?
05:11 Do drivers need to know the engine?
10:08 Three booleans vs. one enum
13:09 Sourcegraph, Zed, and back again
16:23 How Amp started with just bash
18:05 Spinning Amp out of Sourcegraph
21:58 Killing features people liked
24:31 Same team, much bigger product
25:42 Two meetings a week, no hiring
29:02 Building the new docs page with agents
30:01 "We thought it would be fun"
34:43 Cloudflare's 30-second timeout
37:47 Rebuilding on Rivet over a weekend
38:16 Agent threads that run for three weeks
39:36 When Google killed a FoundationDB node
40:52 Can the agent read the logs?
43:18 Features with no UI
So excited to listen to this one! New favorite podcast (:
First episode of Once In The Trenches (OITT) with the Co-Founder of Amp, @thorstenball.
What does it mean to build for the frontier? Does knowing how software works still matter? When should you kill a feature? We talked about all this and more.
Timestamps:
00:00 Intro
00:48 Writing interpreter and compiler books
02:00 Still worth learning interpreters?
05:11 Do drivers need to know the engine?
10:08 Three booleans vs. one enum
13:09 Sourcegraph, Zed, and back again
16:23 How Amp started with just bash
18:05 Spinning Amp out of Sourcegraph
21:58 Killing features people liked
24:31 Same team, much bigger product
25:42 Two meetings a week, no hiring
29:02 Building the new docs page with agents
30:01 "We thought it would be fun"
34:43 Cloudflare's 30-second timeout
37:47 Rebuilding on Rivet over a weekend
38:16 Agent threads that run for three weeks
39:36 When Google killed a FoundationDB node
40:52 Can the agent read the logs?
43:18 Features with no UI
Aaron retweeted
Last week, @20thr, CEO of Namespace, went on ETN.
He talked about our recent Series B, and why we deploy our own racks across multiple data centers and build the software stack that runs on them.
Aaron retweeted
Long overdue: @pidotdev is now installed by default in all @namespacelabs Devboxes!
Start a Devbox.
Launch pi.
Prompt.
Close your laptop lid 😉
Customer obsessed. That’s how I’d describe the Namespace team. So much care and attention goes into making sure our customers get real value, have a great experience, and can keep shipping fast.
That’s why I’m excited to share that we’ve raised a $42M Series B led by Scale Venture Partners, with participation from New Enterprise Associates (NEA), 20VC, and others.
This funding will help us expand our data center infrastructure, continue hiring world-class talent, and most importantly, keep investing in our customers.
If you want to be part of a team supporting some of the most ambitious companies in the world and helping them move faster everyday, we’re hiring!
namespace.so/careers
Grateful to be part of this team!
Today, I'm excited to share that we've raised a $42M Series B led by @scalevp, with participation from @NEA, @20vcfund and others, bringing our total funding to $65M.
The next 100 billion commits are coming faster than any infrastructure was built to handle.
We're building, from the ground up, the developer platform for this next wave of software development.
We already power software development for @spacexai, @tryramp, @ElevenLabs, @SierraPlatform , @framer, @TrustVanta, and more than 1,000 of the world's most ambitious companies.
In the last 12 months, demand has surged, with total revenue growing 8x. We will use the funds to accelerate product development, expand our data centers, and continue hiring world-class talent.
Aaron retweeted
Ray Kim, Mobile Engineer at @classpass: “We evaluated many options, and Namespace is the only one that could deliver the performance our iOS team needed.”
Before Namespace, Mac runners made up about 90% of ClassPass's CI spend, a concentration the team kept having to justify.
With Namespace, they not only sped up their CI but also cut costs by 55%.
Aaron retweeted
Welcome to the newest additions to our logo wall.
We're proud to support some of the fastest-moving companies in the world. And we're just getting started.
Aaron retweeted
All our products are powered by the same underlying core infrastructure.
Egress policies to control outbound connections are part of that foundation, so they’ve been part of Namespace Devboxes since day 1.














