Alkahest statically analyzes a React/Next project and reverse-engineers a screen-level product map — every screen, how they navigate, and the data each one calls. Share it as a link; anyone on the team reads it in the browser, no install required.
Why Alkahest
New teammates, PMs, and designers shouldn't have to read the router to learn how the product is wired. Alkahest derives that picture from the source — and keeps it current.
Parses your React/Next source directly. No instrumentation, no running the app, nothing to wire into CI. Point it at a repo and scan.
Every screen as a node, navigation as edges, and the API/data calls each screen makes — so flows and dependencies are visible at a glance.
Publish the map to a hosted viewer and send a URL. Teammates explore the graph in the browser — no install, no checkout, always the latest scan.
Drive it from the terminal, or expose it to your AI agent over MCP so it can read the product map while it codes.
The CLI and the graph renderer are open source (MIT). The hosted service adds accounts, sharing, and team plans on top.
Because the map is derived from code, a re-scan reflects reality. Re-publish and the link updates — no stale diagrams to maintain by hand.
How it works
Run alkahest scan at the root of a React/Next app. Alkahest parses the
source and builds a screen-level map locally — preview it any time with
alkahest view.
Create a publish token on your account page, then
alkahest login --token <token>. The token links the CLI to your account.
alkahest publish uploads the map and returns a shareable URL. Send it to
your team — they open the interactive graph in the browser.
# 1 · install the CLI (from GitHub — not yet on npm) npm install -g github:cr8rcho/alkahest # 2 · map your project (preview locally) alkahest scan alkahest view # 3 · connect your account alkahest login --token <your-token> # 4 · publish a shareable link alkahest publish # → https://alkahest.app/p/your-project
FAQ
A screen-level product map: a graph where each screen of your app is a node, navigation between screens are edges, and the API/data calls a screen makes are attached to it. It's the bird's-eye view of how your product is wired, derived from the code itself.
React and Next.js projects today. Alkahest reads your source statically — it does not run your app, so there's nothing to instrument.
No. The CLI runs locally and alkahest publish uploads the map to the hosted
viewer at alkahest.app. Anyone with the link can explore the graph in their browser —
no install or repo access needed.
No. Only the derived map (screens, navigation, and data-call metadata) is published — not your source files.
Yes — it's open-core. The CLI and the graph renderer are MIT-licensed and on GitHub. The hosted service (accounts, sharing, team plans) is the paid layer on top.
Create a free account, generate a publish token, and ship your first link.