Blog

Why the plan lives in your repo, not in a database we run

RevampKey writes its diagrams, specs and module trackers into your project folder instead of a hosted dashboard — here's the reasoning.

The easy version of a planning feature stores the plan in a database somewhere and shows it to you in a web dashboard. We didn't build that version, on purpose.

The plan has to outlive the session

A flow diagram or a spec is only useful if it's still there — and still readable — six weeks after the run that produced it, when someone opens a pull request and asks why a decision was made. A record in a vendor's database answers that question only as long as you keep paying for it and keep the tab open. A file in your repository answers it for as long as the repository exists, with git blame doing the rest.

It has to survive RevampKey being closed

Specs, trackers and flow diagrams are written to .revampkey/plans/ in your project. They are plain JSON and Markdown. You can read them, diff them, and review them in a pull request with RevampKey not running at all.

Credentials follow the same rule

The same reasoning applies to the tools RevampKey connects to over MCP — GitHub, Sentry, a database. Tokens for those live in your operating system's keychain, not in a server we operate. A connection is scoped to the tool calls it needs, and nothing you work on is stored in the cloud or used for training.

None of this is a constraint we work around. It's the starting assumption: the plan is your project's, not ours to hold onto.