onyx vs scout
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 — Company intelligence agent that navigates Slack, Drive, wiki and CRM live — no ingest/embed pipeline — and builds its own wiki + CRM as it learns your company.
Opposite answers to company context: Onyx ingests and indexes every source up front with permissions, scout navigates Slack/Drive/CRM live with no ingest pipeline — pick by whether you'd rather run sync jobs or pay per-query latency.
| onyx | scout | |
|---|---|---|
| Stars | 33k | 754 |
| Forks | 4.8k | 75 |
| Language | Python | Python |
| License | NOASSERTION | Apache-2.0 |
| Last activity | today | 4 months ago |
| Topics | rag, agents | agents, memory |
| Curated connections | 5 | 3 |
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.
scout — the curator's take
The navigation-over-search thesis applied to company knowledge: ls/grep/follow-the-link across live sources instead of chunk-embed-pray. Built on Agno's AgentOS. Pick it to prototype a 'company brain' on live sources; skip if you need strict access-control auditing or a classic ingested RAG corpus.