Alternatives to Hanwha Vision
Other Physical access control and video security vendors we measure, sorted by how much they publish that Hanwha Vision does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 29 that differ from Hanwha Vision on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Hanwha Vision has 11 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Hanwha Vision does not” is the one that closes them.
| Vendor | Score | Publishes, and Hanwha Vision does not | Hanwha Vision publishes, and they do not | |
|---|---|---|---|---|
| Kisigetkisi.com | 57/100 | 6 Data processing agreement, Data location stated, Public pricing, +3 | 1 No third-party tracking before consent | Compare |
| Genetecgenetec.com | 43/100 | 6 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +3 | 1 No third-party tracking before consent | Compare |
| Rhombusrhombus.com | 43/100 | 6 Data location stated, Public pricing, Certifications named, +3 | 1 No third-party tracking before consent | Compare |
| Verkadaverkada.com | 59/100 | 5 Data location stated, Status page with history, Public pricing, +2 | 1 No third-party tracking before consent | Compare |
| SmartRentsmartrent.com | 39/100 | 4 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| ButterflyMXbutterflymx.com | 35/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Milestone Systemsmilestonesys.com | 30/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 No third-party tracking before consent | Compare |
| Avigilonavigilon.com | 27/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 1 No third-party tracking before consent | Compare |
| Ambient.aiambient.ai | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Envysionenvysion.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| ProdataKeyprodatakey.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
| Brivobrivo.com | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 1 No third-party tracking before consent | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.