The open-source DeepWiki alternative.
A free public wiki like DeepWiki's, plus a deterministic layer it cannot ship: a defect-validated code-health score, dead code, git risk, and a README badge that keeps the whole index refreshing itself. Open source and self-hostable, including on your private repos, without a Devin account.
DeepWiki proved that an auto-generated wiki is a great way to understand a public repo. The question is what happens when the code is yours, private, and you need more than a read-only wiki.
repowise generates the same kind of wiki, diagrams, and Q&A, then makes it open, self-hostable on your private code without a Devin account, and just one layer of a wider deterministic stack that also scores health, finds dead code, reads git history, captures decisions, and keeps itself current with a README badge.
A badge that keeps the wiki honest, and itself fresh.
DeepWiki's growth loop runs on a README badge that buys weekly auto-refresh. repowise ships the same mechanic, plus a second badge DeepWiki has no equivalent for, and it is live on our own README today.
A distribution badge, and an honest health badge
Add the repowise badge to a README and that repo's index starts refreshing weekly on its own, no cron job or webhook to wire up yourself. A second, fully opt-in badge shows the average code-health score, or a trend variant that is safe to display even at a mediocre absolute number, since the direction health is moving is often the more interesting fact.
- Distribution badge: links back to the repo page, unlocks automatic weekly refresh
- Health badge: opt-in, average code health or an 'improving' trend variant
- Both render as a single public, cached SVG, nothing to install beyond the markdown
- Byte-for-byte the same badge GitHub renders, previewed live below
Add a badge to your README
Both badges are public, cached, and update on their own after every index. Nothing to install.
Repowise badge
Links to this page. Adding it also re-indexes the repo every week.
[](https://repowise.dev/repo/repowise-dev/repowise)Code health badge
Average health across every file, straight from the latest index.
[](https://repowise.dev/repo/repowise-dev/repowise)Which one is right for you?
Choose repowise if
- You want an auto-generated wiki for your private repos without logging into a vendor's agent
- You want open source and self-hostable, with every layer and heuristic inspectable
- You want the wiki plus code health, dead code, git intelligence, decisions, and agent provenance in one tool
- You want an agent-neutral MCP context layer for Claude Code, Cursor, Cline, and Codex
- You want the wiki rebuilt incrementally on every commit on infrastructure you control
Choose DeepWiki if
- You just want to glance at a popular public repo with a zero-friction github.com to deepwiki.com URL swap
- You rely on the 50,000+ pre-indexed public repos already available instantly
- You are already invested in Cognition's Devin agent ecosystem
- You want a fully managed, polished public experience with nothing to host
repowise vs DeepWiki
| Capability | repowise | DeepWiki |
|---|---|---|
| Auto-generated wiki and documentation | Included | Included |
| Architecture diagrams | Included | Included |
| Codebase Q&A / chat | Included | Included |
| MCP server for AI agents | Included | Included |
| README badge that triggers automatic refreshrepowise: two badges, a vanity distribution badge plus an optional health score/trend badge | Included | Included |
| Instant URL-swap view of any public repoDeepWiki: swap github.com for deepwiki.com | Not included | Included |
| Large library of pre-indexed public reposDeepWiki: 50,000+ top public repos pre-indexed | Partial support | Included |
| Open source and self-hostable | Included | Not included |
| Private repos without a paid agent accountDeepWiki private repos require a Devin account | Included | Not included |
| Defect-validated code-health score | Included | Not included |
| Dead code detection (unreachable files, unused exports) | Included | Not included |
| Git intelligence (hotspots, ownership, bus factor) | Included | Not included |
| Architectural decision records | Included | Not included |
| AI code provenance (agent attribution) | Included | Not included |
| Agent-neutral context (Claude Code, Cursor, Cline, Codex)DeepWiki's MCP feeds Cognition's agent ecosystem | Included | Partial support |
Self-assessed against publicly documented features as of July 2026. A dash means partial or limited support. Vendor capabilities change, so please verify against DeepWiki's current docs before deciding.
Our own repo, public and free.
Every claim on this page is checkable on a real, live index: repowise's own OSS repository, indexed by repowise itself and open to anyone.
The same kind of auto-generated wiki and Q&A DeepWiki popularized, indexed on this exact repo and free to browse.
Every file scored 1 to 10 across defect, maintainability, and performance, deterministic and free.
Unreachable files and unused exports, tiered by confidence, with no equivalent on DeepWiki.
The deterministic layer you see on those three pages, code health, dead code, git intelligence, and decisions, is free on every repo you index, public or private, self-hosted or hosted, with zero LLM spend. This repo's wiki additionally has prose, so you can see what the narrative layer looks like once you choose to add it, on your own self-hosted run or ours.
A wiki is the start, not the whole story.
The same auto-generated wiki, diagrams, and Q&A DeepWiki popularized, plus the layers a read-only public wiki was never built to provide.
Wiki, health, dead code, git, decisions, and agent context together
DeepWiki is a wiki and Q&A product. repowise puts the wiki alongside a defect-validated code-health score, dead-code detection, git intelligence, architectural decision archaeology, agent provenance, and ten MCP tools, so the same index serves understanding, quality, and your AI agents.
- Code health for every file, validated at ROC AUC 0.74, 95% CI 0.68 to 0.79, up to 0.90 per repo
- Dead code: unreachable files, unused exports, zombie packages, tiered by confidence
- Git intelligence: hotspots, ownership, bus factor, hidden coupling
- Architectural decisions mined from 8 sources
Self-host the wiki without a vendor's agent
DeepWiki needs a paid Devin account to wiki a private repo. repowise is open source under AGPL-3.0: one pip install, point it at any private repo, and your source never leaves your environment. Bring your own LLM key or run fully offline.
- Run on your own infrastructure, no Devin account needed
- Zero telemetry, code never leaves your environment
- Bring your own LLM key or go fully offline with a local model
- AGPL-3.0: inspect, fork, self-host the whole platform
Context for any agent, rebuilt on every commit
repowise is not fuel for one vendor's agent. Its ten MCP tools give Claude Code, Cursor, Cline, and Codex a real model of your code, and the wiki is rebuilt incrementally on every commit so the context never goes stale.
- MCP tools for Claude Code, Cursor, Cline, and Codex
- Wiki rebuilt incrementally on every commit, typically under 30 seconds
- get_overview, get_answer, get_context, get_risk, get_why, and more
- Multi-repo workspaces for cross-service understanding
A score you can reproduce, not just a prompt.
DeepWiki's wiki, like any LLM-generated narrative, can read differently on a re-run. The code-health, dead-code, and git-intelligence layers underneath repowise's wiki never do.
No API key for the first index
pip install repowise, then repowise init --yes --no-prose builds the graph, git history, and full code-health score with zero LLM calls and nothing to configure.
Same score, every run
21 markers score every file the same way each time. No temperature, no prompt drift, no different answer on a re-run of an unchanged file.
No lock-in on the model
Bring your own LLM key for prose, or skip prose entirely and keep the wiki's supporting layers, health, dead code, git intelligence, and decisions, fully deterministic.
Validated against real bugs
Cross-project ROC AUC 0.74 (95% CI 0.68 to 0.79, up to 0.90 per repo) against real defect labels, not a similarity score between a prompt and a diff.
Switching over takes four steps.
There is no export to run and no data to migrate out of DeepWiki: you point repowise at the same git remote and it builds its own index from scratch, deterministic layer first.
Install
pip install repowise. No Docker required, no account, no indexing queue you do not control.
Index for free
repowise init --yes --no-prose builds the graph, git history, and full code-health score with no API key and no spend.
Add prose if you want it
Bring an LLM key, or run local via Ollama, and re-run with --prose to add the same kind of wiki narrative DeepWiki gives you, now on your private repos too.
Add the badge
Paste the README badge snippet once and weekly refresh, plus an optional live health score, keep the wiki current without you touching it again.
Two different answers to who controls this.
A wiki tool is infrastructure. Before it touches a private repo, the license and the deployment model matter as much as the feature list.
Source availability
repowise's core is open source under AGPL-3.0 (OSS 0.35.0): every marker, every scoring rule, every heuristic is public and inspectable. DeepWiki is closed-source SaaS from Cognition; nothing beneath the product surface is published.
Where your code runs
repowise runs on your own infrastructure, your VPC, your laptop, or a container you control, and can operate fully offline with a local model. DeepWiki processes your repo on Cognition's servers; there is no self-hosted deployment option.
Forkability
AGPL-3.0 means you can inspect, modify, and keep running repowise indefinitely on your own terms, independent of any roadmap decision repowise itself makes. A closed product carries no such guarantee if the vendor changes course.
Cost model
Self-hosting repowise is free indefinitely; hosted and enterprise tiers are optional convenience, not a requirement. DeepWiki is free only for public repos; any private repo requires a paid Devin account, whether or not you use Devin itself.
The honest version
DeepWiki is a genuinely excellent product, and there are places it leads. It is backed by Cognition, the team behind Devin, and that brand and distribution matter. Its zero-friction experience is hard to beat: swap github.com for deepwiki.com and you are instantly reading a wiki for almost any public repo, with more than 50,000 of the top public projects already pre-indexed. The free public experience is polished and there is nothing to host. If you mainly want to glance at popular open-source projects, or you are already invested in Cognition's agent ecosystem, DeepWiki is a strong choice.
The trade sits on top of self-hosting and licensing too, covered above in full: repowise wins when the code is your own and private, when you want openness and self-hosting, and when you want code health, dead code, git intelligence, decisions, and agent-neutral context on top of the wiki.
What repowise costs.
The repowise core is open source under AGPL-3.0 and free to self-host, with every heuristic public. Hosted tiers: Free for public repos, Pro at $15 per month, Teams at $60 per month, and custom enterprise licensing when you need it. DeepWiki's pricing changes, so verify it on their site, then compare it with a tier you can read line by line.
Questions, answered
Is repowise a good DeepWiki alternative?
Yes, if you want an auto-generated wiki with architecture diagrams and codebase Q&A like DeepWiki, but open source, self-hostable, and able to run on your private repos without logging into a vendor's agent. repowise generates the wiki and then adds a deterministic layer DeepWiki does not have: a defect-validated code-health score, dead-code detection, git intelligence, architectural decisions, agent provenance, and a README badge. DeepWiki remains the easiest way to glance at a popular public repo, since you just swap github.com for deepwiki.com.
Can I use repowise on private repos without a Devin account?
Yes. With DeepWiki, private repositories require a paid Devin account. repowise is self-hostable under AGPL-3.0, so you run it on your own infrastructure with one pip install, point it at any private repo, and your source never leaves your environment. You can bring your own LLM key or run fully offline with a local model.
Is repowise open source and self-hostable? DeepWiki is not.
Yes. The repowise core is open source under AGPL-3.0, so every layer, marker, and scoring rule is public and inspectable, and you can self-host the whole platform. DeepWiki is a closed hosted product from Cognition, the makers of Devin, and is not self-hostable.
Does repowise have code health and git intelligence that DeepWiki lacks?
Yes. DeepWiki focuses on the wiki, diagrams, and Q&A. repowise adds a code-health score for every file from 21 deterministic markers, validated against real defects (cross-project ROC AUC 0.74, 95% CI 0.68 to 0.79, up to 0.90 per repo), plus dead-code detection, git intelligence (hotspots, ownership, bus factor, hidden coupling), architectural decision records mined from 8 sources, and agent provenance that tracks how much of your code AI wrote and whether it is healthy.
Does repowise have a badge like DeepWiki's refresh loop?
Yes. repowise ships two README badges. A vanity distribution badge links back to the repo page and, once it is added, keeps that repo's index refreshing on a weekly cadence automatically, the same mechanic DeepWiki's badge uses. A second, fully opt-in health badge shows average code health, or a trend variant that is safe to display even on a mediocre absolute score. Both are a single cached SVG: nothing to install beyond pasting the markdown.
Does repowise work with my AI coding agent?
Yes, and it is agent-neutral. repowise exposes its whole index through ten MCP tools (get_overview, get_answer, get_context, get_risk, get_why, and more) for Claude Code, Cursor, Cline, and Codex. DeepWiki also ships an official remote MCP server, but it feeds Cognition's agent ecosystem rather than being a neutral context layer you self-host for any agent.
Is repowise free?
Yes. repowise is free and open source under AGPL-3.0 to self-host, including code health, dead-code detection, git intelligence, decisions, agent provenance, the ten MCP tools, multi-repo workspaces, and the local dashboard, on public or private repos, with zero LLM spend required for any of it. Prose narrative is a separate, optional pass, on either the self-hosted tool or the hosted product. DeepWiki is free for public repos, but private repos require a paid Devin account. repowise also offers paid hosted and enterprise tiers when you want zero-ops hosting.
Can I see repowise's own code health and dead code before installing anything?
Yes. repowise's own OSS repository is indexed publicly, with its wiki, code-health breakdown, and dead-code report all live and free to browse, generated by the same engine that would score your repo. It is linked below so you can check every claim on this page against a real index instead of a screenshot.
What actually costs money in repowise, if the deterministic layer is free?
Self-hosting repowise costs nothing: code health, dead-code detection, git intelligence, decisions, and the MCP tools all run with zero LLM spend, on any repo, public or private. What costs money is the LLM prose pass that writes the wiki's narrative, since that calls a model, and the paid hosted and enterprise tiers that trade your own infrastructure for a zero-ops deployment. DeepWiki's equivalent gate is simpler and blunter: public repos are free, any private repo needs a paid Devin account, regardless of which repowise features you would actually use.
How is repowise different from DeepWiki?
DeepWiki gives you a polished, zero-friction wiki for public repos via a URL swap, backed by 50,000+ pre-indexed projects, and a badge that keeps that index refreshing. repowise gives you the same auto wiki plus a defect-validated code-health score, dead-code detection, git intelligence, architectural decisions, agent provenance, and its own two-badge refresh loop, all open source and self-hostable on your private code, and rebuilt incrementally on every commit. DeepWiki is documentation; repowise is a full deterministic intelligence layer for your own codebase.
Generated docs, diagrams, and Q&A, fresh on every commit.
The defect-validated score, in depth.
Hotspots, ownership, coupling, bus factor.
21 markers, the ROC AUC methodology, and how to read a worklist.
How the ten MCP tools cut agent context tokens by up to 96%.
Where repowise's zero-LLM dead-code detector ranks.
The other code-health-first comparison, against a commercial tool.