Mobile · Community reporting

Sentinel

See It. Report It. End It.

Sentinel puts a credible reporting channel in the hands of the public and pushes verified alerts back out to the people close enough to act. It is the sensor layer of the Arc Light network — the part that reaches where no agency budget can.

LiveiOSAndroid
01 — In the product

What it looks like in use.

Sentinel home screen showing nearby high-severity alerts, a local incident map, and a list of recent reports across the United States.
Home — nearby alerts ranked by proximity, a live local map, and recent activity nationwide.
Sentinel map screen showing BOLO and incident pins across the Tampa Bay area with report type filters and a detail sheet for a selected incident.
Map — incident and BOLO pins with hazard-type filters; a tapped pin opens its verification state.
Sentinel BOLO screen listing missing persons cases with age, location, and distance, plus a button to report a new missing person.
BOLO — missing persons sorted by distance, searchable, with one-tap reporting.
Sentinel report detail screen for a transportation hazard, showing severity, time observed, safety status, and a map of the incident location.
Report detail — hazard type, severity, time observed, safety status, and exact location.
02 — What it does

Built around four things it has to get right.

Radius-targeted alerting

Alerts are delivered to devices within a defined radius of an incident rather than broadcast to an entire user base. A BOLO reaches the neighborhood that can act on it while it still matters, instead of becoming noise three states away.

Structured incident reporting

Sixteen report categories — from missing persons and human trafficking to unexploded ordnance, cyber threats, and environmental hazards — each with its own capture fields, so a report arrives as usable structured data rather than free text.

Evidence capture at the point of observation

Photo and video capture is bound to the report at the moment it is taken, with location recorded at capture time. That coupling is what makes a citizen report defensible enough for an investigator to act on.

Missing persons amplification

Missing persons cases are cross-referenced against national records and amplified across the local network, turning a static database entry into an active search in the area that matters.

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

Capture

Native clients — SwiftUI on iOS, Kotlin on Android — handle capture, permission flows, and location acquisition. Reports are queued locally so a submission survives poor connectivity in the field and syncs when the device recovers.

02

Verify

Incoming reports pass through a multi-factor veracity assessment that weighs community corroboration, cross-references against authoritative third-party feeds, and accounts for submitter history. Confidence travels with the report rather than being decided once at intake.

03

Distribute

Verified incidents are matched against the geospatial index of subscribed devices and dispatched through platform push infrastructure. Targeting happens server-side so the client never needs the full incident set to know what concerns it.

04

Feed the network

Every accepted report enriches Sleuth Net and the analytics layer, so field observations compound into pattern detection instead of terminating at a single alert.

04 — The tech

What it is built on.

iOS
SwiftSwiftUIMapKit
Android
KotlinJetpack
Backend
Firebase AuthCloud FirestoreCloud Functions
Delivery
Firebase Cloud MessagingAPNs

Data sources

Sentinel draws on authoritative external feeds alongside our own network, so community reporting is corroborated rather than taken on faith.

NamUs missing persons recordsNASA EONET hazard eventsCommunity reports
Next step

Want to see Sentinel against your own use case?