StackMap
Subscribe

arkon vs llm_wiki

Self-hosted enterprise knowledge hub + MCP server: an LLM pipeline compiles SOPs and docs into a traceable, human-reviewed wiki, then serves it to AI clients scoped by department and role. — versus — Desktop app implementing Karpathy's LLM Wiki pattern: an LLM ingests your documents into a persistent, interlinked wiki with a knowledge graph, hybrid search, deep research and an MCP server.

The curated verdict

Same pattern — an LLM compiles raw documents into a traceable, reviewed wiki served over MCP. arkon targets companies with department and role scoping; LLM Wiki is a personal desktop app.

arkonllm_wiki
Stars1.5k20k
Forks2922.3k
LanguagePythonTypeScript
LicenseNOASSERTIONNOASSERTION
Last activity3 months agoyesterday
Topicsragrag, knowledge-graphs
Curated connections34

arkon — the curator's take

The MRP pipeline is the differentiator: instead of chunk-and-index, documents are compiled into merged, source-traceable wiki pages behind a plan-review gate — knowledge management, not just retrieval — with department-scoped serving over one MCP endpoint. When NOT: the license is NOASSERTION, a real blocker for the enterprises it targets — clarify before adoption; ★1.2k young, and the compile-everything approach costs LLM tokens where a plain vector store costs none.

llm_wiki — the curator's take

Pick LLM Wiki if you like Karpathy's 'compile knowledge once instead of re-retrieving it every query' idea but don't want to wire it up yourself: drop in PDFs, Office docs, EPUBs or web clips and an LLM writes and maintains source-traced wiki pages, with Louvain clusters, gap-finding and deep research on top, plus an MCP server and a skill so Claude Code or Codex can query it. It's a personal, single-user desktop app — not a team knowledge service (see arkon) — and every ingest spends LLM tokens on a two-step analyse-then-write pass, so big corpora cost real money. Licence is GPL-3.0 (the GitHub API reports NOASSERTION): fine to use, copyleft if you fork and redistribute.