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