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