Software v2026-05-04.2

Self-Hosted DeepWiki Alternatives Guide

OSS and self-hostable ways to replace Devin's DeepWiki with generated repo docs, MCP, code search, Q&A, and agent context.

The closest single OSS/self-hosted replacement for Devin DeepWiki is OpenDeepWiki. For AI coding agents, the best default stack is Sourcebot plus Serena; the strict OSS version is Kodit plus Serena plus Repomix, with OpenDeepWiki added when agents need durable architecture docs.

Candidates checked 18 Wiki generators, MCP engines, code search tools, RAG platforms, and execution agents.
Top OSS single tool OpenDeepWiki 82/100 fit score in this source-based rubric.
Strongest search/Q&A layer Sourcebot Fair-source, not OSI OSS, but the best lightweight shared code-intelligence product.
Strict OSS stack OpenDeepWiki + Kodit + Serena Generated wiki, MCP/REST code search, and local symbolic agent tools.
Best agent stack Sourcebot + Serena Shared MCP search/Q&A plus local LSP-backed symbol retrieval and editing.

Answer

OpenDeepWiki is the closest OSS single-tool replacement.

It combines generated repository documentation, Mermaid diagrams, multi-code-host ingest, local/ZIP support, user management, database options, and a built-in MCP endpoint.

Better stack

Use a layered stack when you want more than DeepWiki.

Pair OpenDeepWiki or Kodit for generated docs with Sourcebot for shared search/Q&A/MCP and Serena or Narsil for local agent-grade code intelligence.

Agent audience

Coding agents need tools, not just pages.

For Claude, Codex, Pi, Cursor, or a custom MCP client, prioritize file reads, symbol lookup, references, grep, call graphs, and small cited context over a polished human wiki.

Catch

The hard part is not generation; it is coverage, permissions, and retrieval quality.

Generated pages can look complete while skipping subsystems. Enterprise usefulness depends on ACLs, refreshes, source citations, and MCP tools that agents actually use.

Bottom line

There is no perfect clone; there is a clear best stack.

The closest OSS/self-hosted replacement for Devin's DeepWiki is OpenDeepWiki. If the job is a private repo wiki with diagrams and MCP, start there. If the job is broader codebase intelligence, the stronger answer is a stack: OpenDeepWiki or Kodit for generated docs, Sourcebot for shared search/navigation/Q&A/MCP, and Serena or Narsil for local agent code intelligence.

Baseline

What Devin DeepWiki is actually doing

CapabilityDevin / DeepWiki baselineReplacement implication
Repository indexingIndexing enables Ask Devin and DeepWiki and is separate from Devin's dev-environment setup.A replacement needs a durable repo index, not just one prompt with repo text.
Generated wikiDeepWiki produces architecture diagrams, docs, source links, and codebase summaries.A plain semantic-search MCP server is not enough.
Q&AAsk Devin uses DeepWiki plus advanced code search for cited answers.The search/Q&A layer and generated docs layer can be separate tools.
Public repo MCPPublic DeepWiki MCP exposes read_wiki_structure, read_wiki_contents, and ask_question for public repos.A self-hosted private-repo replacement should expose MCP, not only a web UI.
Steering.devin/wiki.json can steer docs with notes and explicit page plans.The best replacements need explicit page planning or repeatable prompt/config control.
LimitsStandard DeepWiki steering supports 30 explicit pages; enterprise supports 80.Large repos need intentional page selection and coverage validation.

Shortlist

Best candidates by fit score

RankToolFit scoreUse it forWhy it ranks hereMain catch
1OpenDeepWiki82 / 100Self-hosted DeepWiki-like generated wiki plus MCPBest single-package clone shape: generated docs, diagrams, multi-code-host ingest, local/ZIP support, database options, user management, and MCP.Smaller ecosystem than deepwiki-open; .NET/Semantic Kernel stack; quality still depends on LLM prompts/models.
2Sourcebot80 / 100Shared code search, Ask-style Q&A, code navigation, MCP contextBest lightweight product for ask/search every repo with citations and agent MCP access.Fair-source, not OSI OSS; no durable generated wiki; permission syncing and OAuth MCP are Enterprise-gated.
3Kodit78 / 100OSS MCP/REST code and document intelligence serverApache-2.0, no-key startup, built-in embeddings, SQLite default, BM25 + semantic + grep + visual document search, wiki/enrichment MCP tools.Young project with lower adoption; generated docs require LLM enrichment configuration.
4SourceBridge76 / 100Ambitious field-guide/context layer pilotConceptually closest to better-than-DeepWiki: field guides, code tours, diagrams, requirements traceability, MCP, GraphQL, CLI, VS Code.Very young by public repo signals; treat as a pilot, not the default platform.
5deepwiki-open70 / 100Popular OSS DeepWiki-style web appStrong adoption, private repo token support, diagrams, RAG Ask, DeepResearch, local Ollama support.No obvious MCP in the README; less useful as an agent context service unless wrapped.
6CodeWiki68 / 100Static repo documentation generationResearch-backed structured docs with Mermaid architecture/data-flow/dependency/sequence diagrams and GitHub Pages output.More CLI/static-docs than always-on shared code intelligence.
7Serena64 / 100Local MCP navigation and editingExcellent agent-side symbol retrieval/editing through LSP across 40+ languages.Not a wiki generator or shared web knowledge base.
8Narsil MCP62 / 100Local MCP code intelligence and security context90 tools, 32 languages, call graphs, taint analysis, SBOM, license checks, optional neural search.Young; high tool count needs careful client/tool budgeting; not reader-facing wiki output.

