A wiki written from your GitHub repo, for your team and their AI agents to ask. Cited to the code. Updated as you push.
Your code is never used to train models.
symbols · communities · processes
Agents query over MCP. People ask in the tools they already use. Same graph, same citations.
Questions about the code used to land on you. Now your PM, support and your coding agent ask doc0 where they already work, and the answers link back to the code.
Linear
ENG-412 · Retry failed refunds
Maya
@doc0 what happens today when a refund fails?
doc0
The refund is retried three times, an hour apart. After that it waits in the dead-letter queue until someone replays it.Payments › Refunds
The ticket is scoped against how the system works, and nobody pings you.
Slack
#support
Sam
@doc0 do webhooks retry if the customer's server returns a 500?
doc0
Yes. Failed deliveries retry with backoff for 24 hours, then show as failed in the customer's dashboard.Webhooks › Delivery
The customer gets the real answer, and the escalation never reaches your desk.
Claude Code
> add rate limiting to the export route
doc0_symbol_context("rateLimit")
src/middleware/rate-limit.ts:12-48
4 callers · used by /api/search
Reusing rateLimit() from src/middleware.
Your agent can find the helper you already wrote before it writes a second one.
So every page shows its work. Read one the way you would review a pull request, and check it against your code.
Architecture
ExampleAuthentication flow
Every API request passes through validateJWT(), which checks the signature and expiry before the session loads. An expired token answers 401, and the client refreshes it once before signing the user out.
Sources: src/auth/session.ts:31-58, src/auth/refresh.ts:12-40
Rate limits
rateLimit() counts requests per API key in a sliding window and answers 429 with a Retry-After header once a key passes 600 requests a minute.
Sources: src/middleware/rate-limit.ts:12-48
Claims cite the file and lines they came from, so any sentence can be followed back to the code.
The grounding score on every scored page shows the share of cited symbols verified against your source.
Pages must pass quality gates before they ship: lint on every page, grounding wherever cited symbols can be checked.
Edit any page. Push code, pages regenerate, and your edits stay. Version history included.
We ran doc0, DeepWiki and Google CodeWiki on 10 public repos that doc0 was never tuned on. A blind AI judge checked each wiki’s claims against the source. doc0 scored highest on all 10.
| System | Claim support |
|---|---|
| doc0 | 0.856 |
| DeepWiki | 0.588 |
| Google CodeWiki | 0.430 |
Claim support, from 0 to 1: how well each wiki’s claims are backed by the source. Mean over 10 public repos · Methodology and raw scores
No docs to write, and no pipeline to maintain.
Install the GitHub app, then pick a repository, public or private, and the branch to follow.
It parses your code into a graph and writes from it: a technical wiki for engineers, a user guide for everyone else, an API reference when it detects endpoints, and a changelog from your merged PRs.
Read the wiki, chat with it, or ask from Slack, Linear, Claude Code and Cursor. When you push, only the pages your change affects regenerate, and your edits stay.
EU data residency on every plan. We don’t keep a copy of your repository, and your code is never used to train models.
Documentation and knowledge-graph generation run in the EU, and so do the embeddings behind search and chat.
Your repository is cloned, analyzed in memory and deleted. Search and chat run on indexed chunks, encrypted at rest and deleted with your project.
Your code is used for inference only, on every plan.
Keep a project private, publish the technical wiki or the user guide on its own, and give each teammate a role.
Sensitive account and project changes are recorded in an audit log.
Certification is underway for both.
Search relevance ranking uses a US sub-processor on every plan. The full list is in our privacy policy.
Pricing
Every plan includes the technical wiki and the user guide, AI chat, full-text search, and EU data residency. Most docs platforms bill per site and per seat. doc0 doesn't.
billed annually
For individual developers with private repos.
billed annually
For teams where engineering, product, and support all need code context.
Unlimited team members
For organizations with custom allowances, security reviews, and procurement.
Custom allowance
Lines are counted from your own source code. Vendored and generated files never count, and test files are excluded by default.
One graph of your codebase: a cited wiki for your team, MCP for your agents, kept current as you push.