Our mission
Drift is the mistakes that pile up in code that still looks like it works, and AI produces it faster than any team can catch. We make it visible, put a number on it, and keep a person deciding every fix.
What drift costs
Once for the tokens. Then again in the engineer-hours it takes to make that output safe to ship. That second cost is the one no one tracks. Call it cost-per-usable-token: what the code actually costs once you add the work to trust it. The token is nearly free now. That work is not.
On our drift scale, cleaning up AI-generated code runs 45 minutes to 2.5 hours per file. AI-generated security flaws run three times as often as the human kind, and cost twenty-two times as much to fix. That's the bill. It hides inside headcount and velocity until someone measures it.
What we believe
Humans decide what software should be. Machines can speed up the building. But someone has to keep what ships true to what was intended, and more review after the fact is exactly what's failing, because no one reads code as fast as a model writes it.
So control moves up front. Humans set the rules and the tolerances, and the tooling holds the machine to them. Prevention, not correction.
What we do
Measure drift. Keep a person deciding every fix.
ReWeaver is built where the work happens, for the humans who make the product.
For the people building it
The tools keep your AI-generated code true to the design it came from, and keep you the author of what ships. That's the foundation.
For the leaders who answer for it
DriftDetector reads the whole codebase against the rules it's meant to follow and puts a cost on the gap. Same drift, two altitudes: the mismatch one person catches, and the bill across the whole team.
Every fix is deterministic: an exact match to the intended state, or nothing. Logged in git. Decided by a person. Nothing ships because a model feels confident.
Who we're for
And the leaders who answer for what they ship. The person at the keyboard, and the person who signs for the spend.
Why I started it
I kept watching good tools frustrate the people using them.
Jonathan Gordon
CEO / Founder
I'm Jonathan Gordon. Close to forty years in this field, from typing green text into a terminal to leading design at the companies whose tools everyone now uses. I moved from writing software to designing it because I wanted to be upstream of that frustration.
Human-centered design is the throughline: decide what a thing should be, then hold the technology to that decision instead of letting it decide for you. ReWeaver is that discipline pointed at the machine that now writes the code.
The team
Who's building it.
Platform
Runs on Mac today. Windows support is in beta, with some rough edges while it matures.
See what it's costing you.
Point ReWeaver at your codebase and we'll surface real drift, and its cost, in the first session. Whether you design it, build it, or answer for it.
Join the Beta