README

Floorplan

See how your app actually fits together.

Claude or Codex reads your codebase and draws an interactive map of it. Every part, file and web request gets a plain-English name, and every connection between them is shown.











Try the live demo · Watch the video · Install · Quick start · Compared · Features · See it in action · How it works · Docs · FAQ




  

▶ Watch the walkthrough: installing Floorplan, then a tour of Brewline, a demo coffee-subscription app built across four repos.
Try the live demo → Explore the Brewline map in your browser, no install needed.

 Why Floorplan?

You built an app, probably with a lot of help from AI, and it works. But ask "what happens when someone checks out?" or "what breaks if I change this?" and the honest answer is no idea.

Floorplan gives you the diagram nobody drew. Ask Claude Code or Codex for a floorplan and a few minutes later you have a map you can explore, ask questions on, and keep up to date as you work.

- For builders: understand the app you made, in your own words, without reading the code.
- For teams: onboard someone in minutes, from the big picture down to the exact file.
- For working with AI: after every change Claude or Codex makes, see exactly which parts it touched and why.

 Floorplan, Archify or Understand Anything?

All three turn code into something you can see, and all three are worth knowing. They answer different questions:

| | Floorplan | Archify | Understand Anything |
|---|---|---|---|
| The question it answers | How does the app I built actually work, and what should I worry about? | How do I show this clearly? | How does this big codebase work, down to the functions? |
| Made for | People who build with AI and don't read the code | Anyone explaining a system, a process or an idea | Developers getting to know a large codebase |
| What you get | A zoomable map of your whole app: parts, files and endpoints, the screens, the requests between frontend and backend (even across repos), and outside services | A polished diagram in one of 10 types (architecture, sequence, ERD…) or a one-page explainer, from a repo or just a description | A knowledge graph of every file, function and class, with layers, a business-domain view and guided tours |
| Only here | Health check (keys in code, open Supabase tables and Firebase rules, fakeable Stripe webhooks, endpoints anyone can use), Recent work (what your AI just changed, and why), blueprints from a PRD | 10 diagram types, image and video exports, diagrams of things that aren't code | Diff impact, a dashboard that adapts to your role, knowledge-base graphs |
| Runs in | Claude Code, Codex | Claude Code, Codex, Cursor, OpenCode and more | Claude Code, Codex, Cursor, Copilot, Gemini CLI and more |

Pick Floorplan to understand and check an app you own. Pick Archify to draw a diagram for a doc, a talk or a decision. Pick Understand Anything to study a large codebase function by function.

They also work together: map your app

Top issues

Latest release

- Endpoints in route tables (54, from @Yahhi): servers without a framework often keep their endpoints in a lookup a dispatcher reads, keyed by method and path, like { "GET /api/orders": listOrders } in JavaScript or a Python dict of handlers behind a cloud function. Floorplan found no endpoints in these apps, so the website's requests weren't linked to the server. Now each key is an endpoint, named after its handler (a function, an inline function that calls one, or a wrapped one like requireAuth(createOrder)). Tables of other things keyed the same way, like access levels or notes, are left al