Namespace Labs
@namespacelabs
Followers
582
Following
2
Media
34
Statuses
215
Speed up your development and testing workflows using your existing tools. (Much) faster GitHub actions, Docker builds, and more. At an unbeatable price.
Joined September 2021
Don't wanna be here?
Send us removal request.
Explore trending content on Musk Viewer
#MiamiGP
• 335653 Tweets
Lando
• 332869 Tweets
Oscar
• 150997 Tweets
Bernard Hill
• 128430 Tweets
Charles
• 116791 Tweets
Menotti
• 112621 Tweets
Cinco de Mayo
• 111808 Tweets
Luciano
• 105900 Tweets
GW最終日
• 104409 Tweets
Verstappen
• 99520 Tweets
Perez
• 94563 Tweets
Lewis
• 76893 Tweets
McLaren
• 67314 Tweets
Cavs
• 62903 Tweets
Hugo
• 58528 Tweets
Flaco
• 56201 Tweets
Vélez
• 52479 Tweets
Vitória
• 45427 Tweets
Leclerc
• 42939 Tweets
Sporting
• 40434 Tweets
Rangers
• 39030 Tweets
Benfica
• 34697 Tweets
Sainz
• 34181 Tweets
Paolo
• 31243 Tweets
連休最終日
• 29694 Tweets
Mika
• 29317 Tweets
Piastri
• 28721 Tweets
#f1jp
• 26985 Tweets
Checo
• 25577 Tweets
Marquês
• 19943 Tweets
Safety Car
• 16877 Tweets
Pinned Tweet
Heard today: "I have now put probably over a million of minutes through namespace and god knows how many local builds and hot damn, it is a killer addon to our workflow."
0
3
6
Coming very soon: Go server production images will use
@chainguard_dev
base Wolfi images. Goodbye and thank you for all the fish distroless, you did a good job.
1
4
31
OIDC all the way. No manual handling of secrets.
We love Workload Federation here at Namespace.
Each instance gets its own workload-specific credentials which you can use to federate with other services.
We love it so much we don't even provide static pre-shared tokens yet.
3
4
19
After spending so much time debugging CI, we wanted a simple way to jump in, understand and fix workflows.
Today we're releasing Breakpoint, our go-to solution to help debug CI failures; create breakpoints and dial in with SSH, no new software needed.
100% open-source.
1
6
15
Breakpoints in GitHub Actions? After spending so much time in GH debugging workflows, we wanted a simple way to jump in and debug. Coming out tomorrow, fully open-source.
1
3
15
Part of our job is helping you make your developer workflow go faster.
The first step of optimization is understanding, and data gathering.
That's why now every *docker build* issued in Namespace gets its own trace view.
2
3
14
Oh that's us! We love Nix, have a great time!
2
2
12
This. Tests must be representative. Mocks trade ease of use and speed of execution for correctness. We should make functional/integration tests simpler to build and faster to run instead.
Mocks in tests are mostly a happy story you are telling to yourself. In the better case, you're repeating what you've expressed yourself before in your actual code. In the worst case, you're retelling someone else's story, without being quite sure about all its details.
28
33
208
0
2
11
We heard from customers that they were seeing failures with GitHub's cache from time to time. Reducing their cache hit ratio, and sometimes even failing runs.
So in Namespace-style we went ahead and introduced an alternative that is 💪 more robust and 🏎️ faster.
👇 See below.
1
3
11
June's been great: here's changelog
#007
.
But before that: a huge thank you to all our new users.
It's been great to work with you all. Thank you for sharing the journey with us. We'll bring you the best development platform we can.
Now with the updates.
1
2
10
Develop and test faster: you can now create ephemeral environments in seconds which you can ssh into even after your CI runs finish. Build faster, with incremental building on any docker build. More updates on changelog
#005
.
0
3
9
Looking for a nice side-project to check during the holidays? Check out :-)
Our team is winding down for a few days to enjoy the holidays. We wish everyone a great 2023. 🎄🎊
1
2
9
How quickly do you like your kubernetes clusters created and why is it in a few seconds?
3
1
9
Use docker build, or kubernetes clusters in CI? Help us test out ! Get high performance versions of docker build + kubernetes clusters for testing in your existing CI workflows for free, during our Early Access, with virtually no configuration change.
0
3
8
Today we're introducing Cache Volumes: turn the incrementality in your GitHub Actions runs to 11.
Including:
- Zero-latency package/build results caching
- Docker image cross-invocation caching
- Pre-installing dependencies
- Fast monorepo checkouts
And more (a thread)
1
6
8
We freshened up the Ephemeral Clusters early access page at Seamlessly use with Github Actions, or via the CLI. And in the coming days, you'll be able to create clusters programmatically as well. And soon... the reveal of a game-changing feature. 👀
0
3
8
We're testing out a new product (Ephemeral Clusters) and need your help! Zero-setup Kubernetes clusters created in a few seconds (real cluster, privileged supported, etc) that are great to use in CI. Join our Discord to join the private early access. 1/
1
8
8
It's pretty cool that we have new customers coming in, and in their first days they end up creating thousands of VMs.
1
2
7
Before finding our caching capabilities, remote builders, and more, folks usually come into Namespace because we help them save money.
In 5 minutes, you're set to save on GitHub Actions.
1
3
7
We've updated , it needed a refresh! Book a demo with the team, we'd love to show you the product. :-) Coming soon, posts with recorded examples, our roadmap, and our belief in open-source.
1
2
7
With Namespace you get onboarded in minutes rather than days. Install the ns CLI, run `prepare` and you're ready to go. All dependencies and environments required for development are then available. No more dependency management. Learn more at
1
0
7
We have a few new things coming up over the next weeks... but before that, a quick demo of some of the features we've released in April. We wanted to have a quick way to test out changes in PRs, so we made Previews. We needed faster builds, so we made Remote Builders. And more.
1
6
7
Namespace 💙 open-source. With Docker's recent changes in support for open-source projects, we're considering providing a free open-source tier in , adding a public registry, in addition to the existing private registry. Let us know if you'd be interested.
0
3
7
Tired of slow, expensive, Github Actions? We are too!
Now you can speed up your Github Action workflows; in the same place you get fast remote builders, and ephemeral test capacity. And there's more coming.
Learn more below.
1
2
7
We've just added remote build cluster support to the Early Access! Build any Dockerfile in a high-capacity cluster and push the resulting images to our managed private registry, zero-conf. Turn-key and not limited by how fast your CI worker goes. Check out
0
2
7
We love pricing with no gimmicks. No hidden costs.
And we love pricing pages that do the math for us.
Can we make it clearer? Let us know.
1
1
6
Friday, it's changelog time!
0
0
6
It's been a while since we sat down with a summary of what's new. But here it is. Changelog
#008
.
- Cache Volumes are a game changer in CI
- Large(r) runner support (32c 128gb ram)
- Public APIs
- GitHub action savings calculator
And more! (link below)
1
2
6
We've been working on making remote previews as simple as "docker run" or "docker compose up". Check it out.
2
0
6
100 new simultaneous clusters in 37s. We recently saw a great demo of spawning 100 new clusters in 8 minutes. We love performance so we wanted to check how would we perform. It’s not quite apples to apples but let’s have some fun. :-) 37 secs cold start to 100.
1
3
6
Instant Previews was one of the features that piqued the most interest at
#kubecon
; but how do you actually get feedback in seconds?
0
3
6
One of the biggest performance pain-points we hear from folks are slow Javascript/Typescript builds/tests. We're doing something about it.
Here's a few examples where we are 2x faster on building and testing frontend code.
Change one line, and get faster. It's that simple.
👇
1
2
6
The changes have landed! Go servers built by Namespace now use Chainguard base images by default. Thank you to all the folks at
@chainguard_dev
for the great work on Wolfi and Chainguard Images. Coming next: Nodejs base images, and our builders.
1
5
6
We are going to Kubecon Europe 2023! Our first booth too. Can’t wait to meet you all.
0
3
6
Now that was fun! See below for a Namespace intro and come join us on Discord and Github!
"Potentially my favorite project of 2022" 🤯 Just wrapped up my chat with
@rawkode
about
@namespacelabs
-- had a ton of fun! Thank you David for the opportunity.
1
4
15
0
0
6
Our Managed Runners are fast. But how fast? We did a case study with the open source repository of an application we use and love. We saw numbers between 2x and 1.5x faster. And the cherry on top? It would still be 80% cheaper than the comparable GitHub runners. 🔗 in the thread.
1
4
6
Recently we've been working with a few folks that would like to bring their own compute, but make use of our orchestration and make-vms-fast magic. If you're on AWS or GCP and would like to have your own version of micro-vm backed serverless containers, let's have a chat!
0
2
5
We could have put our workload federation features into a separate price tier, but we didn't.
They're part of all of our plans.
We care deeply about security and want the best tools available to you.
Security without compromises.
2
1
5
We're starting to rollout native ARM64 build support to Remote Builders. We're excited about it, but generally it's been great to see folks getting faster incremental builds that are a drop-in to "docker build", with a single change. More in the🔗
1
1
5
We love Docker. But we wish it handled more of our developer journey. So we built Namespace.
No more writing Dockerfiles by hand. No more unreproducible CI failures. And more!
Moving from Docker Compose to Namespace in our latest blog post
0
2
5
@0xE282B0
did something pretty cool w/ his WASM on Namespace demo.
And it got us thinking: Should we add a simple flag to enable WASM containers in our clusters?
Would probably be the simplest way to try WASM containers in your familiar Kubernetes environment.
1
3
5
We're looking forward to
#Unpacked23
!
We care deeply about software provenance and enforcing that the bits we produced, are the bits actually running.
We're excited to learn about what our partners are doing to help.
June 20th -- see you there!
JUST OVER ONE MONTH TO GO UNTIL
#Unpacked23
!
Register >
Join us June 20th for:
🤩 Awesome content for
#DevOps
+
#DevSecOps
Leaders
👀 Virtual expo featuring community sponsors you know + love
🏆 Swag and gift card giveaways
👯 Networking opportunities
🌎…
0
0
3
0
2
5
It's our first changelog!
0
1
5
Some sweet tips for the weekend.
0
1
5
Our team put together a guide to Namespace's Remote Builds; a drop-in replacement for Docker build, but faster, and with more observability. One of the ways we're making container-based development and testing better for teams.
0
1
5
Don’t mock your dependencies! Browser-based tests against a production-like stack can be easy with the right platform.
0
0
5
Not sure about the name but we are all in on ephemeral whole-system environments. It builds on our Google heritage; we’ve seen in action how productivity increases with whole system test coverage. And now we are building it for everyone.
1
0
5
People are often surprised that with Namespace you get your GitHub Actions CI to go at least twice as fast with a single line change to your workflow file.
But it’s that simple.
And you can easily try it out in a PR without any commitments.
0
1
5
We have a unique approach to infrastructure dependency management. Dependencies should be simple to use and manage. Also typed and encapsulated! We call them Resources. Explore resources in this post, and see how easy it is to use minio and
@_localstack
1
1
5
Turbo-charged environments, transparent Docker support from your workstation, native arm64, breakpoints, oh my! It's Changelog
#6
.
1
2
4
We're getting started with our Mac/Silicon (m2pro) Early Access; with support for GitHub Actions, Buildkite, and generally ephemeral compute. Drop us a note at support at if you'd like to be in the early access.
0
2
4
Minimal configuration for a Go server. No Dockerfile, no Docker compose, just `ns dev` and deploy changes continuously to a local Kubernetes cluster. With incremental builds, and cross-platform support.
0
2
4
If you use Nix with GitHub Actions you should use
@DeterminateSys
's magic-nix-cache action.
It will turn your multi-minute builds into 30s-1min.
If you want to bring it down further to a couple tens of seconds, check out Namespace's cache volumes.
1
2
4
@PraveenPerera
Hey! We're bringing up some new capacity in the US by end of the month. Drop us a quick note to support
@namespace
.so and we'll add you to the queue to be moved.
1
0
1
Feels great to move development between local instances and the cloud in a single command (`prepare local` vs `prepare eks`). And soon you'll be able to boot up a subset of your stack locally while using the rest of your production stack. Still Kubernetes, but now simple.
@dberkholz
Agreed; we need the flexibility. And the options at the moment feel like they treat cloud and local development as strictly separate.
@namespacelabs
blends the target environment into a single overflow—the same experience, whether the target is remote/cloud or local.
0
0
3
0
1
3
@ThePracticalDev
And to build them quickly in any environment, try out Namespace remote builders. 100% compatibility with `docker buildx` -- but remote and fast. Check out and let us know what you think!
0
0
3
Over here at
@namespacelabs
we think
@_localstack
is a great way to support local development, and we're excited to see how developers can leverage it in our development environments.
0
1
3
If you believe the answer is single digit seconds join us at for some news on early access soon.
How quickly do you like your kubernetes clusters created and why is it in a few seconds?
3
1
9
0
0
3
You can now register directly at Looking forward to seeing you!
We're testing out a new product (Ephemeral Clusters) and need your help! Zero-setup Kubernetes clusters created in a few seconds (real cluster, privileged supported, etc) that are great to use in CI. Join our Discord to join the private early access. 1/
1
8
8
0
1
3
Friday -- it's Formula 1 weekend time! Oh, Changelog too!
0
0
3
End-to-end tests don't have to be slow.
- Fan-out each variant of the app being tested into an instance with its own resources.
- Expose the app securely to the caller (TLS+workload identity).
- Run cypress against the target.
0
1
3
If you use GitHub Actions, or do Docker builds in CI, chances are high that we can get them to be 25-50% faster out of the door with no changes.
Our customers are testing faster, and cheaper, without having to change their workflows.
1
0
3
Whole-system testing couldn't be easier. Namespace instantiates whole stacks ephemerally on separate Kubernetes namespaces and runs tests as real clients inside the cluster. Representative and without mocks. Learn more at
0
2
3
Get a demo of our new environment and resource orchestration in
#KubeCon
#CloudNativeCon
! Better DX for microservices - fast edit-refresh development and collaboration with ephemeral prod-representative environments for e2e tests, previews, CI.
Book a slot
0
1
2
And we have a few new bits coming soon... including Mac Silicon support, and our SOC 2 certification.
Read more at
0
0
2
We've updated with a series of feature highlights. Today: multi-language support. Build and deploy servers of different languages using a single unified developer experience that offers best-in-class per language.
0
1
2
We're headed to KubeCon in Amsterdam very soon! Looking forward to meeting you there. Come to SU32, grab some goodies, and chat with the team.
1
3
2
We have a few more features we'll be adding (checkout the roadmap), but we'd love your feedback and help.
We're also making available a free-to-use rendezvous server so adding breakpoints as simple as adding another action to your workflow.
1
0
2
Our docs just got a fresh coating of paint! We've also added a bit more about our current feature-set, and our roadmap.
0
0
2
👀
tfw when the CI became so much faster 🤯
Go lint: 2m -> 19s
Unit tests: 2m -> 49s
E2E tests: 7m -> 3m
5
0
18
0
1
2
🤯
You can now extend
#Kubernetes
clusters with
#Wasm
shims and they start in < 10 sec. 🤯
The fastest way to develop Wasm containers on Kubernetes! Cluster creation and deployment of
@spinframework
demo < 30 sec
@namespacelabs
#DevEx
2
11
23
0
0
2
👀🤗
We've added a few more features to high-performance build clusters, near instant log streaming, in-browser terminals. Every week we're shipping awesome features, go team!
0
2
7
0
0
2
Join us on Discord to get an early peek at new features and posts!
0
0
1
@Avinesh__T
Thanks! Let us know what you think. Everyday we improve Namespace based on community feedback.
0
0
1
We are looking for folks with a passion for infrastructure and developer tools to join our journey! Find out more at
0
1
1
Try it out at
0
0
1
Dive into this journey and upgrade your development happy path; you can start by trying out Ephemeral Clusters at
0
0
1
Not just nodejs, but also Go!
@sidpalas
Love these—very informative! If you don’t want to have to maintain these Dockerfiles by hand, you can also just use the nodejs integration in
@namespacelabs
foundation and end up with a similar container image, which improves over time!
0
0
2
0
0
1
We have been spending some time thinking through ways that we can help developers focus on building their own products, rather than wrangling infrastructure. How many times do we need sort out build, test, security, prod? Sign up for a sneak peak at .
0
0
1
@skaragulm
100%. As some resources in Kubernetes are not namespace-isolated, we prefer to create new clusters to ensure that whole system tests run in isolation. And we've also seen folks create separate clusters for different features they're working on. But not a one-fit-all solution!
0
0
1
And soon, traces will highlight cpu or i/o contention; or simply network or lock time that your builds spend time on.
0
0
1