Alternatives to Device42
Other IT documentation and asset tracking vendors we measure, sorted by how much they publish that Device42 does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 that differ from Device42 on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Device42 has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Device42 does not” is the one that closes them.
| Vendor | Score | Publishes, and Device42 does not | Device42 publishes, and they do not | |
|---|---|---|---|---|
| Ardoqardoq.com | 48/100 | 5 Subprocessor list, Status page with history, Public pricing, +2 | 2 Data location stated, Certifications named | Compare |
| Electricelectric.ai | 48/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Lansweeperlansweeper.com | 43/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | 1 Certifications named | Compare |
| Orbusorbussoftware.com | 39/100 | 4 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 1 Certifications named | Compare |
| Planviewplanview.com | 39/100 | 4 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 1 Data location stated | Compare |
| Toriitoriihq.com | 39/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 1 Data location stated | Compare |
| Avolutionavolutionsoftware.com | 39/100 | 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Cledaracledara.com | 39/100 | 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Zylozylo.com | 39/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Bizzdesignbizzdesign.com | 38/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | nothing | Compare |
| Sastrifysastrify.com | 35/100 | 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact | 1 Certifications named | Compare |
| Josysjosys.com | 26/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 2 Data location stated, Certifications named | 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.