Matrix

Feature comparison

ToolLicense postureSelf-hostGenerated wiki/docsDiagramsMCPSearch/Q&ACode nav/graphPrivate repo story
OpenDeepWikiMITYesStrongMermaidBuilt inChat/Q&ABasic graph/code analysisGit hosts, ZIP/local upload
deepwiki-openMITYesStrongMermaidNot obviousRAG Ask, DeepResearchLightGitHub/GitLab token support
CodeWikiMIT in READMELocal/self-hostStrong static docsMermaid plus visual artifactsDocs linkedNot primaryArchitecture-aware docsLocal repo
SourceBridgeAGPL-3.0YesStrongMermaidBuilt inCode discussionTree-sitter graph/impactAny local/server repo
SourcebotFair-source / FSLYesNoNoBuilt inStrong Ask with citationsStrong search/navEnterprise permission sync
KoditApache-2.0YesOptional enrichmentOptional enrichmentBuilt inStrong search, enrichment toolsSearch/snippet layerAny Git URL with PAT/SSH
Sourcegraph EnterpriseCommercial self-hostYes, EnterpriseNoNoBuilt inStrong Deep Search/CodyStrongest mature nav/permissionsEnterprise permission sync
Onyx CE/EEMIT CE, EE add-onsYesNot code-wiki-specificNoBuilt inStrong workplace RAGNo real code navigationGitHub connector focuses PRs/issues; permission sync EE/Cloud
SerenaMITLocalNoNoBuilt inRetrieval/memoryStrong LSP symbolic editingLocal checkout
Narsil MCPApache-2.0LocalNoGraph/security reportsBuilt inHybrid/neural searchCall graphs/security/SBOMLocal repos, optional remote

Agent audience

Best choices when the reader is Claude, Codex, Pi, or another coding agent

If the consumer is an AI agent planning or writing code, the ranking changes. Human-readable architecture pages help orientation, but an agent usually needs narrow, current, source-linked retrieval: file reads, grep, symbol definitions, references, call graphs, dependency context, and compact Markdown or MCP tool output it can cite in a plan.

Agent jobBest pickWhy it helps an agentDo not use as the only layer
Claude/Codex/Cursor-style local coding loopSerenaLSP-backed symbol retrieval, references, memories, and editing tools map directly to how an agent plans and changes code in a checkout.Generated wiki pages; they are too coarse for safe edits.
Shared multi-repo agent questionsSourcebotMCP tools for grep, file reads, tree/glob, commits, symbol definitions/references, model listing, and ask_codebase give agents live cited context across repositories.A static wiki; it will drift and may miss the exact file path.
Strict OSS shared agent contextKodit + Serena + RepomixKodit supplies permissive MCP/REST search and enrichment, Serena supplies local symbolic operations, and Repomix gives portable snapshots when the agent cannot call the live index.Sourcebot if OSI licensing is mandatory.
Planning before a larger changeSourcebot or Kodit + OpenDeepWikiUse search/Q&A for current files and citations, then use generated wiki/docs for architecture hypotheses and subsystem maps.OpenDeepWiki alone; planning needs exact file evidence.
Security, dependency, or impact analysisNarsil MCP, then SerenaNarsil adds call graphs, taint analysis, SBOM, license, and dependency context; Serena can then inspect and edit the relevant symbols.Plain semantic search; it misses graph and supply-chain structure.
Agent-readable onboarding for a new repoOpenDeepWiki or CodeWiki + Sourcebot/KoditGenerated docs are useful as a first-pass map, but the agent still needs live search and file access to verify every plan.deepwiki-open unless wrapped with MCP or another file/symbol tool.

Layers

What each layer does

