❯_ RWX raised $12M. Read the founding story and thesis on the blog.
CI Debt Audit

What is waiting on CI
costing your team?

RWX is a CI/CD platform that never re-runs work that has not changed. We will show you what your current setup is costing.

Get your audit

Enter your work email.

No call required. Nothing to install.

Engineering teams already running on RWX

What you get

Your numbers, with the math shown.

Engineer-hours lost to CI, what they cost, and where that lands once agents multiply your build volume. Every assumption on the page.

ci-debt-audit · example
northwind.io
CI Debt Audit
Estimated from public footprint · Sept 2026
1,386
engineer-hours a month waiting on CI
$1.8M
a year at a loaded rate
3x
pipeline runs on an agent cadence
Assumptions
  • ~150 engineers (estimated)
  • 6 pipeline runs per engineer per workday
  • 12 min average pipeline, 50% of it blocking
  • $110/hr fully loaded

Example output

What it reads

Public signals only.
Nothing from inside your build.

Three scans feed the model. Every claim carries its source.

Stack

Your CI provider

Detected from your public web and DNS fingerprint, then labelled as detected, inferred, or assumed. We show you which one it was.

Org size

Engineering headcount

Estimated from live engineering job postings and public company data. The basis line on the audit tells you exactly how the number was reached.

Load

Pipeline volume

Modeled from team size and typical run frequency, then projected forward against an agent-driven cadence.

Where the time goes

Same build.
Better runtime.

Most CI bills pay to redo work that has not changed.

Typical run, every commit
clone48s
install-deps3m 12s
build4m 05s
jest (flake, attempt 2)4m 28s

Every push pays the full cost again.

The same run on RWX
clone2s
install-depsCached
buildCached
jestretry, 22s

Unchanged work is never re-run. The flaky step replays on its own.

Proof

Fall in love with your build platform.

Every number is published, with a named customer behind it.

0%
lower CI/CD costs
Grid
0%
faster CI feedback loops
Honeycomb
0%
shorter CI runtimes, off GitHub Actions
Tropic

RWX is super fast. It executes jobs quickly, caching works incredibly well, and it's all very hands-off. But most importantly, the cost savings have held as our usage has scaled.

Mickey ReissHead of Engineering, Grid

Fast, reliable CI is a necessary part of a well-functioning engineering team, especially with the amount of code being generated today. With RWX, the tools have been there to keep the feedback loop moving.

Dean StrelauStaff Engineer, Honeycomb

Deployments that once took multiple hours, even up to an entire day, and required multiple engineers are now 20-minute, one-person workflows.

Nate VickVP of Platform Engineering, ClickFunnels

RWX was built by engineers for engineers, and it shows in how fast and hands-off CI feels day to day. Our runtimes are down to 10 minutes.

Pedro CoronelPrincipal Engineer, Tropic

Switching to RWX for CI not only enabled us to accelerate feedback loops, it helped our developers regain confidence shipping larger, more ambiguous changes.

Mike McCuneVP of Engineering, Coalesce

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 ThomasSVP of Engineering, Bonusly

Migrating CI is the part nobody wants to do

So most teams do not do it in one move. Tropic ran RWX alongside GitHub Actions until they trusted the results, then cut over. ClickFunnels got their starting config delivered as a single file to commit. If your pipelines are deeply wired into another platform, the honest answer is that the port takes real work, and the parallel run is how you find out whether it is worth it before you commit to anything.

Who built this

Dan Manges has run CI at scale twice before.

Dan Manges, founder and CEO of RWX
RWX is named after the read, write, execute permissions in computer file systems. Dan founded it after two tours as a CTO, where he spent years on the wrong side of a build platform that could not keep up with the team using it.
CTO, Root InsuranceThrough to IPO in 2020
CTO, BraintreeThrough the PayPal acquisition in 2013

He wrote publicly about how hard the CI/CD problem turned out to be, and why RWX shipped later than planned. That is the person on the second call.

Kohsuke Kawaguchi Creator of Jenkins. An investor in RWX.
Next step

Tear the math apart.

Once you have the audit, fifteen minutes with Collin to walk the numbers and tell us which assumptions are wrong. If it holds up, the next conversation is with Dan.