Softwr

Cybersecurity · head to head

Motorola Vigilant vs Very Good Security

Motorola Vigilant logo

Motorola Vigilant

Cybersecurity

Fixed and mobile licence plate recognition with a shared law enforcement plate database

From
On request
Rated
-
Full reviewWebsite
Very Good Security logo

Very Good Security

Cybersecurity

Tokenisation proxy that keeps card and personal data out of your own systems and out of PCI scope

From
$1000/month
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Motorola Vigilant state law can decide eligibility outright: California's SB 34 imposes operator duties and restricts sharing ALPR data with out-of-state and federal agencies, and agencies have been audited and found non-compliant.; Very Good Security vGS sits in the live path of every request carrying sensitive data, so its latency and availability become yours, and an outage in the proxy is a payment outage no matter how healthy your own systems are.
  • They diverge on capability: Motorola Vigilant covers Fixed LPR cameras, Very Good Security covers Aliasing proxy.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Motorola Vigilant and Very Good Security actually diverge.

Attributes where Motorola Vigilant and Very Good Security differ
AttributeMotorola VigilantVery Good Security
Starting priceOn request$1000/month
Pricing modelquotePer month
PlatformsWeb, Windows, iOS, AndroidWeb, API

Identical on both: free tier (No), user rating (Not yet rated), category (Cybersecurity).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Motorola Vigilant

  • Fixed LPR cameras
  • Mobile LPR
  • LEARN database
  • VehicleManager analytics
  • Hotlist alerting
  • Published API
  • Audit logging

Only in Very Good Security

  • Aliasing proxy
  • PCI scope reduction
  • Network tokenisation
  • Processor optionality
  • Card issuing data
  • Vault and access controls
  • Data residency options
  • Compliance artefacts

What people use each for

The jobs each tool is most often brought in to do.

Motorola Vigilant

  • A police department building a hotlist alerting network on arterial roads into a jurisdictionnot Very Good Security
  • An investigator reconstructing a suspect vehicle's movements across multiple agency jurisdictionsnot Very Good Security
  • A toll or parking authority enforcing against a registered vehicle listnot Very Good Security
  • A sheriff's office locating a vehicle associated with an active AMBER or missing person alertnot Very Good Security

Very Good Security

  • A marketplace facing its first PCI DSS Level 1 assessment that wants to keep card data off its own estate rather than harden a dozen servicesnot Motorola Vigilant
  • A merchant negotiating with a second acquirer that needs card credentials portable so the negotiation is real rather than theoreticalnot Motorola Vigilant
  • A fintech collecting bank account and identity documents that wants sensitive fields absent from logs, backups and analytics warehouses by constructionnot Motorola Vigilant
  • A card issuer that must display a full PAN in its own mobile app without the app or its backend touching cardholder datanot Motorola Vigilant

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Motorola Vigilant

  • State law can decide eligibility outright: California's SB 34 imposes operator duties and restricts sharing ALPR data with out-of-state and federal agencies, and agencies have been audited and found non-compliant.
  • Local surveillance technology ordinances increasingly require a published usage policy, retention limits and a public council hearing before purchase, which can add many months or block the procurement entirely.
  • Motorola has faced litigation over its dual role as ALPR operator and end user, so the legal exposure of the data-sharing model is unresolved and sits partly with the purchasing agency.
  • The value comes from the shared LEARN database, which means the capability an agency actually buys depends on what other agencies contribute, and that can shrink if peers withdraw for legal or political reasons.
  • Nothing is published on price, and camera hardware, database subscription and analytics are separate line items, so the multi-year total is far higher than the initial camera quote suggests.

Very Good Security

  • VGS sits in the live path of every request carrying sensitive data, so its latency and availability become yours, and an outage in the proxy is a payment outage no matter how healthy your own systems are.
  • Token portability is the whole selling point yet leaving VGS means migrating tokens back out, a project the vendor has no incentive to streamline, so the lock-in you removed from your acquirer partly moves to VGS.
  • Entry pricing at around one thousand US dollars a month is real money for a pre-revenue fintech, and it buys volume-limited throughput, so cost scales with exactly the growth that made you buy it.
  • Scope reduction is not scope elimination: your QSA still assesses how you integrate, and teams regularly discover that a support tool or an internal admin screen pulled plaintext back in and dragged systems into scope again.
  • Proxy-based interception constrains how you design request flows, and non-standard payloads, streaming uploads or binary formats often need custom routing rules that make debugging production issues noticeably harder.

