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