Alternatives to Axis Communications
Other Physical access control and video security vendors we measure, sorted by how much they publish that Axis Communications does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 29 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 “publishes and Axis Communications does not” is the one that closes them.
| Vendor | Score | Publishes, and Axis Communications does not | Axis Communications publishes, and they do not | |
|---|---|---|---|---|
| Kisigetkisi.com | 57/100 | 5 Data processing agreement, Data location stated, Public pricing, +2 | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Genetecgenetec.com | 43/100 | 4 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 1 Status page with history | Compare |
| Rhombusrhombus.com | 43/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | 1 Status page with history | Compare |
| ButterflyMXbutterflymx.com | 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.com | 59/100 | 3 Data location stated, Public pricing, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| SmartRentsmartrent.com | 39/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Milestone Systemsmilestonesys.com | 30/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Status page with history, Certifications named | Compare |
| Ambient.aiambient.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 |
| Envysionenvysion.com | 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 |
| ProdataKeyprodatakey.com | 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 |
| Avigilonavigilon.com | 27/100 | 2 HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Brivobrivo.com | 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.