Crucix vs SurfSense
Self-hosted OSINT terminal: 27 open feeds — satellite fires, flights, radiation, sanctions, markets, conflict data — polled in parallel onto one Jarvis-style dashboard. LLM turns it two-way. — 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 external sources and produce briefs. SurfSense aims at competitive intelligence (Reddit/YouTube/search into a cited knowledge base); Crucix aims at geopolitical/situational awareness with real-time feeds and alert tiers.
| Crucix | SurfSense | |
|---|---|---|
| Stars | 11k | 16k |
| Forks | 1.7k | 1.5k |
| Language | JavaScript | Python |
| License | AGPL-3.0 | NOASSERTION |
| Last activity | 2 months ago | yesterday |
| Topics | security, web | web, rag |
| Curated connections | 2 | 4 |
Crucix — the curator's take
The fun kind of serious: one Node process (a single express dependency!) pulls 27 public intelligence feeds every 15 minutes onto a self-contained dashboard with a 3D globe — and hooking up an LLM makes it two-way, pushing tiered alerts to Telegram/Discord and answering /brief from your phone. Zero cloud, genuinely yours. NOT an investigation platform: it monitors the world's pulse, it doesn't build case files on entities (that's flowsint's job) — and treat the feed quality honestly: public OSINT sources carry noise, coverage gaps and occasional propaganda; alerts are leads, not conclusions. AGPL if you're embedding it commercially.
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.