The command center for investigations that matter.
Sleuth Net is where field reports, authoritative hazard feeds, and case work meet on one map. It is built for the people who have to turn scattered signals into a decision — investigators, analysts, and coordinators working an active problem.
Global map — live reports clustered by region, with hazard, source, and severity filters alongside the feed.
Report detail — incident record with visual evidence, mapped location, community verification, and an auditable status trail.
02 — What it does
Built around four things it has to get right.
Unified incident map
Community reports and third-party hazard data render on a single map with clustering and filtering, so density and correlation are visible at a glance instead of buried across separate tools.
Global hazard monitoring
Environmental and security events are tracked continuously from authoritative sources, giving analysts the same picture whether they are working a local case or a cross-border one.
Community validation
Forums let users corroborate and challenge reports. Professional communities require verification for full participation; unverified accounts have read-only access, keeping the validation signal meaningful.
Case tooling
Reports can be organized, annotated, and tracked over time, so an investigation accumulates context rather than restarting at every shift change.
03 — How it works
The path a signal takes.
Enough of the architecture to judge whether we know what we are doing — not enough to hand someone a blueprint.
01
Server-side ingestion
External feeds are proxied and normalized server-side, never fetched from the browser. That keeps API credentials out of the client, insulates the interface from upstream outages, and lets a failing source degrade quietly instead of breaking the map.
02
Normalization
Sources with incompatible shapes — event feeds, records systems, community submissions — are mapped into one internal hazard representation, which is what makes cross-source correlation possible at all.
03
Geospatial rendering
The map layer is built to stay responsive as incident volume grows, with clustering and viewport-driven loading so an analyst is never waiting on data they cannot see.
04
Access control
Verification tiers govern what each account can see and do, enforced at the data layer rather than hidden in the interface.
04 — The tech
What it is built on.
Frontend
React 18Google Maps JavaScript API
Backend
Firebase AuthCloud FirestoreCloud Functions
Ingestion
Server-side feed proxiesScheduled ETL workers
Infrastructure
VercelEdge caching
Data sources
Sleuth Net draws on authoritative external feeds alongside our own network, so community reporting is corroborated rather than taken on faith.
NASA EONET environmental eventsNamUs missing persons recordsSentinel community reports
