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