Flock vs Rekor

The short version

Flock Safety and Rekor both sit in the automatic license plate recognition market, but they are not the same kind of purchase. Flock is best known for managed LPR cameras, a public-safety platform, hotlist alerts, investigation tools, and a national LPR network. Rekor Scout is positioned more like ALPR and vehicle-recognition software that can run on existing or third-party camera infrastructure.

That difference matters more than the brand name. A city buying Flock is often buying a bundled camera, software, network, and subscription relationship. A buyer looking at Rekor may be asking whether it can use current IP cameras, keep more deployment control, self-host parts of the system, or configure retention differently through an enterprise setup.

There is no honest universal answer to which is better. The better question is what the buyer needs to control: hardware, data retention, sharing, audits, hosting, integrations, procurement terms, or public trust.

What Flock is selling

Flock's public product pages describe license plate readers, video cameras, drone products, gunshot detection, FlockOS, Flock Nova, Flock FreeForm, a National LPR Network, and investigation tools as part of a broader public-safety platform.

For a police department or city council, that is the appeal. Flock can look like a one-vendor package: cameras in the field, alerts, searches, integrations, maps, and investigative workflow. Flock's developer documentation also describes APIs for device data, hotlists, vehicle-detection ingest, plate lookup, alerts, CAD, and geolocation.

That breadth can be useful. It can also make oversight harder. A council should not review Flock as just a camera purchase if the real system includes data search, sharing, hotlists, APIs, alerts, and network features.

What Rekor is selling

Rekor Scout's documentation says Scout runs on the buyer's hardware or application and enables automatic license plate recognition from any IP camera. It also says Scout can be used as a general surveillance tool or as an engine to add LPR capabilities to other applications.

The Scout dashboard documentation says Rekor can recognize license plate number, make, model, color, and direction of travel, and that results are shown in a searchable dashboard. The web server documentation says the web server collects, manages, and presents plate data produced by one or more Scout Agents, while the Agent handles the video processing.

That makes Rekor feel less like a single fixed camera package and more like a configurable ALPR stack. The buyer still needs licenses, hosting, camera placement, policies, and support. But the architecture conversation starts in a different place.

The hardware question

Hardware is one of the cleanest differences. Flock is known for its own LPR camera deployments. Public city contracts and local coverage commonly describe camera counts, pole or installation work, subscriptions, and renewals around Flock cameras.

Rekor Scout documentation says it works from any IP camera and can recognize plates from IP, traffic, or security cameras. That does not mean every existing camera will work well. Rekor's system requirements page says performance depends on vehicle speed and angle, video resolution, the number of streams, other CPU load, and traffic volume.

For a buyer, the practical question is simple: are you buying new field hardware, or are you trying to add ALPR to cameras and infrastructure you already control. Flock may be cleaner if the city wants a packaged deployment. Rekor may be more interesting if the city has usable cameras, IT capacity, and a reason to control more of the stack.

Retention and hosting

Flock's public messaging says it uses a standard 30-day retention limit that can be modified based on state laws and community preferences. Many public city pages and contracts around Flock also describe 30-day retention, though the exact rule should be checked in the local policy and contract.

Rekor's public documentation is more plan-specific. Rekor Scout Basic allows data retention up to five days. Rekor Scout Pro allows up to 60 days. Rekor Scout Enterprise says retention is completely configurable and can send data to cloud, self-hosted on-premises, or GovCloud hosting.

That is a major procurement point. Short retention is not automatically better if evidence needs are different, and configurable retention is not automatically safer if the city never sets a strict policy. The buyer should decide the retention rule before the contract, then make the system enforce it.

Pricing is not one number

Flock pricing is usually discovered through public contracts, quotes, agenda packets, and city budget records rather than a public checkout page. Existing public examples in this site's reporting show Flock purchases often structured as subscriptions with camera counts, service terms, implementation details, and renewal exposure.

Rekor publishes more self-serve Scout plan information. Its documentation lists Scout Basic at $12 per month per camera and Scout Pro at $72 per month per camera, while Scout Enterprise is available only by sales contract and billed per license. That does not make Rekor automatically cheaper for a government deployment, because enterprise terms, hardware, hosting, installation, IT labor, and support can change the total cost.

