onyx vs WeKnora
Self-hosted context layer and AI chat for teams: indexes 50+ workplace apps with permissions into a hybrid index, then serves agentic RAG, deep research, custom agents and an MCP server. — 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 enterprise knowledge platforms serving the same document base as RAG search and agent reasoning; Onyx leans on live app connectors and access-control sync.
| onyx | WeKnora | |
|---|---|---|
| Stars | 33k | 38k |
| Forks | 4.8k | 5.3k |
| Language | Python | Go |
| License | NOASSERTION | NOASSERTION |
| Last activity | today | today |
| Topics | rag, agents | rag, agents |
| Curated connections | 5 | 6 |
onyx — the curator's take
Use it when you want one permission-aware index over Slack, Drive, Confluence and friends that both humans (chat, Slack bot, Chrome extension) and coding agents (MCP) can query — the pre-built index beats agents fanning out across dozens of MCP servers on latency and tokens. Standard mode is a heavy multi-container deploy with connector sync jobs; skip it for a single doc collection or when you don't want to own an ingest pipeline.
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.