Crucix vs flowsint
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 — Self-hosted OSINT investigation platform — explore entities on a Neo4j-backed visual graph and expand them with 30+ enrichers: DNS/WHOIS/subdomains, breach checks, Maigret, crypto wallets.
The two OSINT postures: flowsint investigates — entity graphs, enrichers, case building on Neo4j; Crucix monitors — 27 live feeds, alerts when the world changes. Depth on a target vs breadth on the planet.
| Crucix | flowsint | |
|---|---|---|
| Stars | 11k | 7.5k |
| Forks | 1.7k | 937 |
| Language | JavaScript | TypeScript |
| License | AGPL-3.0 | Apache-2.0 |
| Last activity | 2 months ago | 26 days ago |
| Topics | security, web | security |
| Curated connections | 2 | 3 |
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.
flowsint — the curator's take
The open-source Maltego-shaped option: drop an email, domain, wallet or username on the canvas and chain enrichers to grow the relationship graph — privacy-first (everything stays on your machine, API keys in an encrypted vault), team-deployable with one exposed port, and the UI stays responsive at thousands of nodes. Use it for structured recon and OSINT investigations: journalists, security analysts, fraud teams. NOT an AI tool — there is no LLM in the loop; the n8n connector is the automation escape hatch, and its place in this catalog is as the investigation surface your agents and workflows can feed. Early development, tests admittedly incomplete; read ETHICS.md — the responsible-use line is enforced culturally, not technically.