Pricing, plan by plan

Motorola Vigilant

On request
  • Vigilant LPR$undefined/year
    • Fixed and mobile camera hardware quoted per unit
    • LEARN database access subscribed per agency
    • Analytics software licensed separately

Very Good Security

$1000/month
  • Starter$1000/month
    • Aliasing proxy
    • Vault storage
    • PCI scope reduction
  • Growth$undefined/month
    • Network tokenisation
    • Multiple processors
    • Data residency options
  • Enterprise$undefined/year
    • Custom vault architecture
    • Dedicated support and SLA
    • Contractual compliance coverage

Which should you pick?

Choose Motorola Vigilant if

  • You need fixed lpr cameras.
  • You work on Web, Windows, iOS, Android.
  • You also want mobile lpr.
Motorola Vigilant review

Choose Very Good Security if

  • You need aliasing proxy.
  • You work on Web, API.
  • You also want pci scope reduction.
Very Good Security review

Questions people ask

Is Motorola Vigilant or Very Good Security better?
Neither clearly leads. Motorola Vigilant starts at On request and Very Good Security at $1000/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Motorola Vigilant or Very Good Security?
Motorola Vigilant starts at On request and Very Good Security at $1000/month.
Does Motorola Vigilant or Very Good Security run on more platforms?
Motorola Vigilant runs on Web, Windows, iOS, Android. Very Good Security runs on Web, API.
What is Motorola Vigilant best used for?
Motorola Vigilant is most often used for a police department building a hotlist alerting network on arterial roads into a jurisdiction, an investigator reconstructing a suspect vehicle's movements across multiple agency jurisdictions, a toll or parking authority enforcing against a registered vehicle list, a sheriff's office locating a vehicle associated with an active amber or missing person alert. Of those, a police department building a hotlist alerting network on arterial roads into a jurisdiction and an investigator reconstructing a suspect vehicle's movements across multiple agency jurisdictions are not what Very Good Security is typically brought in for.
What can Motorola Vigilant do that Very Good Security cannot?
Motorola Vigilant covers Fixed LPR cameras, Mobile LPR, LEARN database, VehicleManager analytics. Very Good Security covers Aliasing proxy, PCI scope reduction, Network tokenisation, Processor optionality.

Answered from the vendors’ own pages

Motorola Vigilant: What is LEARN?

The Law Enforcement Archival Reporting Network, the shared database where plate reads from subscribing agencies are stored and queried. It is the core of the product.

Very Good Security: Does VGS make me PCI compliant?

No. It removes cardholder data from your systems so your assessment covers a far smaller boundary, but you still complete an assessment and your integration is part of it.

Motorola Vigilant: Can any agency buy it?

No. Several states restrict ALPR use and data sharing, and many municipalities require a published usage policy and a public hearing first. Check statute and local ordinance before budgeting.

Very Good Security: Can I move to another processor without re-collecting cards?

Yes, that is a core reason people buy it. The vault reveals stored credentials to whichever processor you route to.

Motorola Vigilant: Does California allow sharing with federal agencies?

SB 34 restricts sharing ALPR information with out-of-state and federal agencies, and California agencies have been audited on precisely that point.

Very Good Security: What does it cost?

Published entry pricing is about one thousand US dollars per month; growth and enterprise tiers are quoted.

Motorola Vigilant: Is it only for police?

No. Toll and parking authorities, and some commercial repossession and insurance operations, also use LPR, though the LEARN law enforcement network is agency restricted.

Very Good Security: Is it only for card data?

No. The proxy handles any sensitive field, including bank details, national identifiers and documents, though payments is where the product is now focused.

Share

Related pages

More on Motorola Vigilant

More on Very Good Security

Keep looking

Other head to heads