What Repave is
Repave modernizes a legacy system by first agreeing, in writing, what it does — and only then implementing that behaviour against a modern stack.
The behaviour is written as Gherkin: plain-language scenarios that describe what the system does from the outside. Scenarios extracted from the legacy codebase are the as-is specification, the record of what you have today. Scenarios you edit or add are the to-be specification, the record of what you want. Agents implement against the to-be specification and the same scenarios verify the result, so nothing ships that the specification does not describe.
The two kinds of project
Web application modernization takes a legacy web application — its screens, its rules, its database access — and produces a modern application feature by feature. You review the extracted scenarios, adjust them where the legacy behaviour is not the behaviour you want to keep, and implement each feature against the target stack.
Batch job conversion takes scheduled or triggered jobs that read and write a legacy database and produces equivalents against a modern target, with the same emphasis on an agreed description of what each job does before anything is rewritten.
What you will do, in order
- Upload the legacy codebase. Repave analyses it and builds a picture of its structure, its data access and its user journeys.
- Review the as-is specification. The extracted scenarios are the system as it behaves today, linked back to the code they came from.
- Decide the to-be specification. Keep, change or drop each behaviour. This is the decision the rest of the work depends on, and it is a human one.
- Implement feature by feature. Agents write the code for a feature against the to-be scenarios, in a workspace you can open and edit yourself.
- Verify. The scenarios are executed against the running application, in a browser, and the result is a report you can read rather than a claim.
Where to go next
- Install with Docker Compose — run Repave on your own host.
- GCP Marketplace — the packaged virtual machine.
- Features — what the product does, surface by surface.
- Methodology — why the work is shaped this way.