Alternatives to Mapillary
Other GIS and mapping vendors we measure, sorted by how much they publish that Mapillary does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 25 that differ from Mapillary on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Mapillary has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Mapillary does not” is the one that closes them.
| Vendor | Score | Publishes, and Mapillary does not | Mapillary publishes, and they do not | |
|---|---|---|---|---|
| Mapboxmapbox.com | 61/100 | 7 Subprocessor list, Status page with history, Public pricing, +4 | 1 Data location stated | Compare |
| GIS Cloudgiscloud.com | 55/100 | 5 Subprocessor list, Public pricing, Certifications named, +2 | 1 HTTPS enforced with HSTS | Compare |
| Bentley Systemsbentley.com | 52/100 | 4 Data processing agreement, Status page with history, Uptime SLA with a figure, +1 | nothing | Compare |
| Safe Software FMEsafe.com | 52/100 | 4 Data processing agreement, Status page with history, Certifications named, +1 | nothing | Compare |
| LightBoxlightboxre.com | 48/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 1 HTTPS enforced with HSTS | Compare |
| Alteryx Spatialalteryx.com | 39/100 | 3 Public pricing, Certifications named, security.txt (RFC 9116) | nothing | Compare |
| Foursquarefoursquare.com | 30/100 | 3 Status page with history, Public pricing, Named privacy contact | 1 Data location stated | Compare |
| Geoapifygeoapify.com | 30/100 | 3 Data processing agreement, Public pricing, No third-party tracking before consent | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| Maptilermaptiler.com | 26/100 | 3 Public pricing, Certifications named, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Koordinateskoordinates.com | 22/100 | 3 Status page with history, Public pricing, Named privacy contact | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| Ascent Cloudascentcloud.io | 35/100 | 2 Status page with history, Certifications named | nothing | Compare |
| Atlasatlas.co | 35/100 | 2 Public pricing, Named privacy contact | nothing | 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.