See any codebase
as a map, not a maze.
You own code you didn't fully write: an app built with AI, a repository you inherited. Hand it over. Thirty seconds later you're reading its real architecture: what starts it, what talks to what, where the data lives, what's dead. Every wire is an import that exists in the code, citable to its exact line.
✓ Nothing you load leaves this browser. There is no server to upload to.
or drag it onto this row. Files are read here, uploaded nowhere.
from an export, or the Claude Code skill
pages & scripts only; real architecture needs source
First time? Try expressjs/express or pallets/flask. Private repos work with a token in Settings.
Read it — what the analyzer computed, nothing invented
Your files arrive already sorted into layers, left to right: the front door, the routes, the working core, where data lives, the outside world. Then the map starts explaining itself.
Short chapters walk you through your own system in plain language: where execution starts, the spine most requests travel, the files everything leans on, what's dead.
Click any wire and it shows you the exact import that created it, file and line, with a link straight to the source. A claim you can check is the only kind here.
Dead code, circular imports, hot files, layering violations: surfaced automatically, each one verifiable on the canvas.
Big repo? Low-traffic files wait in a searchable overflow: listed, expandable, never hidden. The whole codebase is reachable.
Ask it — answers are computed from the graph, never generated
Type a question in the map's top bar. A query engine parses it and answers by computation, so the answer cannot be made up. When there's nothing to find, it says so.
who imports analyze.js
6 files feed analyze.js · 7 imports · 1 hop. Highlighted on the canvas, each one clickable.
circular imports
0. None. That's good. Nothing was invented to fill the gap.
path from main.js to render.js
Route main.js → render.js · 1 hop. The journey, step by step, every step a real import.
Change it — every map is editable; new systems start from a sentence
Drag components, draw wires, edit anything, undo freely. Or describe a product you haven't built: answer a few sharp questions, and get a complete proposed architecture with every assumption stated. Then tell it what to change, in your own words.
Works without any API key. You get a vetted starter blueprint, honestly labeled.
Annex A — Controls
| Hover · click · double-click | spotlight a file's wires · pin it and read details · zoom to it |
| g tour | guided chapters; [ ] to move between them |
| u / d reach | everything that feeds the selected file / everything it reaches, with a receipt: files · imports · hops |
| r route | the shortest real import chain between two files |
| / ask | "who imports app.js" · "dead code" · "biggest files", or just search a file name |
| click a wire | the exact file:line import that created it |
| p trace | one animated pass along the critical path |
| Edit | drag, add, connect, delete, with undo (⌘Z), on any map |
| ? | the full manual, on the map itself |