The parts of the system
| Component | What it does |
|---|---|
| Cameras | Fixed ALPR units on poles, reading plates 24/7 (see what they look like) |
| FlockOS platform | Cloud storage of plate records, timestamps and vehicle descriptors |
| Hotlists | Stolen vehicles, wanted plates, AMBER alerts — plates are checked against these |
| Alerts | Real-time notification to the agency when a hotlisted plate is read |
| Data sharing | Inter-agency access agreements — a documented source of controversy |
The whole system runs on roughly 120,000 cameras across 49 states (GadgetReview), which is what turns isolated plate reads into a nationwide network.
Who buys and operates it
- Police departments — stolen-vehicle and investigation alerts
- Cities and counties — public-safety monitoring
- HOAs and gated communities — entry logging
Each customer signs a contract and sets its own data retention and sharing policy — which is why the system looks different city to city. See data retention and state-level status.
Why the system is controversial
The platform's power is also the problem: records outlive the reason they were created, and sharing agreements can route your plate data beyond your own city (documented in California). The response has been real: 23+ jurisdictions have ended their Flock contracts (live tracker). See 6 reasons it's controversial.