arkon vs WeKnora
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 — Tencent's enterprise knowledge platform: one set of document bases served three ways, as RAG search, a reasoning agent with sandboxed skills, and a self-maintaining LLM wiki.
Both are self-hosted enterprise knowledge hubs with an MCP server that compile docs into something agents can query.
| arkon | WeKnora | |
|---|---|---|
| Stars | 1.5k | 37k |
| Forks | 305 | 5.0k |
| Language | Python | Go |
| License | NOASSERTION | NOASSERTION |
| Last activity | 5 months ago | 3 days ago |
| Topics | rag | rag, agents |
| Curated connections | 4 | 5 |
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.
WeKnora — the curator's take
Use it for a self-hosted team knowledge base with real operations: RBAC, audit logs, auto-sync from Feishu, Confluence, Notion and GitLab, and IM bots (WeCom, Feishu, Slack). Strongest inside the Chinese enterprise stack. Skip it if you want a library to embed rather than a platform to run, or for a single user's notes. The license is custom (NOASSERTION on GitHub), so check it before commercial use.