scout vs WrenAI
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. — versus — Open-source GenBI engine: agents write governed SQL and deploy shareable dashboards over 22+ data sources, grounded in a Git-friendly context layer (MDL semantics, definitions, memory).
Two shapes of 'company context for agents': Scout navigates unstructured sources (Slack/Drive/wiki) building its own wiki; Wren governs the structured-data side with semantic models and SQL.
| scout | WrenAI | |
|---|---|---|
| Stars | 634 | 16k |
| Forks | 58 | 1.8k |
| Language | Python | Python |
| License | Apache-2.0 | NOASSERTION |
| Last activity | 9 days ago | 2 days ago |
| Topics | agents, memory | agents |
| Curated connections | 2 | 2 |
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.
WrenAI — the curator's take
The strongest open answer to 'my agent writes confidently wrong SQL': business definitions, approved joins and past queries live in reviewable files, not prompts, and dry-plan validation catches errors before execution. Agent-driven by design (skills + CLI, works through Claude Code/Cursor). Skip for one-off charts from a CSV — the context layer is the point, and it takes real setup.