Flock vs Motorola Vigilant

The short version

Flock Safety and Motorola Vigilant both sit in the license plate reader market, but they feel different in procurement. Flock is usually sold as a managed camera, alert, investigation, and shared-network package. Motorola's LPR lineup is positioned as a broader system of fixed, mobile, dual-purpose, and software-based license plate recognition tools tied into VehicleManager analytics.

For city councils, the choice is not simply which vendor reads plates better. The real question is which operating model the city can govern. Flock emphasizes fast deployment, a large fixed LPR network, real-time alerts, limited data retention, custom permissions, and usage audits. Motorola emphasizes agency control over retention and sharing, compatibility across camera types, VehicleManager analytics, and integration with other public-safety systems.

Neither option removes the privacy problem. In both cases, the city still has to decide who can search data, how long reads are kept, whether partner agencies can access the database, how audit logs are reviewed, and what happens when residents ask for proof.

What Flock is selling

Flock's public LPR page describes real-time alerts, Vehicle Signature search, audit trails, NCIC alerts for law enforcement, and access to what it calls the largest fixed LPR network. The same page says Flock connects communities, businesses, and law enforcement in a shared network with billions of monthly plate reads.

That is the core Flock pitch. A buyer is not only buying a camera. It is buying a managed public-safety workflow: camera placement, searchable vehicle data, hotlist alerts, partner footage, permissions, audits, and a platform that can connect to other Flock tools.

The benefit is speed and simplicity. The risk is that a city can approve the purchase as a small camera program while the practical system behaves like a larger regional search network. That is why the contract, sharing settings, retention period, and audit process matter as much as the camera count.

What Motorola Vigilant is selling

Motorola's U.S. license plate recognition page describes a full LPR system with fixed deployments, car-mounted readers, mobile patrol units, dual-purpose cameras, parking enforcement options, and integrations with existing video infrastructure. It says agencies can set their own retention rules according to policy and manage data sharing on their own terms.

Motorola's VehicleManager page goes further. It describes patented vehicle location analytics, access to billions of detections, partial-plate and location-based searches, date and time filters, associate-vehicle tools, predictive analytics, configurable data retention settings, and agency-managed data sharing and access.

That makes Motorola Vigilant feel more like an agency-controlled LPR and analytics stack. It may fit agencies that already run Motorola systems, need mobile and fixed LPR together, want to connect existing cameras, or want a more configurable architecture. But configurable does not automatically mean safer. It means the agency must actually configure and audit the system well.

The network question

Flock's network is part of the product story. Its LPR page markets access to partner footage across the country and says agencies can get real-time alerts and footage from partners to stop crime in motion. For investigations, that reach is attractive.

Motorola Vigilant also operates around large pools of detections. Its VehicleManager page says agencies can work with billions of detections and use location intelligence to identify past vehicle locations, possible associate vehicles, and future likely locations.

The oversight question is similar for both vendors: does the city control only its own local reads, or can users search across a broader network. If broader access exists, the council should ask who grants it, who logs it, whether search reasons are required, and whether out-of-state or federal agencies can benefit from local data.

Retention and audit controls

Flock's current LPR policy says customer LPR data is hard deleted on a rolling 30-day basis by default, unless a different schedule is required by a customer's law or policy. Its product and policy pages also point to usage audits, audit logging, role-based controls, encryption in transit and at rest, and customer ownership of LPR data.

Motorola's public LPR page says customers stay in control of LPR data and can set retention rules according to policy. Its VehicleManager page describes agency-defined retention, configurable retention settings, and agency-managed data sharing and access.

That is a clean comparison point. Flock is publicly anchoring around a default 30-day deletion rule with exceptions. Motorola is publicly emphasizing agency-defined retention. A city comparing the two should not accept either phrase at face value. It should ask for the exact retention setting in the quote, whether the vendor can change it, whether administrators can extend it, how deletion is verified, and how audit logs are exported.

Privacy risk is not theoretical

Flock has been at the center of recent city fights over immigration enforcement, data sharing, audit logs, and public trust. That is already covered across this site's city pages. The point for this comparison is simple: Flock's network value is also the source of many governance questions.

Motorola Vigilant has its own baggage. EFF reported in 2018 that ICE signed a contract with Vigilant Solutions to access its license-plate reader database, and that data from Irvine Company shopping centers fed into Vigilant's database system. EFF also reported that Vigilant shared data with as many as 1,000 law enforcement agencies nationwide and, through Digital Recognition Network, sold ALPR data to financial lenders, insurance companies, and debt collectors.

