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