See Archify in action
https://github.com/user-attachments/assets/78570807-ba1d-4737-953f-55504a378a87
One sentence. Your repo, mapped. Watch the 35-second demo: explore the diagram, follow source links, and trace a path. Try the interactive examples ↗
Install, then describe your idea
Works with Cursor, Claude Code, Codex CLI, and OpenCode. See installation options below for additional integrations.
Install Archify for me by reading https://raw.githubusercontent.com/tt-a1i/archify/main/llms.txt
Send this to your agent:
Use Archify to diagram a web request: Browser calls the API,
the API checks Redis, and a cache miss queries PostgreSQL and fills the cache.
Then continue: “Add authentication”, “Highlight the cache-miss path”, or “Switch to the light theme”.
No repository is required: start with a description, or ask your agent to read a repository for a source-backed architecture diagram.
Choose your agent · Installation details and update checks · Create and check diagrams with your agent
Ask a question, get a one-page answer
Not every answer is one diagram. Ask your agent to answer as a page and Archify builds an explainer: the conclusion first, then one panel per question, with tables, steps, charts, code and validated diagrams.
- Conclusion first. The answer and its reasons lead; every panel takes one question.
- Diagrams that explain. Steps sit beside the diagram they walk through and light its parts as you read. Click any node to open the full interactive view.
- Easy to check. Claims cite numbered sources; repository excerpts are pinned to a commit and open in a source card.
- Easy to share. One HTML file with four styles and light or dark themes. Export a PNG, WebP or JPG long image, or print to PDF. Ask about any panel to get a follow-up your agent can use to revise just that panel.
Use Archify to answer as one page: our API's P99 went from 80 ms to 600 ms
while the mean barely moved. What is the likely cause, and how should we investigate?
Live examples: First HTTPS visit · P99 latency (Chinese) · How Archify finalize keeps the last good file, read from this repository (Chinese) · First rental checklist (Chinese)
❤️ Sponsors
Archify × Kimi Work. Find Archify in the Kimi Work plugin store as Interactive Architecture Diagram. Describe your system in one sentence to create an interactive diagram. Try it in Kimi Work →
Want to sponsor Archify? Contact us by email.
Show what matters
| Explain an agent workflow | Follow a cache miss | Explore service relationships |
|---|
| | |
| Trace everything downstream of one step. | Highlight the path from web app to database. | Focus on authored backend and database connections. |
The Proof Lab contains all 11 checked-in scenarios, their JSON sources, and validation receipts.
Understand a real repository
CODE → DIAGRAM · A source-backed system map
Archify traced mco-org/mco at 9f1a1cf and produced this checked map. Open it ↗ · trace reach ↗ · typed source
Easy to extend. More ways to make it yours.
COMMUNITY STORIES · Selected examples shared by users
Keep building after the diagram is generated. Archify is open source and its output is standalone HTML. Ask your agent to adapt it, connect useful links, or add interactions for your own workflow. Community creations already span team collaboration, travel planning, legal citation checks, contract review, and incident retrospectives. These are just a few examples.
One user started with a hand-drawn multi-agent architecture, turned it into an interactive diagram, then added a Kimi execution pool through conversation. Others asked their agent to read a project and brought the resulting architecture into Feishu or DingTalk for team discussion.
Another user turned a Shanghai CityWalk guide into a four-day itinerary: switch between days, inspect a stop, and jump to Amap, Xiaohongshu, or Dianping. The author also added arrival check-ins and stop notes, turning the itinerary into a small tool to use during the trip. These extensions were added by the community author for this particular artifact.
▶ Explore the interactive Shanghai CityWalk
This is the beginning of the README. Read the rest at the original. Read the full README ↗
