Transparency alternatives to Xibo
Other Digital signage vendors we measure, sorted by how much we found at them and not at Xibo. This is a comparison of disclosure, not of features or fitness.
12 shown of 53 that differ from Xibo on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Xibo has 7 gaps in what we could measure: Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Named privacy contact. The column “Found there, not found at Xibo” is the one that closes them.
| Vendor | Score | Found there, not found at Xibo | Found at Xibo, not found there | |
|---|---|---|---|---|
| Appspaceappspace.comSee also Transparency alternatives to Appspace | 52/100 | 5 Status page with history, Public pricing, Certifications named, +2 | 3 Data location stated, security.txt (RFC 9116), Notice before subprocessors change | Compare |
| Yodeckyodeck.comSee also Transparency alternatives to Yodeck | 65/100 | 4 Subprocessor list, Status page with history, Public pricing, +1 | 2 Data processing agreement, security.txt (RFC 9116) | Compare |
| ScreenCloudscreencloud.comSee also Transparency alternatives to ScreenCloud | 57/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Pickcelpickcel.comSee also Transparency alternatives to Pickcel | 48/100 | 4 Subprocessor list, Public pricing, Certifications named, +1 | 3 Data processing agreement, Data location stated, security.txt (RFC 9116) | Compare |
| Poppulopoppulo.comSee also Transparency alternatives to Poppulo | 48/100 | 4 Subprocessor list, Status page with history, Certifications named, +1 | 3 Data processing agreement, Data location stated, security.txt (RFC 9116) | Compare |
| Onsignonsign.tvSee also Transparency alternatives to Onsign | 35/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 4 Data processing agreement, Data location stated, security.txt (RFC 9116), +1 | Compare |
| Navorinavori.comSee also Transparency alternatives to Navori | 39/100 | 3 Public pricing, Certifications named, Named privacy contact | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | Compare |
| Wallboardwallboard.infoSee also Transparency alternatives to Wallboard | 39/100 | 3 Status page with history, Certifications named, Uptime SLA with a figure | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | Compare |
| viewneoviewneo.comSee also Transparency alternatives to viewneo | 30/100 | 3 Public pricing, Certifications named, Named privacy contact | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
| Screenlyscreenly.ioSee also Transparency alternatives to Screenly | 26/100 | 3 Status page with history, Public pricing, Certifications named | 4 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +1 | Compare |
| Rocket Alumnirocketalumnisolutions.comSee also Transparency alternatives to Rocket Alumni | 48/100 | 2 Public pricing, Certifications named | 2 security.txt (RFC 9116), Notice before subprocessors change | Compare |
| Broadsignbroadsign.comSee also Transparency alternatives to Broadsign | 43/100 | 2 Status page with history, Named privacy contact | 2 Data location stated, 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.