Horizon vs SurfSense
Your own AI news radar: monitors the sources you choose and generates daily briefings in English and Chinese — self-hosted, personal, scheduled. — versus — Open-source competitive-intelligence platform for agents: live Reddit/YouTube/TikTok/Maps/search connectors; scheduled agents produce briefs and alerts into a cited knowledge base. REST + MCP.
Both watch live sources and produce briefs; SurfSense is the platform play (connectors, API/MCP, cited knowledge base for agents), Horizon the personal radar — one human, one daily briefing.
| Horizon | SurfSense | |
|---|---|---|
| Stars | 8.2k | 15k |
| Forks | 1.2k | 1.5k |
| Language | Python | Python |
| License | MIT | NOASSERTION |
| Last activity | yesterday | yesterday |
| Topics | web, agents | web, rag |
| Curated connections | 1 | 2 |
Horizon — the curator's take
The personal-scale answer to information overload: point it at your sources, get one daily briefing instead of forty tabs — bilingual EN/中文 out of the box, run on your own machine on a schedule. NOT a research platform: it monitors and summarizes, it doesn't build a queryable knowledge base or serve agents — when the briefing needs to become infrastructure, you've outgrown it.
SurfSense — the curator's take
The interesting shape: not a scraper, the layer above — agents subscribe to live market signals (Reddit threads, YouTube, rankings, Maps) through one REST/MCP surface, scheduled runs turn findings into briefs, and everything lands in a citable knowledge base. If you're building market-monitoring agents, this saves you the connector swamp. Two honesty flags: the project just pivoted from 'NotebookLM alternative' to competitive intelligence (the README says so itself) — momentum is real but the identity is weeks old; and NO standard license resolution at review time — verify before building on it.