A fair comparison needs a three-year or five-year total cost. Include cameras, poles, power, bandwidth, installation, licenses, renewals, warranty, removal, data export, staff time, audit reporting, and contract exit costs. The cheapest line item can become expensive if the city has to rebuild oversight later.

Privacy and public trust

Both vendors know privacy is the hard part. Flock's public materials emphasize retention limits, encryption, audit trails, and customer controls. Rekor has also pushed privacy messaging, including an incident-based data-retention patent announcement that says data not connected to a crime or lesser offenses can be subject to shorter or no retention periods depending on policy.

Vendor privacy language is only the start. Residents will ask different questions: who can search the database, whether searches require a case number, whether outside agencies can access data, whether federal immigration enforcement can benefit from local plate reads, whether audit logs are reviewed, and whether misuse is reported publicly.

That means Flock vs Rekor should never be framed only as a technology comparison. The winning proposal is the one with the better public policy, clearer logs, narrower sharing, shorter retention where appropriate, and more credible oversight.

Which buyer fits each vendor

Flock is likely a stronger fit for agencies that want a managed public-safety camera package, fast field deployment, one vendor relationship, hotlist alerts, investigation workflow, and access to Flock's broader platform. That convenience is exactly why city councils should review sharing, APIs, data retention, search rules, and network controls in detail.

Rekor is likely a stronger fit for buyers that already have cameras, want ALPR software layered onto existing infrastructure, need cloud or on-premises options, have technical staff to manage deployment questions, or want more configurable retention and hosting. That flexibility also creates responsibility. Someone still has to design the policy, run audits, and explain the system to the public.

For private businesses, campuses, and HOAs, Rekor's self-serve plans may be easier to evaluate up front. For cities and police departments, the real comparison should happen through public quotes, contracts, data-policy exhibits, and demos that show exactly how searches, sharing, alerts, and retention work.

Questions to ask before choosing

Ask both vendors whether the buyer owns or leases the cameras, who controls camera placement, how plate reads are stored, where data is hosted, how long data is retained, who can search it, whether every search requires a case number, and whether audit logs can be exported for public review.

Ask whether outside agencies can search local data directly, request searches indirectly, or receive alerts through shared hotlists. Ask what happens if the contract ends: camera removal, data deletion, data export, refund rights, and how fast access is shut off.

Then ask for a live demo of the settings that matter. A retention promise, sharing promise, or audit promise should be visible in the product and written into the contract.

The bottom line

Flock vs Rekor is really packaged network vs configurable ALPR stack. Flock may be easier for a city that wants a managed public-safety deployment. Rekor may be more attractive when the buyer wants to use existing cameras, self-host, tune retention, or keep more infrastructure control.

Neither choice removes the governance problem. License plate readers create searchable vehicle-location records. That means the buyer needs public process, written policy, retention controls, audit logs, sharing limits, and a clean exit plan before the cameras start collecting data.

The right vendor is the one that can prove those controls in writing, in product settings, and in public records.

Sources used

Flock Safety, License Plate Readers product page: https://www.flocksafety.com/products/license-plate-readers

Flock Safety, Developer Platform overview and API documentation: https://docs.flocksafety.com/developer-hub/docs/introduction

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

Rekor Scout documentation, Scout overview: https://docs.rekor.ai/scout

Rekor Scout documentation, dashboard overview: https://docs.rekor.ai/scout/scout-dashboard/overview

Rekor Scout documentation, subscriptions and licensing: https://docs.rekor.ai/scout/getting-started/subscriptions-and-licensing

Rekor Scout documentation, system requirements: https://docs.rekor.ai/scout/agent/system-requirements

Rekor Scout documentation, web server overview: https://docs.rekor.ai/scout/web-server/overview

Rekor Systems, incident-based data retention patent announcement, March 18, 2026: https://www.globenewswire.com/news-release/2026/03/18/3258063/0/en/rekor-systems-secures-landmark-patent-for-incident-based-data-retention-replacing-outdated-alpr-and-vehicle-dragnets-with-privacy-first-intelligent-storage.html

City of Troy, Michigan, public council packet and Flock order form, August 18, 2025: https://apps.troymi.gov/Meetings/Meetings/DownloadPDF/6883733