Namespace (@namespacelabs) / X

Namespace

394 posts

Namespace

@namespacelabs

Accelerate your dev workflow, without changing your existing tools (w/ GitHub actions, Docker, etc). Trusted by @TrustVanta @VerkadaHQ @framer and many more.

namespace.so

Joined September 2021

Following

1,173

Followers

Namespace
@namespacelabs
2h
We are happy to support @computesdk! They launched thousands of instances, each one issuing thousands of concurrent requests, on a software stack that was continuously being updated. Exactly the type of workloads Namespace is designed for.
ComputeSDK
@computesdk
4h
Last week we announced the results of the scale invitational. Link to the full results in the 🧵 It's our latest benchmark powered by @namespacelabs. With backing from our excellent long term partners. @latitudesh @browserbase @TigrisData @neondatabase @GitBookIO
1.7K
Namespace reposted
ComputeSDK
@computesdk
Jun 19
🚨 Benchmark Friday 🚨 After weeks of work from us and the participants, today we are excited to release the results of the 2026 100k Scale Invitational. Over the next hour we'll be releasing each set of results. Huge shoutout to @namespacelabs for powering our benchmarks!
626K
Namespace
@namespacelabs
Jun 19
Behind every API, webhook, event pipeline, there are people trying to keep things running. And keeping these things running is not an easy task. At Namespace, we try to work with those people. Earlier this week, Gihub events were dropping fields we depend on and customer jobs
144
Namespace
@namespacelabs
Jun 18
New features across Devboxes, Bazel, and macOS to cut overhead from your build and dev workflows. 🔲 Devboxes now support leasing by tag, ephemeral mode, snapshot restore, and spec file configuration for secrets and egress policy. ⚡ Bazel Remote Build Execution is in early
118
Namespace
@namespacelabs
Jun 17
If your GitHub Actions feel slow, the usual causes are underpowered runners and cold caches. Namespace addresses both: high-performance hardware, NVMe caching that persists across runs, and a one-line migration. Get started here: namespace.so/docs/solutions…
GIF
103
Namespace
@namespacelabs
Jun 12
We built a first class integration for Claude Managed Agents. The harness orchestrates & uses the tools it needs. You manage a Devbox configuration, and the lifecycle management is done for you. Simple and powerful. A Namespace Devbox for each one of your agents.
Claude
From namespace.so
474
Namespace
@namespacelabs
Jun 2
Four agents, four test suites, one overheating Mac. Run the tests in a Devbox. 🔄 Sync uncommitted changes ⚡ Ephemeral environments 📦 Custom prebuilt images `$ npx skills add namespacelabs/agent-skills` Read more: namespace.so/blog/devbox-te…
368
Namespace reposted
Heavybit
@heavybit
Jun 1
On episode 52 of The Kubelist Podcast, Marc Campbell (@marccampbell) and Benjie De Groot (@shipyardbuild) speak with Hugo Santos. They discuss the evolution of @namespacelabs, why traditional cloud infrastructure isn't always optimized for dev workflows, and what it takes to
00:00
433
Namespace
@namespacelabs
May 27
Quite a bit has shipped over the last few weeks. Here are the highlights: 🤖 Claude Managed Agents: Anthropic owns the agent loop, you own the execution environment 🌐 nscr.io now supports custom domains. Serve your workspace images under a custom domain with
410
Namespace
@namespacelabs
May 21
We're introducing first-class support for Claude Managed Agents on Namespace Devboxes. Agent quality is bounded by environment quality: if a build takes 3 minutes, the agent waits 3 minutes between iterations. Devboxes are built for code workflows. Fast startup with large
1.2K
Namespace reposted
Hugo Santos
@20thr
May 18
Love to see our customers on this list. ❤️
Brex
@brexHQ
May 18
BREX DATA: Spring 2026’s top 25 fastest-growing software vendors.
435
Namespace
@namespacelabs
May 18
Things engineers are doing to keep their Claude Code session alive: → Walking through airports with their laptop ajar → Boarding flights at the last possible second → Untying their kids' skates while watching the screen over their shoulder It doesn't have to be like this.
556
Namespace
@namespacelabs
May 12
Another npm supply chain attack, this time TanStack, 84 packages, millions of weekly downloads. As these things keep happening, we need to keep building security layers. So, when one thing fails, it doesn't take everything with it. Here is how we think about security.
Namespace
@namespacelabs
May 5
No single control is enough. Here's how we think about layering security so that when something fails, everything else still holds. Read more: namespace.so/blog/defense-i…
224