ESTalk to our team

Know the moment a vehicle enters or leaves a zone.

Positions come in. Zone transitions go out, as signed webhooks to your systems and live updates in a console. One backend for many customers.

Service territory
Sample data

From position to event

Service territory
Sample data
Approval flow
Sample data
Observability
Web service
Database
Queues
  1. Over REST or Phoenix Channels, into sharded ingest.

  2. H3 cell-set membership in a Rust NIF decides whether it crossed a zone edge.

  3. The transition is recorded in an outbox first, then delivered as a webhook signed with HMAC-SHA256.

For products that react to where things are

Zones as you draw them

Circle, polygon and temporal geofences on a live map.

Events you can trust

Retried up to eight times, with a circuit breaker and a dead-letter queue.

Many customers, one backend

Multi-tenant, with roles and API keys scoped to each tenant.

History you can replay

Trajectories and events on TimescaleDB, replayed and exported as CSV.

Events go where your work happens

Your dispatch, CRM or customer app gets the event the moment the line is crossed.

Under the hood

  • REST API with OpenAPI 3.1
  • Clustering, Prometheus metrics and OpenTelemetry traces
  • Trips and driver leases
  • TypeScript SDK

What should happen when something crosses the line?

We’ll show it to you working, using the product and its demo materials, and talk through your case.

Ask for a demo