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