LayerBest toolsWhat it contributesWhat it does not solve
Generated wikiOpenDeepWiki, deepwiki-open, CodeWiki, SourceBridgeHuman-readable pages, diagrams, architecture overviews, onboarding docs.Precise code navigation and live agent context by itself.
Shared code search/Q&ASourcebot, Sourcegraph, KoditMulti-repo search, citations, file reads, branch/ref awareness, MCP/API access.Durable wiki pages unless enrichment is configured.
Agent-side code intelligenceSerena, Narsil, CodeGraphContext, BlarifySymbol definitions/references, call graphs, impact analysis, local editing, security context.Shared reader-facing product surface.
General knowledge RAGOnyxGitHub PRs/issues plus docs, tickets, Slack, Drive, Confluence-style knowledge and MCP.Real source-code navigation or generated repo wiki.
Execution agentOpenHandsDevin-like task execution foundation and self-hosted agent runtime.Standing codebase wiki/search layer.

Repo health

GitHub signals as of May 4, 2026

ToolRepoStarsForksLatest observed pushPublic signal
deepwiki-openAsyncFuncAI/deepwiki-open16,0821,7962026-04-21Very high adoption for wiki clone, but MCP gap.
OpenDeepWikiAIDotNet/OpenDeepWiki3,1474122026-04-11Smaller but more complete single-tool feature shape.
CodeWikiFSoft-AI4Code/CodeWiki9281482026-04-04Research-backed and focused on docs generation.
SourceBridgesourcebridge-ai/sourcebridge1012026-05-04Very young despite strong concept fit.
Sourcebotsourcebot-dev/sourcebot3,3192642026-05-02Productized and current, but fair-source.
Kodithelixml/kodit118152026-05-01Early but technically well-shaped.
Serenaoraios/serena23,8091,5962026-05-04Strong local MCP adoption signal.
Narsil MCPpostrv/narsil-mcp144192026-02-25Powerful but still early.
CodeGraphContextCodeGraphContext/CodeGraphContext3,1425632026-05-03Popular graph-first MCP option, still young.
Repomixyamadashy/repomix24,3221,2052026-05-04Excellent packing/snapshot utility, not a wiki.
OpenHandsOpenHands/OpenHands72,6039,1802026-05-04Best OSS execution-agent signal, not a standing code index.

Picks

Best picks by job

JobPickReason
Replace DeepWiki pages for private reposOpenDeepWikiBuilt-in wiki generation, diagrams, MCP, and self-hosting.
Ask questions across all company reposSourcebotBest lightweight self-hosted Ask/search/navigation product with MCP.
Stay strictly OSS and avoid fair-sourceOpenDeepWiki + KoditCovers generated docs plus MCP/REST code search with permissive licenses.
Give Claude/Codex/Cursor better local repo toolsSerenaLSP-backed symbol retrieval and editing is more precise than wiki text.
Give Claude, Codex, Pi, or a custom MCP client shared repo contextSourcebot + SerenaSourcebot handles shared search/Q&A/file/symbol context; Serena handles local symbol-aware edits.
Keep the agent stack strictly OSSKodit + Serena + RepomixPermissive search/enrichment, local LSP operations, and portable context packing without a fair-source shared search layer.
Add security and supply-chain intelligence to agent contextNarsil MCPTaint analysis, SBOM, license, dependency, and call-graph tools.
Generate static architecture docs for a repoCodeWikiStrong static-doc and visual artifact generator.
Build an internal codebase field guide productSourceBridge pilotMost aligned product vocabulary and feature ambition; maturity risk is the reason to pilot.
Enterprise search with serious ACLsSourcegraph EnterpriseMature permissions and code-intelligence controls, but commercial.
Broader company knowledge, not just codeOnyxGood RAG/MCP layer for docs and work systems; pair it with a code tool.

Caveats

Where these tools can mislead you

  • Self-hosted does not mean no external model calls. Many tools need OpenAI, Anthropic, Gemini, Voyage, OpenRouter, or another provider unless configured with Ollama/local embeddings.
  • MCP support varies a lot. Some tools expose search and file reads; others expose generated wiki pages, graph traversal, or agentic Q&A.
  • For agent audiences, generated wiki quality matters less than tool granularity. A coding agent will usually make better plans with exact file reads, references, call graphs, and snippets than with polished prose.
  • GitHub star counts are adoption signals, not correctness. Kodit and SourceBridge are low-star but strategically interesting; deepwiki-open is popular but lacks obvious MCP.
  • Generated wikis need coverage testing. Large repos can produce attractive but incomplete pages unless you steer page structure and verify missing subsystems.
  • Permission sync is the hidden enterprise boundary. Sourcebot and Sourcegraph have the clearest stories; many OSS tools have no real multi-user ACL model.
  • Onyx is better treated as a companion workplace knowledge layer than a codebase wiki replacement because its GitHub connector docs emphasize PRs and issues rather than source-code navigation.

