FOUNDING BETA

Test ReWeaver on your own code. Shape what it becomes.

Run ReWeaver on the code you ship today. Help us make every drift check more useful in the real world.

Become part of the Founding Beta Team

Spots are limited by design. We onboard in small weekly groups so every tester gets real attention from the team.

WHAT HAPPENS WHEN YOU SIGN UP

Three steps. One real workflow. That's the whole ask.

We are onboarding new testers weekly. Signing up later doesn't mean missing out; it means joining a community that's already improving the product.

The founding cohort onboards the week of July 17, and we keep onboarding new testers weekly after that. Signing up later doesn’t mean missing out; it means joining a community that’s already improving the product.

Get set up

Accept the GitHub invite and install ReWeaver.
Takes less than 15 minutes to get up and running.

Run one real workflow

Point ReWeaver at some of our sample code or a repository you actually work in and complete one workflow. No days of testing. One is enough.

Tell us what happened

Bugs, friction, confusion, ideas. We care about all of it, and it goes straight to the people building the product.

HOW YOUR FEEDBACK SHAPES REWEAVER

You report it. We build it. You see it named.

A founding beta only works if testers can watch their input turn into shipped product.
Here's the loop you're joining.

A founding beta only works if testers can watch their input turn into shipped product. Here’s the loop you’re joining.

A direct line, not a ticket queue

The founder and the engineering team field each bug, question, and piece of feedback, in Discord and in weekly office hours.

Weekly triage, visible shipping

Every report is triaged with engineering each week. Nothing disappears into a black hole, and improvements land frequently.

You asked. We built.

The weekly changelog names the changes that came directly from tester feedback, so your fingerprints are on the record.

BEFORE YOU ASK

The questions every evaluator has.

Short answers here; longer ones in Discord, from the people who built it.

Which stacks does the beta support?

React-first today: .tsx, .jsx, .ts, and .js files, plus HTML/CSS. Additional framework coverage arrives as the beta matures.

Which operating systems?

Mac today. Windows is available in beta, with some rough edges while it matures.

Do I need to bring API tokens?

No. ReWeaver runs its own detection engine, so there's no per-call cost to you, and it works alongside any AI coding tool.

How is this different from a linter?

A linter checks whether your code follows code rules. ReWeaver checks whether your design and your code still agree with each other, in both directions. And detection is deterministic: same inputs, same findings, no AI model in the detection loop.

What happens to my code?

It stays on your machine. Detection runs locally — ReWeaver reads your repository on your own device, and your source code is never sent to us. We don't train models on it. The only traffic that leaves your machine is traffic you initiate: GitHub and Figma, with your own credentials, connecting directly from your device - not our servers.

What does the beta cost?

Nothing. Founding beta testers get the full engine free during the beta, and a direct line to the team building it.

One workflow. Your honest feedback. That's the contribution.

Help define how AI-generated code gets verified, before the rest of the industry catches up.