More recently, ClassAction.org reported on a proposed class action filed May 27, 2026 against Motorola Solutions. The report says the complaint alleges Motorola's ALPR systems shared identifiable vehicle and location data with federal and out-of-state agencies without notice or consent, and that Motorola's tools could analyze more than 17 years of stored data. Those are allegations, not court findings. But they show why buyers should treat Vigilant privacy review as seriously as Flock privacy review.

Pricing and contract review

There is no honest public one-line price for Flock vs Motorola Vigilant. Public contracts vary by camera count, hardware, software modules, mobile units, installation, support, integrations, hosting, and renewal terms.

A Flock proposal may look simpler because many local deals are bundled around camera subscriptions, service periods, installation, and renewals. A Motorola deal may include a different mix of fixed cameras, mobile readers, software licenses, VehicleManager access, integrations, and existing infrastructure.

The fair comparison is a three-year or five-year total cost. Include camera hardware, mounting, power, cellular or network costs, software, data storage, support, training, export fees, removal, renewal escalators, and the staff time needed to run audits. A cheaper system can become expensive if the city has to repair public trust later.

Which buyer fits each vendor

Flock is likely a stronger fit for agencies that want a managed fixed-camera LPR package, fast deployment, simple alerting, a large partner network, and a public-safety platform that can expand into other Flock tools. That convenience should trigger stricter review of network access, sharing settings, and audit logs.

Motorola Vigilant is likely a stronger fit for agencies that already use Motorola public-safety products, need fixed and mobile LPR together, want deeper vehicle-location analytics, need to integrate with existing cameras, or want retention and sharing settings defined by agency policy. That flexibility should trigger stricter review of who sets the policy and who verifies compliance.

For private businesses, campuses, HOAs, and property owners, the answer may be different again. The buyer should ask whether it wants a turnkey camera network, a broader security stack, or a more limited local-only system with narrow sharing.

Questions before choosing

Before approving either vendor, a public agency should ask for the full quote, the master services agreement, the product list, the retention setting, the sharing policy, the agency access list, the audit-log format, the public-record export process, and the deletion process after cancellation.

The agency should also ask whether federal, out-of-state, commercial, or private-sector users can access local reads directly or indirectly. The answer should be written into the policy and contract, not left as a sales-call assurance.

Most importantly, the council should require a live oversight plan. Who reviews searches, how often are audit logs checked, what misuse gets reported publicly, and how fast can the city prove that a sensitive search did or did not happen.

The bottom line

Flock vs Motorola Vigilant is a governance decision disguised as a vendor comparison. Flock offers a managed network-first LPR model. Motorola Vigilant offers a broader configurable LPR and vehicle-location analytics model.

A city can make either choice defensibly only if the contract makes retention, sharing, audits, access, and cancellation clear. Without that, the city is not buying public-safety technology. It is buying a future public meeting where nobody can explain who searched what.

The winner is not the vendor with the bigger network or the flashier analytics. It is the vendor whose system the city can actually control, explain, audit, and shut down if public trust breaks.

Sources used

Flock Safety, LPR Cameras: Automated License Plate Reader: https://www.flocksafety.com/products/license-plate-readers

Flock Safety, License Plate Reader Policy, last updated June 30, 2026: https://www.flocksafety.com/legal/lpr-policy

Flock Safety, Automated License Plate Readers and the Fourth Amendment: A Public-Safety-by-Design Perspective from Flock: https://www.flocksafety.com/blog/automated-license-plate-readers-and-the-fourth-amendment-a-public-safety-by-design-perspective-from-flock

Motorola Solutions, License Plate Readers | License Plate Recognition System: https://www.motorolasolutions.com/en_us/video-security-access-control/license-plate-recognition-camera-systems.html

Motorola Solutions, Vigilant VehicleManager LPR Software: https://www.motorolasolutions.com/en_xp/video-security-access-control/number-plate-recognition-camera-systems/vigilant-vehiclemanager-lpr-analytics-software.html

Electronic Frontier Foundation, California Shopping Centers Are Spying for an ICE Contractor, July 10, 2018: https://www.eff.org/deeplinks/2018/07/california-shopping-centers-are-spying-ice-contractor

ClassAction.org, Class Action Lawsuit Claims Motorola Solutions License Plate Readers Violate California Privacy Laws, June 17, 2026: https://www.classaction.org/news/class-action-lawsuit-claims-motorola-solutions-license-plate-readers-violate-california-privacy-laws