OneRecord is a modular records nexus. It finds and shows every record tied to an event or a subject — a fire incident, a drone program, a vendor — across your agency's existing systems, without moving the data and without flattening who's allowed to see what.
A small shared core, extended by declarative modules — not a monolith that has to know about every record type up front.
An anchor object — an event like Fire Incident #24-0391, or a subject like a vendor or a drone program. Hubs form a graph, not a tree, so a record can belong to more than one story.
A declarative plug-in that attaches one kind of record — 911 calls, after-action reports, policies — to hubs. New record types don't require new core code.
Everything shared: sign-in, tenants, roles, audit, search, hub pages, the connector agent. One place that's secured once, used by every module.
The cloud index holds metadata and extracted text for fast search. The content itself is fetched live from your source system — nothing sensitive sits in a second copy.
Ownership, handling markers, litigation holds, and retention dates are core to the shell — never an optional module you can turn off.
Your systems stay where they are. We index what's already there and fetch the rest on demand.
A connector agent reads metadata from your existing internal systems — no migration, no new system of record.
Matching records attach to the right event or subject automatically, building a graph staff can actually navigate.
Role-based access controls what each person sees — down to the record, not just the system.
Open a record and its full content is fetched live from the source system, not a stale copy.
OneRecord is a separate product from One Public Record (public-records request management), under the same parent brand. OPR becomes one module of OneRecord in a future phase — nothing about OPR changes today.
Early access. OneRecord is in active specification with pilot agencies. If find-everything-about-a-subject is a problem your staff hits weekly, we want to hear about your systems and build the first modules around them.
Tell us what systems you run today and what "find everything about X" currently costs your staff. We'll show you what a hub looks like for your data.
hello@onepublicrecord.com