Top all-time · #7642
Namespace
Company blog · namespace.so/blogsystemsprogramming
Namespace is the company blog at namespace.so, writing about systems and programming. Since 2023, 10 different Hacker News readers have linked it 19 times, most often “Namespace – San Francisco/ New York / Zurich| Full-Time – Remote/Hybrid”. It is still writing: the last post was on 2026-10-14, and you can follow it by feed.
Too few sampled comments (7) to say how often HN recommends it.?
Why HN links it
HN commenters link namespace.so as the homepage of Namespace, a hosted CI and build service for GitHub Actions-style workloads. The comments discuss the product, not any blog writing.
Summarised by Claude from a sample of 7 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Cloud agents on Devboxes, fast GitHub Actions runners, and remote execution for Bazel on Linux, macOS, and Windows. The developer platform for agent scale.
Most-linked posts?
- Namespace – San Francisco/ New York / Zurich| Full-Time – Remote/Hybrid3 people · 7 mentions · first linked 2023-06-01
What Hacker News says?
Namespace fixed all of the issues I had with GitHub Actions. Ghostty uses them to build their project: https://namespace.so Using Namespace made it clear how much cruft GitHub Actions has accumulated and how much performance they leave on the table. I regard GitHub Actions like Nix: weird configuration, largely shell-based, and the value you get out is commensurate with the investment you put in. But it works well e…
Comment linking /
on “Migrating the main Zig repository from GitHub to Codeberg”Submitted How we made container image loading fast as a story · 3 points
HN discussionI spend a lot of time in CI (building https://namespace.so ) and I agree with most of this: - Treat pipelines as code. - Make pipelines parts composable, as code. - Be mindful of vendor lock-in and/or lack of portability (it is a trade-off). For on-promise: if you're already deeply invested in running your own infrastructure, that seems like a good fit. When thinking about how we build Namespace -- there are parts t…
Comment linking /
on “The Pain That Is GitHub Actions”Submitted Namespace: We've raised $23M to build the compute layer for code as a story · 3 points
HN discussionNamespace | San Francisco, CA / New York, NY / Zurich, Switzerland / Remote | Full-time | REMOTE or HYBRID | https://namespace.so At Namespace, we’re building a global, vertically integrated infra stack (custom server racks, hypervisor, scheduler, and much more) for the next wave of software development. We’re hiring for the following openings * Security Engineer * Product Engineer * Infrastructure Software Engineer…
Comment linking /careers
on “Ask HN: Who is hiring? (October 2026)”Submitted So you want to build your own datacenter as a story · 3 points
HN discussion100% -- EC2's general purpose nature is not in my opinion the best fit for ephemeral use-cases. You'll be constantly fighting the infrastructure as the set of trade-offs and design goals are widely different. This is why CodeSandbox, Namespace, and even fly.io built special-purpose architectures to guarantee extremely start-up time. In the case of Namespace it's ~2sec on cold boots with a set of user-supplied contai…
Comment linking /
on “Making EC2 boot time faster”Submitted Eight biggest learnings when preparing for our first KubeCon as a story · 3 points
HN discussionHi -- Namespace's CEO here; if you have a chance, please drop me a note at hugo-at-namespacelabs.com; I'd love to hear what we could be doing better in the UI, and product overall. Thank you! Hugo @ Namespace ( https://namespace.so )
Comment linking /
on “Cache is King: A guide for Docker layer caching in GitHub Actions”Submitted I Gave 100 Fly Brains Their Own Computers to Play Doom as a story · 2 points
HN discussionNamespace | San Francisco, CA / New York, NY / Zurich, Switzerland / Remote | Full-time | REMOTE or HYBRID | https://namespace.so At Namespace, we’re building a global, vertically integrated infra stack (custom server racks, hypervisor, scheduler, and much more) for the next wave of software development. We’re hiring for the following openings * Security Engineer * Product Engineer * Infrastructure Software Engineer…
Comment linking /careers
on “Ask HN: Who wants to be hired? (October 2026)”Submitted Hunting a delayed deadlock that hid for two years in a tiered Bazel cache as a story · 2 points
HN discussionNamespace Labs https://namespace.so Looking for: Frontend / Design Engineers GTM / DevRel Prefer near CET tz; remote friendly. Namespace wants to help developer teams do more with less: faster cycles, and more focus on what matters. Email me directly: hugo AT namespacelabs.com Competitive pay and generous equity. We believe in shared incentives.
Comment linking /
on “Ask HN: Who is hiring? (June 2023)”Submitted Namespace – San Francisco/ New York / Zurich| Full-Time – Remote/Hybrid as a story · 1 points
HN discussionGitHub is free, but the runners are slow and increasingly unreliable. I use Namespace ( https://namespace.so ) and I hook it up both to my personal GitHub as well as my personal Forgejo. I’m in the process of moving from the former to the latter!
Comment linking /
on “Moving from GitHub to Codeberg, for lazy people”At Namespace, we’re building a global, vertically integrated infra stack (custom server racks, hypervisor, scheduler, and much more) for the next wave of software development. We’re hiring for the following openings * Security Engineer * Product Engineer * Infrastructure Software Engineer * Customer-Facing Software Engineer * Engineering Lead Today, we power software development for SpaceXAI, Ramp, Sierra, Fal, Vant…
Comment linking /careers
on “Namespace – San Francisco/ New York / Zurich| Full-Time – Remote/Hybrid”We do - https://foundation.namespace.so/docs . Some feature of "Namespace" are kind of similar to Ergomake, but we use own format with CUE instead of docker-compose. Here is comparison to docker-compose - https://namespace.so/blog/from-docker-compose-to-namespace .
Comment linking /blog/from-docker-compose-to-namespace
on “Docker-compose.yml as a universal infrastructure interface”