Not backed by YC

Documentation that keeps pace with your codebase.

Turn your repository into a navigable docs site, then keep it accurate as code changes—with answers tied back to the source.

Python 3.10+ · MIT license · Bring your own LLM · View on GitHub

https://cloud.deepdoc.tech/pranav322/codewiki
Generated DeepDoc documentation site for the codewiki repository, showing domain-grouped sidebar navigation, an architecture diagram, and the built-in chatbot bar. Generated DeepDoc documentation site for the codewiki repository, showing domain-grouped sidebar navigation, an architecture diagram, and the built-in chatbot bar.
Reader-first docsorganized by domain
Source-backed answersfiles and line ranges
Focused updatesonly changed pages regenerate
Works with Python TypeScript JavaScript Go PHP Vue OpenAPI
See it in action

Watch the pipeline run.

41 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.tsAuth & Permissions
billing/routes.py, usage.pyBilling & Usage
api/webhooks.ts, stripe.pyIntegrations
db/models.py, migrations/*.sqlData & 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.

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 lookupdeep researchcode-first
03

Updates regenerate only what changed

Push a commit, run deepdoc update, and only the affected pages regenerate.

deepdoc update — 3 files changed
billing/routes.pyregenerate
services/stripe.pyregenerate
db/models.pyskip
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
Hover a phase to explore
Getting started

Run it in your repo.

From your repository root, initialize DeepDoc with your preferred provider. It writes .deepdoc.yaml, then generates and serves your docs locally.

Read the full docs
bash
# 1 — install $ pip install deepdoc # 2 — configure a provider (creates .deepdoc.yaml) $ deepdoc init --provider anthropic $ export ANTHROPIC_API_KEY=sk-ant-... # 3 — generate, then preview (Node.js 18+) $ deepdoc generate 47 pages generated in 1m 12s $ deepdoc serve Docs → http://localhost:3000

Your codebase already tells a story. Let it.

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