- When a documented, independently verified security/compliance posture is required
- If procurement requires SOC 2 Type II or ISO 27001 proof in publicly available form, Parkva’s public materials may not satisfy that requirement; request formal attestations during due diligence.
- When transparent, published, self-serve pricing is required
- Parkva provides quote-based pricing; organizations that require publicly posted tiered pricing for budget planning may prefer vendors that publish standard pricing.
- When full hardware ownership without return obligations is required
- Parkva’s default subscription terms treat equipment as vendor-owned unless a contract explicitly states a purchase; buyers that require full ownership should negotiate contract terms explicitly.
- When the organization cannot staff human review and governance
- Parkva materials and independent operational commentary indicate human review is typically required before enforcement actions; organizations lacking review capacity may not be a good fit.
- When reputational risk from LPR deployments is a primary constraint
- Where stakeholder management, communication, and formal policy guardrails are not in place, the reputational and regulatory risks associated with LPR deployments may outweigh potential operational benefits.
- Current limitations acknowledged by vendor or strongly implied
- Site-sensitivity
- Accurate capture depends on proper mounting, angle, lighting, and control-unit thermal management; manual highlights in the user manual underscore these sensitivities.
- Third-party connectivity dependency
- Service availability and performance can be affected by carrier networks and cloud provider availability outside of vendor control.
- Vendor service control
- Terms permit suspension or remote disabling of service under certain conditions; buyers should review terms for continuity and remediation provisions.
- Roadmap / not yet available
- No public product roadmap with delivery dates was identified in the reviewed materials.
- Scale limitations
- Public materials do not provide extensive evidence of very large-scale enterprise deployments; buyers should request references and scale case studies if needed.
- Security or compliance gaps
- No public SOC 2 or ISO attestations were located; treat absence of public attestations as a due-diligence gap until validated under NDA.
- API limitations or integration constraints
- An "open API" is referenced, but public API documentation and technical integration details are not available; procurement should validate API capabilities, authentication models, rate limits, and data schemas.