Independent surveillance watchdog
Replacing Flock with Axon does not end license plate surveillance.
Communities are beginning to replace Flock license plate readers with technology from Axon. The company may be different, but residents still deserve to know what is collected, how long it is stored, who can search it, where it is shared, and what safeguards are actually enforceable.
Why this page exists
Flock Safety's cameras drew scrutiny in communities across the country, and some agencies have responded by swapping vendors rather than answering the underlying questions. Axon, the company best known for Tasers and police body cameras, now sells its own fixed license plate readers and the platform that ties them together. This page examines whether the replacement changes the surveillance capabilities, the policies, or the risks, and what residents should ask before a contract is signed.
The vendor may change, but the public still deserves answers.
What Axon's vehicle surveillance products do
Axon Outpost
A fixed camera that combines three capabilities in one device: automatic license plate recognition, live video streaming, and vehicle attribute recognition. Axon describes it as designed to capture multiple lanes, day and night, at highway speeds, mountable on existing poles, buildings, trailers, or new installations, powered by solar or standard electrical service. Source: axon.com/products/axon-outpost
Axon Lightpost
The same plate reading, vehicle attribute recognition, and live video, packaged to mount on existing streetlight poles and draw power from the light itself. Axon advertises deployment in under an hour with no new infrastructure, and offers agencies help obtaining pole attachment agreements. Source: axon.com/products/axon-lightpost
Axon Fusus
The real-time crime center platform Axon acquired in 2024. Fusus pulls live video from body cameras, fixed cameras, and drones together with plate reads, 911 and dispatch data, and officer locations into one operational view. It can also ingest feeds from private and community-owned cameras that residents or businesses register, and an AI layer watches connected feeds for activity the agency defines. Source: axon.com/products/axon-fusus
Axon Vehicle Intelligence
The umbrella for Outpost and Lightpost plus the sharing layer between agencies. Axon states that plate data stays in the collecting agency's system by default, with controlled sharing an agency can enable, and that third-party cameras can join through its partner program. Whether a given town's data is actually restricted is decided by that town's contract and policy, not by the brochure. Source: axon.com/products/vehicle-intelligence
Axon versus Flock: what changes, and what does not
The two systems differ in real ways, and the differences mostly make the oversight questions bigger, not smaller. Flock's core plate readers photograph passing vehicles. Axon's ship with live video built into the same housing and feed a platform built to fuse camera feeds, plate reads, and dispatch data in real time.
| 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 |
| 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 own published product materials as of August 2026. A vendor may offer a capability that a particular agency chooses not to enable; the deciding document is always the local contract and policy.
Read the full comparison — what actually changes when an agency switches, what happens to the old data, and the questions to ask before the vote.
What stays exactly the same
- The cameras photograph every passing vehicle, not vehicles suspected of anything.
- Retention, access, sharing, and auditing are policy choices an agency makes, and can quietly change.
- There is no federal statute governing how license plate reader data is collected, kept, or shared.
- The questions a community should ask before approving the system are identical, whatever name is on the housing.
Replacing Flock with Axon is not the same as ending license plate surveillance.
Where Axon is replacing Flock
We are tracking agency transitions from Flock to Axon: which communities, which products, how many cameras, what the contracts say about retention and sharing, and whether the public was told before approval. Coverage appears in our news and incidents reporting and the article archive as it develops.
If your community is replacing Flock with Axon, or approving Axon plate readers for the first time, we want the paperwork: contracts, council agendas, policies, and public records responses. Send them to us and we will document the deployment.
Questions every community should ask
- What information does the system collect?
- Does it capture live video in addition to license plates?
- Does it identify vehicle make, model, color, or other attributes?
- How long is each plate read retained?
- Who can search the data?
- Can other agencies search it directly?
- Is federal access prohibited by policy, contract, or law?
- Are all searches tied to a case number or documented purpose?
- Are access logs reviewed by an independent party?
- What happens when a policy is violated?
- Can the system connect with private cameras or other surveillance feeds?
- Was the public informed before the contract was approved?
Take action
- Read your local contract and the department's ALPR policy. Ask for them if they are not posted.
- Submit a public records request for the contract, data-sharing agreements, and audit logs.
- Contact your elected representatives and ask the twelve questions above.
- Attend the council or commission meeting where the contract is discussed.
- Get involved with BlockFlockNow, and submit local meetings so others can attend.
- Send us contracts, agendas, and records from your community.
Sources and corrections
Product descriptions on this page cite Axon's published materials: Outpost, Lightpost, Vehicle Intelligence, and Fusus. Reporting on specific deployments links its sources in each article.
If anything on this page is inaccurate or out of date, including corrections from agencies, researchers, residents, or Axon itself, write to blockflock@bytebunny.io and we will review and correct it.