Axon ALPR · Comparison
Axon vs Flock: what actually changes when an agency switches?
Some agencies are answering criticism of Flock Safety's license plate readers by replacing them with Axon equipment. If your town is one of them, the question that matters is not which logo is on the pole. It is what the new system captures, where the data goes, and whether the rules governing it were rewritten for what the new hardware can actually do. This page compares the two systems point by point, using each vendor's own published materials.
The short version
- Both photograph every passing vehicle, read plates day and night across multiple lanes, and log identifying vehicle attributes beyond the plate.
- Axon adds live video in the same housing: its Outpost and Lightpost cameras stream video in addition to reading plates, which Flock's core plate readers do not.
- Axon's platform reaches further. Fusus, its real-time crime center software, fuses plate reads with body camera, drone, dispatch, and registered private camera feeds.
- Sharing models differ on paper. Flock built one of the largest multi-agency plate-search networks; Axon describes agency-controlled sharing that is off by default. What either means in your town is a contract term, not a slogan.
- Nothing about oversight changes on its own. Retention, access, auditing, and sharing are policy choices that survive or fail independent of the vendor.
A vendor switch is a fresh contract. That makes it the single best moment to demand better rules.
Capability by capability
| Capability | Flock | Axon |
|---|---|---|
| Reads plates day and night, multiple lanes | Yes | Yes |
| Vehicle attribute recognition (make, color, damage, other identifying features) | Yes, marketed as a vehicle fingerprint | Yes, marketed as vehicle attribute recognition |
| Live video streaming from the plate reader itself | Not on its core plate readers; video is a separate product line | Yes, built into Outpost and Lightpost |
| Mounting and power | Poles and fixed mounts, commonly solar | Poles, buildings, trailers, solar or wired; Lightpost mounts on existing streetlights |
| Real-time crime center platform | FlockOS | Fusus, including registered private and community cameras |
| Data sharing between agencies | Large multi-agency search network; participation set by each agency | Agency-controlled sharing, described by Axon as off by default |
| Surrounding ecosystem | Cameras, audio detection, drone products | Body cameras, Tasers, drones, evidence management, dispatch integrations |
| Retention and access rules | Set by each agency's policy and contract | Set by each agency's policy and contract |
Capability descriptions reflect each vendor's published product materials as of August 2026: Axon Outpost, Lightpost, Vehicle Intelligence, Fusus. A vendor may offer a capability a particular agency chooses not to enable; the deciding documents are the local contract and policy.
The differences that matter for oversight
Live video changes the stakes
A plate reader that photographs vehicles raises retention and sharing questions. A plate reader that also streams live video raises those questions plus new ones: who can watch the stream, is it recorded, how long is footage kept, and does the ALPR policy even mention video? An agency that adopts Axon under a policy written for Flock hardware may be operating live street cameras under rules that never contemplated them.
Platform reach is the quiet expansion
Fusus can pull registered private and business cameras into the agency's operational view alongside plate reads. That is a capability question communities should evaluate on its own terms, separate from the plate readers: a town that thought it was voting on cameras at four intersections may find the platform can reach much further.
The data handoff is where switches go wrong
When the vendor changes, the old database has to go somewhere. Deleted? Exported to the agency? Retained by the outgoing vendor until a contract clock runs out? The answer exists in writing in the outgoing contract, and residents are entitled to see it. This is the question most likely to go unasked during a switch, because everyone in the room is looking at the new equipment.
Questions to ask when your town is switching
- What happens to the Flock data when the agency switches to Axon?
- It depends entirely on the outgoing contract. The data may be deleted, exported to the agency, or retained by Flock for the remainder of a retention period. Ask for the specific deletion or migration terms in writing before the switch is approved.
- Does switching from Flock to Axon reduce surveillance?
- Not by itself. Both systems photograph every passing vehicle. The new hardware typically adds live video and a platform that can fuse more feeds, so the surveillance surface is equal or larger after a switch. What limits surveillance is the agency's policy and contract, not the vendor's name.
- Does the old ALPR policy carry over to the new system?
- Not automatically. A policy written for one vendor's product may say nothing about live video, private camera integration, or the new vendor's sharing features. Ask whether the policy was rewritten for the new system's actual capabilities.
- Was the switch competitively bid?
- Ask. Some agencies replace equipment through cooperative purchasing agreements or sole-source justifications rather than open bids. The procurement documents are public records showing what was compared, what it costs, and for how long.
The full checklist of twelve questions that apply to any ALPR system, whatever the vendor, is on the Axon hub.
Track it with us
We document agency transitions from Flock to Axon as they happen: the contracts, the votes, and whether the public was told. Coverage appears in news and incidents and the archive. If your community is switching, send us the paperwork — contracts, agendas, policies, records responses — and we will document it.
The short address for this campaign is noaxon.com, which lands on our Axon hub.