Receipts

Claim table

WhereClaimConfidenceSourceCaveat
BaselineDevin's repository indexing enables Ask Devin and DeepWiki and is separate from environment setup.HighDevin DocsDevin docs can change quickly.
BaselineDeepWiki generates codebase wikis with architecture diagrams, source links, and summaries; Ask Devin uses DeepWiki plus code search.HighDevin DocsProduct quality is not independently benchmarked here.
BaselineDeepWiki MCP exposes public-repo wiki structure, wiki contents, and Q&A tools, while private repo use points to Devin.HighDevin DocsPublic DeepWiki MCP is not a private self-hosted option.
ShortlistOpenDeepWiki is the closest single OSS/self-hosted DeepWiki replacement because it combines generated docs, diagrams, repo ingest, and MCP.HighAIDotNetMaturity and generated-doc quality need a live pilot.
Shortlistdeepwiki-open has strong wiki generation and adoption but no obvious MCP support in its README.MediumAsyncFuncAIMCP may exist outside the README or be added later.
ShortlistKodit exposes MCP/REST, BM25, semantic search, grep, visual document search, and optional wiki/enrichment tools.HighHelixMLAdoption is still early.
ShortlistSourcebot is the best lightweight shared search/Q&A/MCP layer, but core licensing is fair-source and permission syncing is Enterprise-gated.HighSourcebotFair-source may be acceptable for self-hosting but is not OSI OSS.
Decision matrixSourcebot MCP includes grep, list/read file tools, tree/glob, commits, symbol definitions/references, model listing, and ask_codebase.HighSourcebotOAuth and permission behavior depend on license and instance configuration.
ArchitecturesSourcegraph Enterprise has the strongest mature MCP/code-intelligence and permission story, but is commercial.HighSourcegraphPublic Sourcegraph repo metrics are not representative because the main repo is no longer public in the same way.
LayersSerena is best treated as local agent code intelligence, not a generated wiki.HighOraiosSome deeper refactors require the paid JetBrains backend.
LayersNarsil MCP provides local code-intelligence/security tools across 32 languages, including call graphs, taint analysis, SBOM, and optional neural search.HighpostrvYoung project and high tool count may require MCP tool filtering.
Agent audienceFor Claude, Codex, Pi, Cursor, or a custom MCP coding agent, Sourcebot plus Serena is the best default stack when fair-source licensing is acceptable.MediumSourcebotThis is a fit judgment from the available MCP/search and local-symbol tool surfaces, not a benchmark.
Agent audienceKodit plus Serena plus Repomix is the best strict-OSS agent-context stack among the surveyed tools.MediumHelixMLRepomix packing helps snapshot-based planning, but live edits still need file/symbol tools.
Agent audienceGenerated wiki pages are useful agent background but should not be the only layer for agents that will plan or edit code.HighOraiosA high-quality wiki can still help orientation when paired with exact code retrieval.
CaveatsOnyx is strong for workplace RAG/MCP but not a source-code navigation replacement.HighOnyxOnyx can still ingest code-like documents through other paths.

Sources

How this was built

PublisherSourceTypeAccessed
Devin DocsIndex a RepositoryOfficial2026-05-04
Devin DocsDeepWikiOfficial2026-05-04
Devin DocsAsk DevinOfficial2026-05-04
Devin DocsDeepWiki MCPOfficial2026-05-04
AIDotNetOpenDeepWikiOfficial2026-05-04
AsyncFuncAIdeepwiki-openOfficial2026-05-04
FSoft-AI4CodeCodeWikiOfficial2026-05-04
SourceBridge.aiSourceBridgeOfficial2026-05-04
SourcebotSourcebot OverviewOfficial2026-05-04
SourcebotSourcebot MCP ServerOfficial2026-05-04
SourcebotSourcebot Permission SyncingOfficial2026-05-04
HelixMLKodit READMEOfficial2026-05-04
SourcegraphSourcegraph MCP ServerOfficial2026-05-04
SourcegraphSourcegraph Repository PermissionsOfficial2026-05-04
OraiosSerenaOfficial2026-05-04
postrvNarsil MCPOfficial2026-05-04
CodeGraphContextCodeGraphContextOfficial2026-05-04
blarAppBlarifyOfficial2026-05-04
yamadashyRepomixOfficial2026-05-04
OnyxOnyx GitHub ConnectorOfficial2026-05-04
OnyxOnyx MCP ServerOfficial2026-05-04
OpenHandsOpenHandsOfficial2026-05-04