Transparency alternatives to Dronedesk
Other Drone operations vendors we measure, sorted by how much we found at them and not at Dronedesk. This is a comparison of disclosure, not of features or fitness.
12 shown of 33 that differ from Dronedesk on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Dronedesk has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Dronedesk” is the one that closes them.
| Vendor | Score | Found there, not found at Dronedesk | Found at Dronedesk, not found there | |
|---|---|---|---|---|
| DroneDeploydronedeploy.comSee also Transparency alternatives to DroneDeploy | 65/100 | 5 Subprocessor list, Data location stated, Status page with history, +2 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Propeller Aeropropelleraero.comSee also Transparency alternatives to Propeller Aero | 52/100 | 4 Data processing agreement, Data location stated, Status page with history, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Aloftaloft.aiSee also Transparency alternatives to Aloft | 26/100 | 3 Data location stated, Status page with history, Certifications named | 4 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
| Airdataairdata.comSee also Transparency alternatives to Airdata | 39/100 | 2 Data location stated, Status page with history | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Aeroboticsaerobotics.comSee also Transparency alternatives to Aerobotics | 35/100 | 2 Data processing agreement, Notice before subprocessors change | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Raptor Mapsraptormaps.comSee also Transparency alternatives to Raptor Maps | 26/100 | 2 Data location stated, Certifications named | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| Firmatekfirmatek.comSee also Transparency alternatives to Firmatek | 26/100 | 1 Data location stated | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Perceptopercepto.coSee also Transparency alternatives to Percepto | 26/100 | 1 Data location stated | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Flyabilityflyability.comSee also Transparency alternatives to Flyability | 22/100 | 1 Data processing agreement | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| Pix4Dpix4d.comSee also Transparency alternatives to Pix4D | 22/100 | 1 Status page with history | 2 Public pricing, Named privacy contact | Compare |
| Wingtrawingtra.comSee also Transparency alternatives to Wingtra | 22/100 | 1 Data location stated | 3 Public pricing, security.txt (RFC 9116), Named privacy contact | Compare |
| FlytBaseflytbase.comSee also Transparency alternatives to FlytBase | 17/100 | 1 Certifications named | 2 Public pricing, 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.