Real product-team discipline, delivered at machine speed.
RevampKey plans the states, the design and the spec before it writes any code, and keeps you in control by revising all three every time you correct it.
Linux too. Free to start.
Ready to revamp payments-service?
Partial refunds on checkout
Click a stage to jump. Hover the frame to pause.
The run above is one task, followed end to end: adding partial refunds to a payments service. Every diagram, spec and commit further down this page comes from that same run.
It draws the states before it writes the code.
Take the task above. The hard part of a refund isn’t the refund. It’s the order that was only half captured, the webhook that arrived twice, the card that expired mid-retry. RevampKey draws those branches first and asks you to correct them before it writes anything.
Nine of the seventeen states are failures. You correct them here, while the flow is still a draft, before any code exists to be undone.
Still being corrected by you. Nothing here constrains the build yet. This is the moment changing your mind is free.
Settled. From here it governs new work, and every later change to it is a numbered revision you can read back.
Every decision it made is a file you can open.
The diagram, the screens, the spec and the module list are written into your project with their own revision history, so “why did we do it this way” still has an answer six weeks later.
Files
payments-serviceThe file list is the run’s own record of what it touched, kept beside the plan that said it would.
Changes
5 commitsOne commit per module, each written when that module’s criteria passed, not one commit at the end.
Modules
5 of 5 doneThe tracker the run worked from: every module, its tasks, and the criteria it had to pass before the next one opened.
Decisions
v3revised twice after you corrected the flowA refund can never exceed the captured amount.
Enforced in the service, not the UI, because the gateway webhook can also initiate one.
A duplicate webhook must be a no-op.
The gateway retries for up to 24 hours; the refund is keyed by its idempotency key, not its arrival.
+ added in v3, after you flagged the retry windowA partially refunded order stays open until it is fully settled or cancelled.
Closing it early loses the remaining balance in reporting.
Ledger writes come before customer notification.
A customer must never be told about money the ledger has no record of.
+ added in v3The spec is the decisions the flow and the screens forced, with the reason each one was made and the revision that added it.
Design
3 artboardslinked to the flow’s statesScreens are drawn as real artboards on the project’s canvas, one per state the flow declared, so the surface and the behaviour cannot drift apart.
Refund lifecycle
v2activeThe diagram above in section two is this file. It is stored in your repository, it has two revisions, and you can read the difference between them.
Every tab here is a file in your project folder. They stay readable with RevampKey closed, and they are what a reviewer opens six weeks later.
A one-line fix stays a one-line fix.
There is no mode to switch on: RevampKey sizes each request itself: a thirty-line change is made and checked with no ceremony, and only work that crosses files and states gets the diagram, the spec and the module breakdown.
One control appears in none of these three panels: a setting for how much planning to do. That is the point.
No forty-file dump at the end.
Each module lands as its own commit against its own acceptance criteria, and RevampKey checks the running result, not the file it just typed, before it opens the next one.
Module 2 is running; module 1 already has its commit. The tests and the three breakpoint checks ran against the built result, not against the file that was just typed.
Asserting that a file you just wrote contains the strings you wrote into it is the code checking its own spelling.
RevampKey’s own verification ruleOn hour four, it still knows what it decided in hour one.
Work goes to specialists: one that reads code, one that writes it, one that draws screens, one that handles version control, and one that drives your connected tools. Each works on a clean desk, reporting back to the lead that keeps the whole picture.
Nothing it learned gets thrown away.
Two hours and forty messages later, the finding from hour one reopens in place.
It searches the grammar, not the text.
Each block is one specialist’s task and the finding it reported back. The lead keeps the findings, not the raw work, which is why hour one is still available in hour four.
A database migration gets the same treatment as a checkout screen.
A schema change, a retry policy, a permission rule, a queue that must drain before deploy. Each gets the same diagram, the same spec, and the same checked commit, across every repository in your workspace.
Only one of these six opens a screen: the refund panel from the run at the top of this page. The diagram, the spec, the modules and the checked commit are the same either way.
The plan lives in your repo, not on our server.
Specs, trackers and diagrams are written into your own project folder, nothing you work on is stored in the cloud or used for training, and tokens for the tools you connect stay in your operating system’s keychain.
Tokens are stored securely in your OS keychain and never leave this machine.
Sign-in runs on Keycloak. Read the privacy policy
Open the repo you’ve been avoiding.
Point RevampKey at the change you keep postponing, and read the plan before you decide whether to let it build.
macOS 12+ · Windows 10+ · Ubuntu 20.04+ · See what shipped in 2.4.0