Transparency alternatives to TagoIO
Other IoT platforms and connectivity vendors we measure, sorted by how much we found at them and not at TagoIO. This is a comparison of disclosure, not of features or fitness.
12 shown of 43 that differ from TagoIO on at least one criterion we measured for both. Public transparency score, not a product or security rating.
TagoIO has 8 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at TagoIO” is the one that closes them.
| Vendor | Score | Found there, not found at TagoIO | Found at TagoIO, not found there | |
|---|---|---|---|---|
| Memfaultmemfault.comSee also Transparency alternatives to Memfault | 57/100 | 5 Data location stated, Status page with history, HTTPS enforced with HSTS, +2 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Particleparticle.ioSee also Transparency alternatives to Particle | 48/100 | 5 Data location stated, Status page with history, HTTPS enforced with HSTS, +2 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| ThingsBoardthingsboard.ioSee also Transparency alternatives to ThingsBoard | 48/100 | 4 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent, +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| EMnifyemnify.comSee also Transparency alternatives to EMnify | 35/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 4 Data processing agreement, Public pricing, Certifications named, +1 | Compare |
| Siemens Insightssiemens.comSee also Transparency alternatives to Siemens Insights | 30/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 4 Data processing agreement, Public pricing, Certifications named, +1 | Compare |
| Balenabalena.ioSee also Transparency alternatives to Balena | 61/100 | 3 Subprocessor list, Status page with history, HTTPS enforced with HSTS | 1 Certifications named | Compare |
| Datacakedatacake.coSee also Transparency alternatives to Datacake | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| Mendermender.ioSee also Transparency alternatives to Mender | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| Monogotomonogoto.ioSee also Transparency alternatives to Monogoto | 30/100 | 3 Data location stated, Status page with history, HTTPS enforced with HSTS | 4 Data processing agreement, Public pricing, Certifications named, +1 | Compare |
| Onomondoonomondo.comSee also Transparency alternatives to Onomondo | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| Qbeeqbee.ioSee also Transparency alternatives to Qbee | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data processing agreement, Certifications named, Notice before subprocessors change | Compare |
| Helinhelindata.comSee also Transparency alternatives to Helin | 22/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, Named privacy contact | 4 Data processing agreement, Public pricing, Certifications named, +1 | 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.