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