Request Briefing

Under the Command View

The Agent Team.

Five agents ship at deployment. Every month after that, new agents are built around how your agency actually operates.

Agents vs Rules

From alerts to understanding.

A single camera detects suspicious activity. A traditional rule generates an alert. ORION recognizes related activity across multiple cameras, recent CAD calls, LPR data, and open investigations—identifying a developing pattern instead of producing another isolated notification.

Alert RuleORION Agent
TriggerSingle conditionCross-source pattern
ContextNoneFull data environment
ActionNotificationSurfaced intelligence + defined action
LearningStaticContinuous refinement

Starter Catalog

The five starter agents.

Every agent refines continuously against your live data environment.

BOLO Agent

BOLO Agent

"The stolen vehicle that drove past a Flock camera at 2am. The plate read that matched a BOLO on the Motorola channel. The hit that happened in the data — and nowhere else."

The BOLO Agent scans LPR, camera, and dispatch feeds continuously for matches against active BOLOs and stolen vehicle lists. The match surfaces in the command view in seconds. The agent learns which match patterns your command staff act on — and sharpens its thresholds against your agency's live response history.

FLOCK · FUSUS · MARK43 · MOTOROLA APX

Dispatch Agent

Dispatch Agent

"Units arrive on scene with less information than the camera on the corner already has."

The Dispatch Agent correlates live CAD calls with surrounding intelligence — cameras, nearby plate reads, officer activity — before units arrive. Over time, the agent learns which correlation patterns your dispatchers rely on and pre-stages that intelligence earlier in the call lifecycle.

MARK43 · MOTOROLA APX · AVIGILON

Investigations Agent

Investigations Agent

"A connection that exists across RMS, body cam footage, LPR history, and surveillance feeds — and takes an investigator three weeks to find manually."

The Investigations Agent pulls threads across every data source and surfaces connections investigators would otherwise spend weeks chasing. It refines its inference weights against the case outcomes your investigators confirm — becoming more accurate at spotting the signal patterns specific to your jurisdiction.

AXON · MARK43 · FLOCK · AVIGILON

Patrol Agent

Patrol Agent

"An officer responding to a routine call with no context on what's happened at that address in the last 90 days."

The Patrol Agent delivers situational awareness as a clean feed, not a research task — what happened here recently, who's wanted, what's active nearby. It learns which briefing elements your patrol officers actually reference in the field and prioritizes those on future calls.

MARK43 · FLOCK · MOTOROLA APX

Cross-Jurisdictional Agent

Cross-Jurisdictional Agent

"A suspect crosses a jurisdictional line and effectively disappears from your operational picture."

The Cross-Jurisdictional Agent correlates your open incidents against intelligence from neighboring agencies and regional networks, in real time. As more agencies join the network, the agent's reach — and its ability to spot cross-boundary patterns — compounds.

REGIONAL LPR · MUNICIPAL CAMERAS · ALLIED FEEDS

Agent 06+

Agent 06+ — Your Operational Priorities

Every agency operates differently. The BOLO Agent watches for the same patterns everywhere. Custom agents are built around your agency's specific workflows, data quirks, regional threats, and command staff priorities. We scope, build, and ship them monthly.

BUILT AROUND YOUR STACK

The Engineering Model

Built around your agency.

No two agencies operate the same way. That's why our engineering team works directly with yours to develop agents around your operational priorities, investigative workflows, and command needs — so ORION continues to support the way your agency operates, without asking your agency to adapt to it.

Request a Strategy Briefing