v3.2 STABLE · in-site AI chat

Turn any codebase into docs your team will actually read.

Generate complete documentation from your repository — with an AI assistant that answers using your actual source code.

View on GitHub

Python 3.10+ · MIT license · Any LLM provider

deepdoc.local/docs/contextly-platform-overview
Generated DeepDoc documentation site for the Contextly platform, showing structured navigation and source-grounded content Generated DeepDoc documentation site for the Contextly platform, showing structured navigation and source-grounded content
DeepDoc Chatbot
You
Where does billing verification happen?
DeepDoc
Payment verification is handled in the Razorpay billing flow, then persisted through the usage and project records.
billing/routes.py:41-88services/usage.py:12-57
Works with Python TypeScript JavaScript Go PHP Vue OpenAPI
See it in action

Watch the pipeline run.

43 sec · all five phases
What it does

One command. A docs site
your team won't ignore.

01

Your docs stay organized

Architecture, endpoints, integrations, and schemas — grouped the way readers actually look for them, not one noisy page per file.

auth.py, middleware.ts → Auth & Permissions
billing/routes.py, usage.py → Billing & Usage
api/webhooks.ts, stripe.py → Integrations
db/models.py, migrations/*.sql → Data & Schema
02

AI answers cite real files

Ask your docs anything. Every answer points to exact file paths and line ranges from your actual source — not hallucinations. Follow-ups keep the whole thread in-page.

Where does billing verification happen?
Payment verification runs in the Razorpay billing flow, persisted through usage records.
↗ billing/routes.py:41-88
↗ services/usage.py:12-57
How does the widget token flow work?
The widget fetches a short-lived token from /api/widget-token, then attaches it to every chat request.
↗ api/widget.ts:18-64
fast lookup deep research code-first
03

Updates regenerate only what changed

Push a commit, run deepdoc update, and only the affected pages regenerate. Your docs keep up without a full rebuild.

deepdoc update — 3 files changed
billing/routes.py regenerate
services/stripe.py regenerate
db/models.py skip
Pipeline

Five phases. No magic.

Every page is grounded in scanned evidence, repaired into valid Markdown, and checked for source coverage before the site builds.

Scan
Plan
Generate
API Ref
Build
Select a phase to explore
Getting started

Three commands.

Initialize against any Python, JavaScript/TypeScript, Go, PHP, or Vue codebase. Set one API key. Generate. The chatbot inherits the same key and runs fully on your machine.

Read the full docs
bash
# 1 — install $ pip install deepdoc # 2 — initialize against your repo $ deepdoc init --with-chatbot --provider anthropic $ export ANTHROPIC_API_KEY=sk-ant-... # 3 — generate and preview $ deepdoc generate ✓ 47 pages generated in 1m 12s ✓ Chatbot index built (1,247 chunks) $ deepdoc serve Docs → http://localhost:3000 Chat → http://localhost:3000/ask

Your codebase already tells a story. Let it.

MIT licensed. No account. No cloud. Runs entirely in your terminal.