We may earn a commission if you buy through links on this page. It never changes a score or a ranking. How we make money
Foursquare is a hosted venue-data and geospatial service, with a free plan and pricing from $25. Replacing it depends on which part of your stack uses it: venue data, geocoding, maps, geofencing or spatial analysis. MapTiler Cloud offers a self-hosted path; Radar and HERE add location-focused services; Geocodio targets geocoding. Compare pricing at your expected volume, then confirm API, SDK, quota, export and migration details with each vendor before moving production traffic.
01Why people leave Foursquare
Usage costs need modeling
Starting prices do not show what a production workload will cost. Check metering, quotas and overage charges against expected traffic.
Integration details need confirmation
Verify API and SDK coverage, authentication, rate limits and production quotas before committing to a migration.
Hosted-service lock-in
If you need more control over deployment, data or exit options, compare self-hosting and export paths before replacing Foursquare.
02The alternatives, ranked by fit
- Hosted maps and geocoding
MapTiler CloudMapTiler CloudChoose MapTiler Cloud if your Foursquare integration is primarily for maps or geocoding, rather than venue data. Its $30 Flex tier and free plan give you a starting point for cost comparison, and a separate self-hosted path may reduce dependence on a hosted service. Confirm API and SDK fit, quotas, export options and migration work for your current data model.
Trade-off: It is not presented as a direct venue-data replacement; confirm coverage and pricing for your workload.
7.2/10from
$30/mofree plan - Geofencing and location
RadarRadarRadar is a closer fit when the job is combining maps, geofencing and location-risk tools. The listed starting price is $0.02, but usage-based pricing and annual commitments make a volume model important; confirm what the price measures. Check API and SDK support, quotas, data export and how your existing Foursquare venue workflows map to Radar before switching.
Trade-off: Annual commitments can reduce flexibility; the listed starting price does not establish your total cost.
7.0/10from
$0.02/mo - Routing and fleet tools
HERE TechnologiesHERE TechnologiesConsider HERE for fleet routing, tour planning or a location-based product that needs a broader hosted location platform. Its free allowances can help with initial evaluation, while usage charges need modeling before launch. Confirm the specific APIs and SDKs, production quotas, export terms and how much of your Foursquare integration can move without changing application behavior.
Trade-off: Usage charges need forecasting, and API details should be confirmed for your use case.
7.0/10from
Freefree plan - North American geocoding
GeocodioGeocodioGeocodio fits address cleanup, enrichment and North American geocoding better than a general venue-data replacement. The service includes an API and spreadsheet tool, and a free plan is listed; published plan prices are missing, so ask for costs at your expected volume. Scope migration around address inputs and outputs, then verify quotas, SDK support and export options.
Trade-off: Published plan prices are missing, and its stated focus is geocoding rather than venue data.
7.0/10from
Freefree plan - Cloud spatial analysis
CARTOCARTOCARTO is worth evaluating when your spatial data already sits in BigQuery or your team needs low-code spatial workflows. It puts spatial analysis in cloud data platforms, which may avoid moving analysis into a separate venue service. Pricing and API details need vendor confirmation; check supported integrations, export paths, deployment choices and the work required to translate existing Foursquare queries.
Trade-off: Pricing and API details need vendor confirmation; it is not positioned as a venue-data substitute.
6.2/10from
Custom - Apple web mapping
MapKit JSMapKit JSMapKit JS is a JavaScript mapping option for web projects, with a listed price from $8.25 and published daily quotas. It may suit a team already evaluating Apple maps, but it is not described as a venue-data replacement. Confirm token requirements, API coverage, quota behavior, export options and the migration effort before routing production requests through it.
Trade-off: Daily quotas and token requirements need verification; venue-data coverage is not established.
4.8/10from
$8.25/mo
03Side by side
| Tool | Score | From | Free plan | Best for |
|---|---|---|---|---|
 Foursquare Foursquare (current) | 6.8 | $25/mo | Yes | Apps that need venue data |
| MapTiler Cloud MapTiler Cloud | 7.2 | $30/mo | Yes | Apps needing hosted maps and geocoding |
| Radar Radar | 7.0 | $0.02/mo | No | Teams combining maps and geofencing |
| HERE Technologies HERE Technologies | 7.0 | Free | Yes | Fleet routing and tour planning |
| Geocodio Geocodio | 7.0 | Free | Yes | Address cleanup and enrichment |
| CARTO CARTO | 6.2 | Custom | No | Teams using BigQuery |
| MapKit JS MapKit JS | 4.8 | $8.25/mo | No | Web projects using JavaScript |
Questions people ask
Is the Swarm app still active?
The developer pricing information does not establish Swarm’s current status. Check its current app-store listings and Foursquare support information before depending on it. If you are building an integration, separately confirm that the APIs, access terms and data-export options support your use case; app availability alone does not establish developer API availability.
Why did Foursquare fail?
Calling Foursquare a failure overstates what its product and pricing information establishes. It is described as a venue-data and geospatial service with a free plan and pricing from $25. For a replacement decision, focus on whether its data, API access, production limits and total cost fit your workload, rather than assuming the service has failed.
Is Foursquare profitable?
Foursquare’s profitability is not published in its developer pricing information. The listed starting price and free plan describe access, not company financial performance. If financial stability matters to your architecture decision, ask the vendor about service commitments and support terms, and review the contract’s data-export and termination provisions before adopting the API.