repowise vs Google Code Wiki: Public Repos, Private Code and What Each Does

Pick Google Code Wiki to read a public GitHub repository for free with nothing to install; pick repowise when the code is private or you want git history, code health and agent tools next to the docs. Google launched Code Wiki in public preview on November 13, 2025. repowise is an open-source engine that builds the wiki from your code graph on your own machine.

Google details are as of October 2026, from its launch announcement. repowise details are from release 0.56.

repowise vs Google Code Wiki at a glance

Code Wiki is a hosted reader for public repositories; repowise is a self-hostable index whose wiki is one of several views.

What Google Code Wiki does well

Code Wiki removes all setup for public code. You open a repository on the site and read.

• Documentation that regenerates. In Google's words, it "scans the full codebase and regenerates the documentation after each change."
• Linked to the code. Each section links to the files, classes and functions it describes.
• Diagrams. Architecture, class and sequence diagrams are generated from the code and stay current with it.
• Chat. A Gemini-powered assistant answers questions using the current wiki as context.

For learning an open source library, that is hard to beat on effort.

Where does your code go?

Code Wiki covers public repositories on Google's servers. For internal code, Google said it is building a Gemini CLI extension "so teams can run the same system locally and securely on internal repositories," and opened a waitlist. Check Google's page for current availability before planning around it.

repowise runs the whole pipeline on your machine or in your CI. With a local model through Ollama, or with --no-prose, no code leaves your network. Because it is AGPL-3.0, you can read how it works and host it yourself.

What repowise adds

repowise turns the repository into an index, then reads that one index in several ways.

A wiki with no model required

repowise renders a page per source file, selected public symbol, subsystem, dependency cycle, infrastructure file and API surface, almost all from code structure. A repository indexed without a key gets a complete wiki. See the wiki feature and auto-generated docs for FastAPI.

repowise wiki page showing the repository overview, docs tree and related files for the repowise repository

Git history

Git intelligence mines ownership, bus factor, churn, hotspots and co-change, so you see which files keep breaking and who knows them. The FastAPI code health view shows it on a real repository.

repowise change coupling view of files that change together with call_resolver.py in the repowise repository

MCP tools for agents

repowise serves ten MCP tools from the local index to Claude Code, Cursor, Cline and other agents. get_answer answers how and why questions with citations, get_risk and get_change_risk score a file or a diff before merge, get_health reports code health, and get_why returns the recorded decisions behind a design.

Which one to pick

Pick Google Code Wiki if the repository is public and you want to read it, with diagrams and chat, in minutes and for free.

Pick repowise if the code is private, must stay on your infrastructure, or you want ownership, hotspots, code health and agent tools alongside the docs.

Use both if you read open source dependencies on Code Wiki and run repowise on your own repositories.

Try it on your own repo

pip install repowise
repowise init --no-prose   # free, no API key
repowise serve             # browse at localhost:3000
repowise mcp               # connect an agent

Then open a public repository on codewiki.google and compare. More tools are in the comparison hub, and the DeepWiki comparison covers the other hosted option.