A wiki of your codebase that rebuilds itself.
An LLM-generated wiki per module and file, rebuilt incrementally on every commit so it never rots. Hierarchical generation, freshness scoring, hybrid RAG search, and selectable styles across 15 languages.
Generated documentation is worthless the moment it falls behind the code. Most wiki tools give you a snapshot and let it rot from the day it is built.
A wiki is only trustworthy if it reflects what shipped this morning, not what the repo looked like at indexing time. repowise treats freshness as a first-class signal: every page is scored, decayed against git history, and rebuilt incrementally on every commit, so the docs stay true to the code.
Documentation that reads like a person wrote it, and stays current.
Hierarchical generation, freshness scoring, and hybrid search, all built on the same indexed graph and git history.
From symbols up to the whole repo
The wiki is generated bottom up: symbols compose into file pages, file pages into module pages, and modules into a repo-level overview. Each level has the context of the one below it, so the result reads like documentation a person would write rather than a flat dump of summaries.
- Per-symbol, per-file, per-module, and whole-repo pages
- Architecture, entry points, and module purpose surfaced at the top
- Built on the tree-sitter dependency graph across 15 languages
- Full-tier depth for 9 languages including C#/.NET
Incremental rebuilds that never let the wiki rot
On every commit, only the pages affected by the change regenerate, typically 3 to 10 pages in seconds. Each page carries a freshness and confidence score with git-informed decay, so stale pages age and regenerate automatically instead of quietly drifting out of date.
- Incremental rebuild on every commit, typically 3 to 10 pages
- Per-page freshness and confidence scoring
- Git-informed decay triggers automatic regeneration
- Auto-sync via post-commit hook, file watcher, or webhook
Hybrid RAG search, in the style you choose
Search fuses full-text and vector results via reciprocal rank fusion, biases by PageRank, and expands one hop along the dependency graph to return a cited answer instead of a file dump. And you choose the documentation voice that fits your team.
- Full-text and vector search fused via reciprocal rank fusion
- PageRank bias plus one-hop graph expansion
- Selectable styles: comprehensive, reference, tutorial, caveman
- Queryable in the dashboard and over MCP via get_answer
From index to a wiki that stays fresh.
Index
repowise parses your repo into a graph and reads its git history. With self-hosting, no code leaves your infrastructure.
Generate
Pages are generated hierarchically from symbols up to files, modules, and the whole repo, in the style you choose.
Score
Each page gets a freshness and confidence score with git-informed decay, so the wiki knows when it is going stale.
Rebuild
On every commit, only the affected pages regenerate, typically 3 to 10 pages in seconds. The wiki never rots.
One wiki, everywhere you work.
In your AI agent
get_answer and search_codebase return cited wiki answers over MCP, not raw file dumps.
In the dashboard
Browse the generated docs per module and file, with architecture and entry points up front.
On every commit
Auto-sync regenerates the 3 to 10 affected pages in seconds, so the wiki tracks HEAD.
Across 15 languages
Full-tier generation depth for 9 languages, with C, Ruby, Swift, Scala, and PHP at good tier.
In your own style
Comprehensive, reference, tutorial, or caveman, without re-indexing the codebase.
On private repos
Self-hosted under AGPL-3.0, so the wiki for a private repo never leaves your infrastructure.
DeepWiki and Google Code Wiki generate a snapshot wiki. repowise adds code health, git risk, and decision archaeology, keeps it fresh on every commit, and lets you self-host it for private repos today, with no waitlist and no logging into a competitor's agent.
Questions, answered
Does the wiki go stale?
No. The wiki is rebuilt incrementally on every commit. Only the pages affected by a change regenerate, typically 3 to 10 pages, in seconds. Every page also carries a freshness and confidence score with git-informed decay, so when the code underneath a page changes the page ages and regenerates automatically instead of quietly drifting out of date.
Which languages are supported?
15 languages in total, with full-tier depth for 9 of them: Python, TypeScript, JavaScript, Java, Kotlin, Go, Rust, C++, and C#. Full tier means AST parsing, import and call resolution, heritage extraction, docstrings, framework-aware edges, and code-health biomarkers. C, Ruby, Swift, Scala, and PHP are good tier, with more config and markup formats parsed beyond that.
Can I choose the writing style?
Yes. Wiki styles let you pick the documentation voice: comprehensive, reference, tutorial, or caveman. The same indexed graph and git history feed every style, so you can switch the tone of the generated pages without re-indexing the codebase.
How does search work?
Search over the wiki is hybrid RAG. Full-text and vector results are fused via reciprocal rank fusion, biased by PageRank so central code ranks higher, then expanded one hop along the dependency graph to pull in directly related pages. The result is a cited answer rather than a raw file dump, available in the dashboard and over MCP through get_answer and search_codebase.
Can I self-host it for private repos?
Yes, today. repowise is open source under AGPL-3.0 and runs fully self-hosted with pip install repowise, so the wiki for a private repo never leaves your infrastructure. You bring your own API key for generation, or run fully offline with a local embedding model. There is no waitlist and no logging into a competitor's agent to read your own docs.
How is it different from DeepWiki or Google Code Wiki?
DeepWiki and Google Code Wiki generate a snapshot wiki. repowise generates the wiki hierarchically from symbols up to files, modules, and the whole repo, then adds the four other intelligence layers around it: code health proven to predict real bugs, git risk and ownership, and architectural decision archaeology. It keeps the wiki fresh on every commit, and you can self-host it for private repos today.