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