Free forever. Hosted when you want it.

Documentation drift is the gap that opens between what a page says and what the code does, because the code kept changing and the page didn't. It's ordinary and unavoidable; the problem is that it's invisible. A page that went wrong in March looks exactly like one confirmed correct last week. Wiki Pilot makes the gap measurable by having each page declare the paths it covers and the commit it was last verified at — so "which pages did this refactor invalidate?" becomes a git diff rather than a memory exercise.

Docusaurus, GitBook, Notion-as-docs — they all render nicely, and then nobody touches the content again. Wiki Pilot's difference is unglamorous: it records which source files a page came from and which commit it was verified at. Change those files without updating the page and the page says so, rather than sitting there looking finished.

Yes. Running wikipilot init asks which kind of wiki you want — technical, user guide, or both — and drafts sections to match. A user guide gets Getting Started, Guides, FAQ, and Troubleshooting; a technical wiki gets Onboarding, How It Works, Technologies, Reference, and Cookbook. Pass --preset technical, --preset user-guide, or --preset all to skip the question.

That's what the onboarding section is for — the page a new teammate reads before their first commit: how to get the project running, how the repo is laid out, where to start editing. The technical and default presets both include it. Without an API key you get a stub with the detectable parts filled in; the deep-investigation pass writes the full version.

No. Drafting, building, and serving a wiki run entirely on your machine. An API key unlocks two optional extras. The first is a deep-investigation pass during init, where an AI agent reads your code and rewrites the draft from what it finds — Claude by default, or OpenAI, Gemini, and other OpenAI-compatible endpoints via --provider. The second is the ask-the-wiki assistant on the built site, which is Claude-only and wants ANTHROPIC_API_KEY specifically.

Not unless you switch on one of the two optional AI features. wikipilot init, build, and serve read your repository and write files locally — there is no Wiki Pilot account, server, or telemetry involved at any point. If you do run the deep-investigation pass, the files the agent chooses to read go to whichever provider you picked, under your own key: Anthropic by default, OpenAI or Gemini if you chose them with --provider, or whatever endpoint you named with --provider custom. The ask-the-wiki assistant works the same way — it runs as a process you start yourself and talks only to Anthropic. Skip both and nothing leaves the machine.

A mid-size repository lands in the low single-digit dollars on the default model, claude-sonnet-5, billed to your own Anthropic key. Other providers bill their own keys at their own rates. The run is bounded no matter how large the repo is — at most 150 model turns and a fixed read budget of 2 MB of file content — and the conversation is prompt-cached, so re-reading history each turn costs about a tenth of the normal input rate. When it finishes it prints the token count and an estimated cost, so you're not guessing after the fact. Passing --model claude-haiku-4-5-20251001 runs at roughly a quarter of the price.

wikipilot build outputs plain static HTML, CSS, and JavaScript into a directory. Host that on GitHub Pages, Cloudflare Pages, S3, or any web server — there is no backend to run. The optional AI assistant is the one part that needs a server, and you point the built site at it with --agent-url.

Yes. Wiki Pilot reads the repository's file structure, README, and package manifest rather than parsing one language's syntax, so it isn't tied to a particular stack.

It's built for it. The wiki-type prompt only appears on an interactive terminal — a piped or non-TTY run takes the default preset instead of hanging — and --yes or --preset makes the choice explicit in a script. The usual pipeline is to commit the wiki/ folder like any other source, run wikipilot build on push, and publish the output directory. The deep-investigation pass is opt-in there too: it runs in CI only when you pass --ai with the chosen provider's key already in the environment, because it won't prompt for a key it can't ask for.

Yes, MIT licensed, and it stays that way. The source is on GitHub and the package is published on npm. Only the hosted Pro and Team tiers are a paid product.

wikipilot init also writes a Claude Code skill into your repo. Asking Claude Code to update the wiki makes it diff each page's declared sources since that page's last verified commit, re-read the files that changed, and rewrite the affected prose. Pages it can't confidently update are marked as needing review instead of being rewritten on a guess.