Top all-time · #6897
RWX
Company blog · rwx.com/blog · on HN as dan_mangesprogrammingsystems
RWX is the company blog at rwx.com, writing about programming and systems. Since 2022, 11 different Hacker News readers have linked it 33 times, most often “RWX: CI/CD platform for the agentic dev cycle”. No feed was found, so read it on the site itself.
Too few sampled comments (5) to say how often HN recommends it.?
Why HN links it
HN commenters link RWX's posts on CI/CD, GitHub Actions caching, and Forgejo support. The comments mostly describe and promote the RWX CI platform rather than judge the writing.
Summarised by Claude from a sample of 5 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
RWX is the CI/CD platform for the agentic dev cycle. Validate changes without a commit. Give your agents sandboxes that share your build config and cache.
Most-linked posts?
- RWX: CI/CD platform for the agentic dev cycle2 people · 2 mentions · first linked 2026-01-14
- The Paradigm Shift of CI/CD as a DAG of Tasks2 people · 2 mentions · first linked 2024-05-20
- We deleted our Dockerfiles: a better, faster way to build container images2 people · 2 mentions · first linked 2025-11-24
What Hacker News says?
A new CI/CD platform. Local CLI (run without git push), remote debugger, automatic content-based caching, DAG-based definition, and dynamic tasks. It’s taken a lot of work to build it, but I’m really excited about how well it’s working. https://rwx.com/mint
Comment linking /mint
on “Ask HN: What are you working on (August 2024)?”Submitted We deleted our Dockerfiles: a better, faster way to build container images as a story · 13 points
HN discussion(Disclosure: I'm a cofounder of RWX) For anybody wanting to solve similar problems and considering Bazel, take a look RWX. It's built around the same concepts of content-based caching and graph-based task execution, but it's far more runtime agnostic and easier to adopt. https://rwx.com
Comment linking /
on “AI coding has made CI a bottleneck, so we reworked ours to keep up”Submitted Git Push to Run CI/CD Is a Terrible Developer Experience as a story · 6 points
HN discussionRWX | Software Engineer | REMOTE (US) | Full-time | https://rwx.com $175K – $250K + equity We're a CI/CD platform with an entirely differentiated execution model. Rather than parallelizing jobs on VMs, we provide a serverless interface using a graph of tasks. We then have automatic, content-based caching, which eliminates the large amount of redundant executions that CI platforms have today. You can test changes fro…
Comment linking /
on “Ask HN: Who is hiring? (July 2025)”Submitted What would GitHub Actions look like if you designed it today? as a story · 4 points
HN discussionWe support anchors in our CI/CD syntax at RWX, but only in a specific `aliases` section. I think this is a nice compromise. aliases: common-env: &common-env key1: value1 key2: value2 tasks: - key: some-task run: ... env: <<: *common-env https://www.rwx.com/docs/mint/aliases
Comment linking /docs/mint/aliases
on “Dear GitHub: no YAML anchors, please”Submitted Proposal for a New Way to Build Container Images as a story · 3 points
HN discussionIt's pretty amazing to see what Blacksmith, Depot, Actuated, etc. have been able to build on top of GitHub Actions. At RWX we got a bit tired of constantly trying to work around the limitations of the platform with self-hosted runners, so we just built an entirely new CI platform on a brand new execution model with support for things like lightning-fast caching out of the box. Plus, there are some fundamental limita…
Comment linking /blog/retry-failures-while-run-in-progress
on “Reverse engineering GitHub Actions cache to make it fast”Submitted Designing a Software Supply Chain for Security and Reliability as a story · 3 points
HN discussionThere's a difference between small scale CI and large scale CI. Small scale: a project is almost small enough to run the build and tests locally, but you still want to have a consistent environment and avoid "works on my machine" problems. Large scale: a project is so large that you need to leverage remote, distributed computing to run everything with a reasonable feedback loop, ideally under 10 minutes. The opposit…
Comment linking /
on “Using Radicle CI”Submitted The Paradigm Shift of CI/CD as a DAG of Tasks as a story · 3 points
HN discussionWe're solving a lot of these problems with Mint: https://rwx.com/mint Key differentiators: * Content-based caching eliminates duplicate execution – only run what's relevant based on the changes being made * Filters are applied before execution, ensuring that cache keys are reliable * Steps are defined as a DAG, with machines abstracted away, for better performance, efficiency, and composition/reuse
Comment linking /mint
on “Your CI pipeline isn't ready for AI”Submitted Using an MCP Server to Fix Tests That Failed on CI as a story · 2 points
HN discussionWe just released support for Forgejo with RWX CI/CD: https://www.rwx.com/docs/getting-started/forgejo
Comment linking /docs/getting-started/forgejo
on “Why I'm leaving GitHub for Forgejo”Submitted Preventing Cache Races as a story · 2 points
HN discussionThere's three main things we do to solve this, all of which relate to the fact that we have our own (OCI-compatible) container runtime under the hood instead of using Docker. 1. We don't gzip layers like Docker does. Gzip is really slow, and it's much slower than the network. Storage is cheap. So it's much faster to transmit uncompressed layers than to transmit compressed layers and decompress them. 2. We've heavily…
Comment linking /blog/we-deleted-our-dockerfiles
on “GitHub Actions Is Slowly Killing Your Engineering Team”Submitted Mint CI/CD 1.0 is now available as a story · 2 points
HN discussionAs a (very happy) RWX customer: - Intermediate tasks are cached in a docker-like manner (content-addressed by filesystem and environment). Tasks in a CI pipeline build on previous ones by applying the filesystem of dependent tasks (AFAIU via overlayfs), so you don't execute the same task twice. The most prominent example of this is a feature branch that is up-to-date with main passes CI on main as soon as it's merge…
Comment linking /docs/rwx/tool-caches
on “GitHub Actions Is Slowly Killing Your Engineering Team”Submitted Test results can be so much richer as a story · 2 points
HN discussionYou should try RWX! You can trigger runs from the CLI for way faster feedback loops. The automatic caching is surprisingly good too. https://www.rwx.com/
Comment linking /
on “I Hate GitHub Actions with Passion”Submitted Strategies for Handling Flaky Tests as a story · 2 points
HN discussionSubmitted RWX: CI/CD platform for the agentic dev cycle as a story · 1 points
HN discussionSubmitted RWX raises $12M as the eng bottleneck moves from writing code to validating it as a story · 1 points
HN discussionSubmitted RWX now supports Codeberg and Forgejo as a story · 1 points
HN discussionSubmitted Work in Progress Commits Are a Thing of the Past as a story · 1 points
HN discussionSubmitted Zero Configuration CI/CD Observability on RWX Using OpenTelemetry as a story · 1 points
HN discussionSubmitted The Paradigm Shift of CI/CD as a DAG of Tasks as a story · 1 points
HN discussionSubmitted Docker-Like Layer Caching on VMs as a story · 1 points
HN discussionSubmitted GitHub Actions is vulnerable to supply chain attacks as a story · 1 points
HN discussion