This is a comparison about one kind of content: documentation of a codebase. Architecture pages, service overviews, onboarding guides, “how does billing actually work.” Confluence does many other jobs well, and this page isn’t arguing you should cancel it.
For code docs specifically, though, Confluence has a structural problem that no amount of discipline fixes: the page and the code it describes live in different systems that know nothing about each other. Someone refactors the payment service; the Confluence page about the payment service doesn’t flinch. Nothing marks it outdated. Nobody is notified. The page keeps its confident tone for years, and new engineers can’t tell it was written four majors ago.
Wiki Pilot moves that documentation into the repository. wikipilot init drafts pages from the code itself, each one recording which source files it documents and which commit it was verified against. When the sources change out from under a page, the built site shows a banner on exactly that page. The docs and the code share a git history, so “what did we believe when we shipped 1.4” is a checkout, not an archaeology project.
The short version
| Wiki Pilot | Confluence | |
|---|---|---|
| Relationship to code | Generated from it, versioned with it | None — separate system |
| Staleness | Detected per page via sources + last_synced |
Invisible |
| Review | Pull requests, same as code | Page edits, separate permissions |
| First draft | Drafted from the repo by the CLI | Blank page |
| Search | Built into the static site | Confluence search |
| Audience | Engineers, in their existing workflow | Whole company |
| Cost | CLI free (MIT); optional hosted tiers | Per seat, per month |
What changes in practice
The first draft exists. The reason most Confluence spaces for engineering are sparse isn’t laziness — it’s that every page starts blank, and describing a codebase from memory is slow. Wiki Pilot’s init reads the repo and drafts the architecture overview, the technology pages, and the onboarding tour before anyone types a word. Editing a mostly-right page is a fraction of the effort of writing one.
Docs get reviewed like code. A change to a Wiki Pilot page is a commit in a PR. The engineer who refactored the module is the natural reviewer of the doc change that goes with it — in the same diff, not in a separate tool they’d have to remember to open.
Staleness has a face. The page banner (“this page may be outdated — its sources changed since the prose was last verified”) converts doc rot from a vague institutional guilt into a visible, per-page work item.
What Confluence keeps
Meeting notes, product specs, HR policies, anything a non-engineer writes or reads — that content has no source files to track and benefits from Confluence’s commenting and permissions. Teams that adopt Wiki Pilot usually keep Confluence for exactly that, and stop pretending it’s where engineers will look up how the code works.
If your Confluence engineering space is a graveyard with three good pages in it, those three pages are the migration plan: move them into the wiki as markdown, let init draft the rest, and let the freshness contract keep all of it honest.