Transparency alternatives to ODO
Other IoT platforms and connectivity vendors we measure, sorted by how much they publish that ODO does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 44 that differ from ODO on at least one criterion we measured for both. Public transparency score, not a product or security rating.
ODO has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and ODO does not” is the one that closes them.
| Vendor | Score | Publishes, and ODO does not | ODO publishes, and they do not | |
|---|---|---|---|---|
| Balenabalena.io | 65/100 | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | nothing | Compare |
| Memfaultmemfault.com | 57/100 | 5 Data location stated, Status page with history, Public pricing, +2 | nothing | Compare |
| Particleparticle.io | 48/100 | 5 Data location stated, Status page with history, Public pricing, +2 | 1 Certifications named | Compare |
| Datacakedatacake.co | 39/100 | 3 Data location stated, Public pricing, No third-party tracking before consent | 1 Certifications named | Compare |
| EMnifyemnify.com | 35/100 | 3 Data location stated, Status page with history, Named privacy contact | 1 Certifications named | Compare |
| TagoIOtago.io | 35/100 | 3 Data processing agreement, Public pricing, Notice before subprocessors change | 1 HTTPS enforced with HSTS | Compare |
| Mendermender.io | 30/100 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | 1 Certifications named | Compare |
| Onomondoonomondo.com | 30/100 | 3 Status page with history, Public pricing, Named privacy contact | 1 Certifications named | Compare |
| Qbeeqbee.io | 30/100 | 3 Status page with history, Public pricing, security.txt (RFC 9116) | 1 Certifications named | Compare |
| Aerisaeris.com | 26/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 2 Certifications named, HTTPS enforced with HSTS | Compare |
| Hologramhologram.io | 22/100 | 3 Status page with history, Public pricing, Named privacy contact | 2 Certifications named, HTTPS enforced with HSTS | Compare |
| Siemens Insightssiemens.com | 22/100 | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | 2 Certifications named, HTTPS enforced with HSTS | 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.