STATIC ANALYSIS. REAL DOCUMENTATION.
Code in. Clarity out.
Analyze source code locally to generate architecture documentation, route and model maps, and Markdown ER diagrams. Explain files or ask codebase questions from the same CLI.
npx @autodocify/autodocs analyze .npx @autodocify/autodocs explain .npx @autodocify/autodocs ask "How does auth work?"STATIC ANALYSIS. REAL DOCUMENTATION.
Docify reads your code, understands the structure, and generates documentation your team will actually use.
npx @autodocify/autodocs analyze .From your project root, run the analyzer. Read the generated docs in your project.
Documentation that evolves with your code.SIMPLE · FAST · FOR BUILDERS
CODEBASE DOCUMENTATION / LOCAL CLI
Docify is an open-source codebase documentation generator for developers working with existing projects. Run its CLI from your project root to inspect source declarations, routes, models, services, dependencies, and project manifests. It writes Markdown architecture documentation, a project overview, and an ER diagram for supported data models, ready to review and commit alongside your code.
Use analyze to generate documentation, explain to summarize a directory or file, or ask to find source evidence for a specific question. The analysis runs locally without executing your application or uploading its source. JavaScript and TypeScript have deeper syntax and call analysis. Coverage varies by language and framework. Treat the output as a starting point to check against your source, rather than a verified runtime trace.
YOUR CODEBASE, IN CONTEXT
Need to find how a feature works? Ask Docify from your terminal. It searches local source, docs, and configuration, then gives an evidence-based answer with file references and a verdict about what the source can establish.
No API key or hosted model. The command runs locally, does not upload your code, and does not write files. Its findings are static evidence, not a verified runtime trace.
Ask directly from your project root. Use --path when the project is in another local directory.
npx @autodocify/autodocs ask "How does auth work?"npx @autodocify/autodocs ask "How does auth work?" --path ../your-projectPrints an answer, source references, and a verdict in your terminal.
HOW TO USE DOCIFY
Docify requires Node.js 20+. Check your installed version with node --version.
From your project root, run npx @autodocify/autodocs analyze ..
Find docs/architecture.md, docs/er-diagram.md and docs/overview.md in your project.
A SECOND WAY TO UNDERSTAND YOUR CODE
Get a source-grounded summary in your terminal without generating or changing any files. Explain a directory to see detected routes, models, services, integrations, authentication, persistence, and inferred application layers. Explain a file to see its purpose, imports, importers, table references, and recognized SDK calls.
JavaScript and TypeScript include deeper import and call analysis. Layer order is inferred from declarations and dependencies, not a verified runtime trace.
Read the source file explanation guide →npx @autodocify/autodocs explain src/services/payment.tsPayment Service Detected in the scanned source: • 3 API endpoints • 1 database model • 2 services • 0 external integrations Application layers (inferred): Client ↓ Express routes ↓ Services ↓ Sequelize models
Prints to the terminal. Does not write files.
Source evidence, not assumptions.
From detected data models.
Ready to review and commit.
Keep docs in sync.
FROM MESSY CODEBASES TO CLEAR DOCUMENTATION
BEFORE
▣ my-project/
▣ src/
▣ controllers/
▣ services/
▣ models/
▣ routes/
▣ package.json
▣ README.mdAFTER (WITH DOCIFY)
▣ docs/
▣ overview.md ✓
▣ architecture.md ✓
▣ er-diagram.md ✓SIMPLE
FAST
FOR BUILDERS
HELP SHAPE DOCIFY
Tell us what would make the analyze, ask, or explain commands and generated docs more useful. Ideas for other Docify improvements are welcome too.
PRACTICAL DOCIFY GUIDES
Generate a Markdown overview, architecture documentation and an ER diagram from an existing project, then review the results against your source.
Read the guide →CODEBASE ANALYSISMap a project's declared routes, models, services and dependencies with Docify before reading individual source files.
Read the guide →CODEBASE QUESTIONSUse Docify ask to find local source evidence, answer a focused codebase question, and follow file references without a hosted model or API key.
Read the guide →SOURCE CODE EXPLANATIONInspect a file's purpose, imports, local importers and detected storage or SDK references with Docify explain.
Read the guide →DATA MODEL DOCUMENTATIONGenerate a Mermaid entity-relationship diagram from supported schema declarations with Docify, then verify fields and relationships against your models.
Read the guide →MORE WAYS TO BUILD / FREE FOR EVERYONE
Create a document, celebrate an achievement, or make your images lighter. No signup required.
Start with HTML or a certificate template. Preview, personalize, and save as PDF.
Open document studio →02 / IMAGESChoose your dimensions and quality. Download PNG, JPEG, or WebP, directly in your browser.
Open image workbench →03 / IMAGE TO PDFConvert a PNG, JPEG, or WebP image into a downloadable one-page PDF.
Open image to PDF →