Operation plane · M15 · Tracking

Real-time fleet telemetry.

Tracking ingests GPS from every driver app, holds live fleet position and state for matching, drives the maps inside your apps and panels, and turns each trip into a real distance-and-time trace that feeds final pricing. The telemetry stays on your node.

See the dispatch engine Request a demo

What tracking does

From a GPS fix to a priced trip.

The same telemetry pipeline feeds three jobs at once — it keeps the dispatch index hot, paints the maps your riders and panels see, and records the trace that final pricing is built on.

High-frequency position ingestion. GPS streams in from every driver app and is built to tolerate intermittent connectivity — gaps are reconciled, not lost, when the signal returns.
In-memory geospatial index. Available drivers by zone and vehicle class — the dispatch engine's hot query — are kept in memory so a match resolves in about a second.
Live streams to apps and panels. The assigned driver's position streams to the passenger app, while the full fleet streams to operator panels — one telemetry source, two views.
Trip traces. Each trip records its route, real distance, and times — the trace that feeds final pricing and reporting, instead of a straight-line estimate.
Local geofences. Operating zones and fare zones are evaluated on the node; leaving the node's geofence is detected here — the event that will trigger cross-network routing.
Query
GET/api/v1/tracking/fleet
nodesf-yellow
zonedowntown
classcar
stateavailable
Run
Response
200 OK 22 ms
{
  "node": "sf-yellow",
  "zone": "downtown",
  "class": "car",
  "available": 14,
  "drivers": [
    {
      "id": "drv_44a",
      "lat": 37.7649,
      "lng": -122.4194,
      "speed_kmh": 28,
      "heading": 41,
      "fix_age_s": 1.2,
      "state": "on_trip"
    }
  ]
}

// Sample query/response. The fleet index and position API run on your node today; the response stays inside the node — it is never replicated to a central service.

One source, two views

The same telemetry on the rider's phone and the operator's wall.

The passenger sees just their driver closing in; the operator sees the whole fleet. Both are painted from the one stream of fixes the node already holds.

DriverClassStateFix ageSpeed
A. MoralesCarOn trip1.2 s28 km/h
K. IdrisMotoOn trip0.9 s34 km/h
L. RomeroCarAvailable1.5 s0 km/h
D. ParkShuttleBoarding2.1 s6 km/h
S. VanceVanReconnecting14 s—
J. LiuCarOffline——

A driver who drops signal shows as Reconnecting, not lost — their position is reconciled the moment the fix returns. Sample data.

Where the data lives

Traces never leave the node.

Telemetry is the most sensitive data your operation holds. Tracking is designed so it stays where it is generated — on your node — and only the events you choose to emit travel any further.

Privacy: traces never leave the node.

Position fixes, the in-memory fleet index, geofence evaluations, and full trip traces are computed and stored on the node that owns them. Tracking does not replicate raw location data to a central service. When the network plane arrives, what crosses a node boundary is a routing event — not the trace behind it.

LIVETracking events1 node
14:02:11position.fix · drv_44a · 1.2ssf-yellow
14:02:08geofence.enter · downtown · TRP-8841sf-yellow
14:02:01trace.update · TRP-8841 · 2.1 kmsf-yellow
14:01:54signal.gap · drv_s7 · reconnectingsf-yellow
14:01:46trace.closed · TRP-8839 · 4.8 kmsf-yellow
14:01:30geofence.exit · node boundary · roadmap—
On-node by default. Raw GPS, the fleet index, and trip traces stay on the node that generates them — there is no central location warehouse to breach.
Events, not raw streams. Other systems subscribe to the events tracking emits — a fix, a geofence crossing, a closed trace — instead of pulling the underlying location feed.
Boundary, not broadcast. Leaving the node's geofence emits a routing event for cross-network handoff. Cross-network routing is a network-plane capability — roadmap, not yet live.
The trace is the receipt. Because real distance and time live in the trace, final fares and reports are built on what actually happened — auditable on the node, not estimated.

// All figures and IDs are illustrative sample data. Position ingest, geofences, and traces are live on the node (M15); geofence.exit at the node boundary handing off to cross-network routing arrives with the network plane — roadmap.

Operation plane · M15

Telemetry that feeds the match and the fare.

Tracking is the live picture the dispatch engine matches against and the trace final pricing is built on. See how an order becomes an assignment in about a second.

See the dispatch engine Request a demo