Fencemaker vs Radar
Both are geofencing APIs. The core difference is the pricing model and how each treats scale: Radar bills on MTU (Monthly Tracked Users) plus API calls and caps geofence count below the enterprise tier. Fencemaker bills on API calls only, with unlimited geofences on every plan and no sales call required to see numbers.
At a Glance
| Radar | Fencemaker | |
|---|---|---|
| Pricing model | MTU + API calls | API calls only |
| Free tier | 1K MTU / 100K calls, 1,000 geofences | 100 checks/day, no card required |
| Entry paid plan | $499/month | $29/month |
| Mid tier | — (jump straight to enterprise) | $79/month |
| Geofence limit | 10K on paid plan, unlimited on enterprise only | Unlimited, every plan |
| Polygon geofences | ✓ | ✓ |
| Entry/exit webhooks | ✓ | ✓ |
| Territory hierarchies | ✗ | ✓ Built in |
| SDK requirement | Yes (iOS/Android SDKs) | No — pure REST |
| Top-tier pricing | Custom quote, sales call required | $249/month, posted publicly |
| Mapping / Geocoding | ✓ Built-in | ✓ Via Mapsi — same infra, sold separately or bundled |
Radar bundles mapping into a single monolithic platform. Fencemaker keeps geofencing focused and fast — and when you need geocoding, routing, or tiles, Mapsi runs on the same self-hosted infrastructure with its own predictable pricing. Best-of-breed, not lock-in.
Where Radar Fits
Radar is built as an all-in-one location platform — geofencing plus maps, geocoding, search, trip tracking, and fraud/compliance tooling in one product. If you need address autocomplete, routing, or fraud detection alongside geofencing, and you're prepared for enterprise-scale pricing and a sales-driven process, Radar's breadth is real.
Where Fencemaker Fits
- You just need geofencing — point-in-polygon checks, entry/exit events, webhooks — without a bundled maps/routing/fraud platform.
- You want predictable costs without tracking a second metric (MTU).
- You need more geofences than the free or first paid tier allows.
- You want territory hierarchies natively.
- You want to see pricing without a sales call.
Switching from Radar: 3 Steps
Most teams complete migration in under 2 hours.
- 1Export your geofences.
Radar lets you export via CSV or API.
GET /v1/geofences → Download as CSV - 2Import to Fencemaker.
Batch upload via CSV or API — polygon format is GeoJSON-compatible.
POST /v1/fences/batch Content-Type: application/json - 3Update your code.
Replace Radar SDK calls with Fencemaker REST endpoints — no client library required.
POST /v1/check { lat: 12.34, lng: 56.78 }
API Comparison
Radar requires SDK initialization and MTU tracking. Fencemaker is a single REST call.
Radar (SDK required)
Radar.initialize('pub_key');
Radar.trackOnce(
latitude: 40.7128,
longitude: -74.0060,
accuracy: 65
);
Radar.on('events', (result) => {
result.events.forEach(...);
});Fencemaker (pure REST)
fetch('https://api.fencemaker.app/v1/check', {
method: 'POST',
headers: {
'Authorization': 'Bearer YOUR_API_KEY'
},
body: JSON.stringify({
latitude: 40.7128,
longitude: -74.0060
})
});
// { fences: ['zone_manhattan', 'delivery_nyc'] }