Building the next generation of CI/CD: @rwx. Previously built @RootInsurance (IPO) and @braintree ($800M acq)
Columbus, OH
Joined February 2008
- Tweets2K
- Following1.5K
- Followers2K
- Likes4.1K
You can get a lot of compute reduction from graph-based execution and content-based caching (Bazel or RWX) before you have to resort to running fewer tests. although that may be necessary eventually
We are either going to need more compute, or better CI.
AI driven dev means more code/tests and more frequent changes trying to merge and deploy to production.
E.g. 10× the changes × 5× the test suite cost = 50× the compute (and higher peak compute demand due to parallelism).
And that's before you rebase a few times to keep up with the fast moving trunk, then battle a merge queue due to flaky tests.
There are a few things everyone should be doing. First off, you make your test suites leaner and faster. High signal units, massive parallelism, thoughtful end-to-ends.
What needs to come next is compute reduction. You should only run the tests that relate to the change you are testing. The next step is getting even smarter. Models can be used to predict which subset of the related tests are most predictive of failure which lets you get to the failure fast and avoid unneeded subsequent test runs.
We've worked with the team at @cursor_ai to build and launch a first-class integration between Cursor Origin and @rwx
Origin’s landing page says, "Code is moving faster than any infrastructure was built to handle. Origin was designed for this moment."
Similarly, RWX is the CI platform uniquely built for this moment.
I've built with Rails throughout my career. I'm excited to have @rwx sponsoring this year.
Rails World wouldn't be possible without the support of many sponsors. This year in Austin, be sure to stop by the Sponsor Lounge and meet our Gold sponsors: @PlanetScale, @HuntressLabs, @jetbrains, @rwx, @SerpApi (also one of our coffee sponsors!), and @clio_labs (also sponsoring the pre-registration event). Find them at their booths, say hello, and learn more about what they’re building.
Big thanks to all of these Gold Sponsors for your support this year. rubyonrails.org/world/2026/ #railsworld
Dan Manges retweeted
2x the builds, half the duration — that's what @honeycombio saw after switching from CircleCI to RWX in March 2026.
@lizthegrey (Technical Fellow at Honeycomb) included the exhibit below in the company's blog post, "AI Amplifies Your Existing Practices: Lessons from Our Shift to an AI-First Strategy."
As Liz puts it: "Fast CI is no longer a nice-to-have. It's now a precondition for AI throughput to be worth anything at all."
Read Honeycomb’s full post: honeycomb.io/blog/ai-amplifi…
Seconded. But with content-based caching, you don't even need the attestations. If the agent loop ran CI, then when the PR is opened, the entire run will be a cache hit and finish in one second. That's how we do it with @rwx
We've moved our CI for swamp inside the agent loop, and have it produce full attestations of the work, which we validate when a merge happens. It's faster, it's more flexible, and I really think it's the way forward. stack72.dev/ai-broke-the-ass…
surely the people who make internet standards can come up with a better way to achieve public suffix list behavior for domains without maintaining a 16,000 text file that is embedded into devices
this problem doesn't exist on @rwx because of the graph-based execution model. 1 push = 1 git clone in CI regardless of how much parallelism downstream.
datadoghq.com/blog/engineeri…
Filing this one under examples of why you should pin your runtime dependency to a specific version. Performance regression in Ruby 4.0.6
github.com/ruby/ruby/commit/…
Dan Manges retweeted
Coalesce lowered CI costs by 50% and achieved 4x faster CI feedback loops by leaving GitHub Actions and moving to RWX.
“Switching to RWX for CI not only enabled us to accelerate feedback loops, but it also helped our developers regain confidence in shipping larger, more ambiguous changes. That benefit alone has been a massive unlock for us.” - Mike McCune , VP of Engineering at Coalesce.
rwx.com/customers/coalesce
Dan Manges retweeted
Been working on this and using it for a long time...stoked to finally share it with a wider audience! 😁
Today we’re introducing Delta. Delta is a multiplayer environment for coding with agents and reviewing what they build, powered by DeltaDB.
The first invites to our private beta are going out now.
zed.dev/blog/introducing-del…
Dan Manges retweeted
@bonusly reports a 75% reduction in build times and a 65% improvement in deployment reliability since adopting RWX's dev cloud in 2025.
“RWX singlehandedly changed how our team approaches the development cycle. Our engineers fully trust the platform, and our CI/CD pipeline has never been faster.” - Jeremy Thomas, SVP of Engineering at Bonusly
Read the case study: rwx.com/customers/bonusly
The limiting factor in software engineering is no longer writing code. It's validating it. Every major shift in software development has required new infrastructure, and AI-driven engineering is no different. @rwx is the dev cloud built specifically for that transition.
I’m excited to announce we raised $12 million in Series A financing led by @hydeparkvp with angel investors including @theo, @bryan_johnson and Jenkins creator @kohsukekawa participating.
rwx.com/blog/series-a?utm_so…
Dan Manges retweeted
I've been to a lot of conferences, and the new high water mark for "best energy in the room" was Software Should Work this past week. 🥇
The speakers had great talks, AND the audience was super excited about the topics. The vibes were incredible.
What an amazing conference! 😍
The best part about building RWX is engaging with engineering teams who strive to use the very best dev tools. Honeycomb has a talented team, and we've loved having so many good ideas flowing through our shared Slack channel.
RWX can send telemetry from CI/CD executions into any OpenTelemetry provider, and we send data for our own pipelines into Honeycomb. It's a fantastic platform.
Bold teams tend to spot the shift early. @honeycombio helped redefine observability. When they needed to accelerate delivery, they turned to RWX:
"Our CI system couldn't keep pace with AI-assisted development. RWX's content-based caching changed how we thought about CI."
rwx.com/customers/honeycomb
Dan Manges retweeted
Conference alert: The incredible @isaacvando from our team is organizing Software Should Work, an independent conference about software reliability, on July 16-17. ParadeDB is not affiliated, although we are proud sponsors.
Speakers include the creators of Zig, SQLite, etc. More info: softwareshould.work/
Is there more to this race than having hot pools?
Vercel Sandboxes are now the fastest sandbox using real VMs as security boundary based on the @computesdk benchmark. The team has been absolutely cooking on this.
And the best thing: Because we have a unified Fluid Compute stack across Sandbox, Builds, and Functions these wins are often shared across the stack.
On the feature side there is a really exciting roadmap ahead as well.
My favorites (all driven by feature requests from our customers):
- Persistent sandboxes (in beta, GA immanent)
- The fully mutable firewall also becomes fully programmable
