Transparency alternatives to Axis Communications
Other Physical access control and video security vendors we measure, sorted by how much we found at them and not at Axis Communications. This is a comparison of disclosure, not of features or fitness.
12 shown of 44 that differ from Axis Communications on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Axis Communications has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Public pricing, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Axis Communications” is the one that closes them.
| Vendor | Score | Found there, not found at Axis Communications | Found at Axis Communications, not found there | |
|---|---|---|---|---|
| Kisigetkisi.comSee also Transparency alternatives to Kisi | 57/100 | 5 Data processing agreement, Data location stated, Public pricing, +2 | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Genetecgenetec.comSee also Transparency alternatives to Genetec | 43/100 | 4 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 1 Status page with history | Compare |
| ButterflyMXbutterflymx.comSee also Transparency alternatives to ButterflyMX | 35/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Verkadaverkada.comSee also Transparency alternatives to Verkada | 59/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| SmartRentsmartrent.comSee also Transparency alternatives to SmartRent | 39/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Rhombusrhombus.comSee also Transparency alternatives to Rhombus | 30/100 | 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact | 1 Status page with history | Compare |
| ProdataKeyprodatakey.comSee also Transparency alternatives to ProdataKey | 29/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Ambient.aiambient.aiSee also Transparency alternatives to Ambient.ai | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 3 Status page with history, Certifications named, security.txt (RFC 9116) | Compare |
| Geneagetgenea.comSee also Transparency alternatives to Genea | 30/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Avigilonavigilon.comSee also Transparency alternatives to Avigilon | 27/100 | 2 HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Spot AIspot.aiSee also Transparency alternatives to Spot AI | 26/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Brivobrivo.comSee also Transparency alternatives to Brivo | 22/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Certifications named, security.txt (RFC 9116) | 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.