Webhook-native, self-hosted zone triggers — no SDK lock-in, no per-event pricing surprises.
Draw a polygon in the Territory Editor, or push one via the API. Zones support entry, exit, and dwell-time triggers.
Your app pings POST /api/v1/track with a lat/lon. Fencemaker runs a PostGIS point-in-polygon check against every active zone for that device.
On entered, exited, or a dwell threshold, Fencemaker delivers the event to Slack, Telegram, or a signed HTTP webhook — same request whether you have one device or ten thousand.
{
"event": "exited",
"device_id": "RIDER-042",
"territory_code": "ZONE-A",
"territory_name": "South Bengaluru",
"lat": 12.9716,
"lon": 77.5946,
"timestamp": "2026-03-06T10:59:07.000Z",
"dwell_seconds": 847
}Delivery zone checks happen on the hot path — a rider's app calls the API before a courier is assigned, and the answer needs to come back in milliseconds. Fencemaker handles the point-in-polygon check and the post-delivery webhook (dispatch, driver payout, or a Slack ping to ops) in the same request cycle, so zone logic doesn't become the bottleneck in your fulfillment flow.
See coverage by country →Technicians and vehicles need territory boundaries that trigger on arrival and departure, not GPS breadcrumbs someone has to review later. Fencemaker fires an entry webhook the moment a rep reaches an assigned territory and an exit event — with dwell time attached — when they leave, so job-start and job-end timestamps write themselves.
See coverage by country →Franchise and retail networks need to know when territory boundaries overlap and enforce them without a spreadsheet. Fencemaker stores each territory as a real PostGIS polygon, so overlap detection is a spatial query instead of a manual audit, and every boundary change is versioned and webhook-notified to the zones it touches.
See coverage by country →How a self-hosted geofencing API compares to hosted SDK platforms like Radar — deployment model, pricing structure, and data control.
Read guide →Enter and exit events aren't the whole picture. Fencemaker's device tracking and dwell-time detection catch devices that linger too long — or not long enough.
Read guide →Send real-time geofence enter, exit, and dwell events straight to a Slack channel. No middleware, no polling — Fencemaker delivers geofence webhooks natively to Slack.
Read guide →