FDNY Incidents on ATProto

NERIS-format fire data on decentralized protocol — LinkedClaims Demo
Dashboard
Incidents
LinkedClaims
About / Lexicon

Incidents by Category

Incidents by Borough

Fire Spread (structure fires)

Detector Presence (fire incidents)

Date Category Type Borough Address Units Duration

What Is This?

This demo shows real FDNY fire incident data converted to an ATProto lexicon format modeled after the NERIS data standard.

Fire departments are trapped by PE-owned software vendors who acquired most RMS products and raised prices 3-6x. NERIS (live Jan 1, 2026) replaced NFIRS for federal reporting, but departments still need local record management software.

Our approach: Store incident data on ATProto Personal Data Servers where departments own it. The com.linkedclaims.fire.incident lexicon maps NERIS fields to ATProto records. The com.linkedclaims.claim lexicon binds incidents to external evidence (news, inspections, cross-department patterns).

Why ATProto?

Data ownership: Each department runs their own PDS. No vendor can hold their data hostage.

Portability: Switch software anytime. Your data stays on your PDS.

Interoperability: Departments can share data across boundaries using standard protocols.

Transparency: Public incident data is truly public, not locked in a vendor's database.

Lexicon: com.linkedclaims.fire.incident

ATProto record type modeled after NERIS core incident and fire modules.