Question 1

How is this different from Mintlify or GitBook?

Accepted Answer

Mintlify and GitBook are great editors, but you still write the docs yourself, and their AI features just summarize prose. doc0 parses your code into a symbol graph (functions, call chains, API endpoints), generates docs from that structure, and exposes both wiki and MCP from the same source. AI tools query the graph directly, not paraphrased prose. No manual writing, no MDX files, no CI pipeline to maintain.

Question 2

How is this different from DeepWiki?

Accepted Answer

DeepWiki generates a one-time snapshot. doc0 keeps the docs current: your docs update when you push, your edits survive regeneration, and the same repo gives you both technical docs and user guides. Plus private repos, team collaboration, custom domains, and an MCP server your AI tools query directly. In our published benchmark, blind judges scored doc0 ahead of DeepWiki on every one of 10 repos tested. Methodology and raw scores are public.

Question 3

How does doc0 work with Claude Code, Cursor, Slack, and Linear?

Accepted Answer

Your AI tools stop guessing about your codebase. Every doc0 project ships with an MCP (Model Context Protocol) server, scoped by a project key. Add it to Claude Code or Cursor with one line of config. MCP queries return grounded answers with source citations to the underlying code files. Beyond search, agents get structural tools raw file access can't offer: impact analysis, path tracing between symbols, detection of open PRs likely to collide, and who-knows expertise mapping. The Slack bot and Linear agent answer from the same index and are available on the Team plan: install the doc0 app in Linear and mention it on any issue, or ask the Slack bot from any channel.

Question 4

How do I make my agent actually use doc0?

Accepted Answer

Installing an MCP server doesn't mean an agent uses it. Left alone, agents drift back to searching raw files. Run npx doc0 setup in your repo: it detects Claude Code, Cursor, or Codex and installs three things per agent: the MCP server entry, an always-on rule that points the agent at your docs first, and a skill with triggers tuned to your project. npx doc0 remove undoes exactly that. Public projects need no account or API key; private projects use your dashboard API key.

Question 5

Can non-engineers (product managers, support, customer success) use this?

Accepted Answer

Yes. doc0 generates two documentation modes from the same code: a technical wiki for engineers and a user-guide wiki written for non-engineers. Both are searchable with AI chat on every plan. On the Team plan, that same context reaches non-engineers where they already work: product managers query the Linear agent when scoping tickets, and support and customer success ask the Slack bot. No MDX, no markdown skills required. The interface is built for reading, not authoring.

Question 6

Does it work with private repositories?

Accepted Answer

Yes. doc0 connects via GitHub App. Your repository is cloned, analyzed in memory, and deleted after processing. We don't keep a copy. To power search and chat we store indexed chunks of your code (encrypted at rest, deleted with your project) plus file hashes for change detection, and your code is never used for training. Private repositories are available on Pro, Team, and Enterprise.

Question 7

Why not just run it locally?

Accepted Answer

Local code-graph tools re-index on every machine and only help the one engineer running them. doc0 is hosted (no per-machine indexing), always-fresh (it auto-updates as you push), and team-shared (one graph powers Slack, Linear, and every AI tool your team uses). On top of the graph, you also get a human-readable wiki, something a local indexer doesn't produce.

Question 8

What happens to my edits when docs regenerate?

Accepted Answer

Your manual edits are preserved. doc0 tracks provenance: which source files generated which pages. When you push code, only pages whose source files changed are regenerated. Edited pages are flagged but never overwritten.

Question 9

What languages and frameworks are supported?

Accepted Answer

doc0 works with any GitHub repository regardless of language. It parses 14 grammars with tree-sitter (JavaScript, TypeScript, TSX, Python, Java, C, C++, C#, Go, Rust, Kotlin, PHP, Ruby, and Swift) and falls back to file-structure analysis for the rest. It detects endpoints in Express, NestJS, FastAPI, Django, Spring Boot, Rails, and 10+ more frameworks.

Question 10

How does the AI chat work?

Accepted Answer

The chat retrieves the most relevant snippets from your docs and source code, then asks an LLM to compose a grounded answer with citations. Under the hood: hybrid vector + full-text search, query expansion to catch synonyms, and reranking to filter noise. You don't need to think about any of that. Every answer cites the files and symbols it's based on, so you can verify.

Question 11

How is the knowledge graph used?

Accepted Answer

doc0 doesn't just summarize files. It maps your entire codebase into a symbol graph with call relationships, community detection, and cross-module execution flows. This powers 'How It Works' pages that trace real code paths, enriches AI chat with structural context, and surfaces authorship and change frequency for every file.

Question 12

How much does it cost?

Accepted Answer

Pro and Team start with a 3-day trial. Pro (€30/mo) covers 500,000 lines of code a month, unlimited public projects, 5 private repos, custom domains, and export. Team (€250/mo) adds unlimited team members, 20 private projects, deep research, plus the Slack bot & Linear agent. Enterprise is priced per organization. Book a call. All plans run on EU-resident infrastructure.

Question 13

Why not just give Claude Code or Cursor my repo directly?

Accepted Answer

Honestly: on a small, well-organized repo, a bare agent does fine. doc0 earns its keep when the repo outgrows a context window, and the moment anyone besides that one engineer, human or agent, needs the same answers. Agents reading raw files re-derive your codebase's structure from scratch every session, burning tokens and inventing function names when context runs out. doc0 builds the structure once (symbols, call graphs, execution flows) and serves it to every tool over MCP. The same index also answers your PM in Linear and your support team in Slack. Raw repo access can't do that.

Question 14

Does doc0 stop my agent from writing duplicate code?

Accepted Answer

It makes duplicates findable before they're written. Agents query the knowledge graph over MCP and get the existing implementation with its callers, so "write a new helper" becomes "use the one that exists." doc0 doesn't gate your agent's writes (no tool truthfully claims to), but an agent that sees the codebase's structure stops recreating it.

Question 15

Where does my code get processed?

Accepted Answer

Projects generate in the EU. Your repository is cloned, analyzed in memory, and deleted after processing. We keep file hashes, the indexed chunks that power search and chat, and their embeddings, never a copy of your repository. Your code is never used for training. Search relevance ranking uses a third-party processor; our full sub-processor list is in the privacy policy.

Question 16

How do you measure documentation quality?

Accepted Answer

We publish our benchmark: blind LLM judges score doc0-generated wikis against DeepWiki and Google CodeWiki on 10 real repositories. Methodology, corpus, and raw scores are public in the benchmarks repository.

Ask your codebase anything. From anywhere.

Your team, your users, and their AI agents get grounded answers, cited to the code. You choose who sees what. Updated as you push.

One repo in. Complete knowledge out.

Don’t trust generated docs? We don’t either.

Editable, and edits survive

Changelog, generated and delivered

API reference, detected

Two docs from one repo

Judge it on code you already know

next.js

supabase

shadcn/ui

fumadocs

hono

drizzle

Your team asks doc0. Not you.

Your PM asks Linear

Support asks Slack

The new hire reads the wiki

Connect once. Your docs stay current as you push.

Connect

Connect

Connect your repo

Generate

Generate

doc0 parses and generates

Query

Query

From every tool your team uses

Your agents read it natively. Your auditors read the logs.

MCP Server

llms.txt + Copy as Markdown

EU data residency

No repository copies

SOC 2 & ISO 27001

Audit logs & access controls

EU data residency, on every plan

Generation runs in the EU

Embeddings run in the EU on every plan

We don't keep a copy of your repository

Your code is never used to train models

Start with a 3-day trial

Pro

Team

Enterprise

Frequently Asked Questions