Transparency alternatives to CARTO
Other GIS and mapping vendors we measure, sorted by how much we found at them and not at CARTO. This is a comparison of disclosure, not of features or fitness.
12 shown of 52 that differ from CARTO on at least one criterion we measured for both. Public transparency score, not a product or security rating.
CARTO has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at CARTO” is the one that closes them.
| Vendor | Score | Found there, not found at CARTO | Found at CARTO, not found there | |
|---|---|---|---|---|
| Mapboxmapbox.comSee also Transparency alternatives to Mapbox | 74/100 | 6 Subprocessor list, Public pricing, Certifications named, +3 | 1 security.txt (RFC 9116) | Compare |
| GIS Cloudgiscloud.comSee also Transparency alternatives to GIS Cloud | 55/100 | 5 Subprocessor list, Public pricing, Certifications named, +2 | 2 Status page with history, HTTPS enforced with HSTS | Compare |
| Planetplanet.comSee also Transparency alternatives to Planet | 48/100 | 5 Subprocessor list, Public pricing, Certifications named, +2 | 3 Data location stated, Status page with history, security.txt (RFC 9116) | Compare |
| MetaLocatormetalocator.comSee also Transparency alternatives to MetaLocator | 38/100 | 4 Data processing agreement, Public pricing, Notice before subprocessors change, +1 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | Compare |
| LightBoxlightboxre.comSee also Transparency alternatives to LightBox | 57/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Safe Software FMEsafe.comSee also Transparency alternatives to Safe Software FME | 52/100 | 3 Data processing agreement, Certifications named, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Feltfelt.comSee also Transparency alternatives to Felt | 39/100 | 3 Public pricing, Certifications named, Named privacy contact | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Geoapifygeoapify.comSee also Transparency alternatives to Geoapify | 30/100 | 3 Data processing agreement, Public pricing, No third-party tracking before consent | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | Compare |
| Mapmemapme.comSee also Transparency alternatives to Mapme | 22/100 | 3 Public pricing, Uptime SLA with a figure, No third-party tracking before consent | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | Compare |
| Alteryx Spatialalteryx.comSee also Transparency alternatives to Alteryx Spatial | 39/100 | 2 Public pricing, Certifications named | 1 Status page with history | Compare |
| Bentley Systemsbentley.comSee also Transparency alternatives to Bentley Systems | 39/100 | 2 Data processing agreement, Named privacy contact | 1 Data location stated | Compare |
| Pointlypointly.aiSee also Transparency alternatives to Pointly | 39/100 | 2 Public pricing, Named privacy contact | 1 Status page with history | 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.