Keelway
Platform · Operations

Every truck on one map, refreshed every 30 seconds.

Most carrier TMSs treat fleet GPS as a partner feature you log into separately. Keelway treats it as a first-class platform module. Samsara feed in, live map out, with the same load, driver, and fuel data already in the platform overlaid on every pin. Click any truck to see who's driving, what load they're on, and when the engine last reported in.

30s
Position refresh cadence
Samsara stream + Keelway re-render
5
Status categories tracked
Total · Moving · Idle · Off · Stale
30 min
Stale threshold
Configurable on enterprise tenants
Live map

Every truck visible at once

The full fleet rendered on one map view. Pins colored by status. Pan and zoom. Filter by region, by driver, by current load. The dispatcher's morning truck check happens here, not in a separate Samsara tab.
Click to inspect

Full context on every pin

Unit number, assigned driver, current load (broker, lane, status), most recent Fleet One EFS fuel transaction, last ping timestamp, current speed and heading. The load card and driver record are one click away.
Status logic

Moving, Idle, Off, Stale

Engine on + speed > 5 mph = Moving. Engine on + ≤5 mph for 5+ minutes = Idle. Engine off = Off. No ping for 30+ minutes = Stale. Stale gets a desaturated pin so dropped connections are obvious.
Operations link

Fuel and load context overlaid

The same data model that powers the load tracking board and the fuel card module feeds the pin overlays. No second source of truth. Click a pin, see the load, jump to the invoice — same identifiers throughout.

Why the integration is first-class, not a partner add-on

Carriers running Samsara through a TMS partner integration spend half their day reconciling truck positions across two systems. The TMS says one thing; Samsara says another; dispatcher pulls up the third tab. Keelway runs the Samsara API natively, with the same load and driver identifiers across both data models. Pin tells you where; pin click tells you what; load card tells you why. One platform, one truth.

Frequently asked questions

How frequently does GPS refresh?+
Every 30 seconds. Samsara publishes positions on a continuous stream and Keelway's map view updates pins on that cadence. Manual refresh available; the auto-cadence is the default.
What does each pin show?+
Truck unit number, assigned driver, current load (with broker and lane), most recent fuel transaction, last ping timestamp, current speed and heading. Click-to-expand reveals the full load card and the driver record.
What is a stale truck?+
A truck whose last Samsara ping is older than 30 minutes. Stale status surfaces in the headline stats and on the map with a desaturated pin. The dispatcher knows immediately whether the issue is a dropped cellular connection or a parked truck.
What's the status breakdown?+
Five headline categories: Total trucks, Moving (engine on and speed > 5mph), Idle (engine on and speed ≤ 5mph for 5+ minutes), Off (engine off), Stale (no ping for 30+ minutes). The category counts update on every refresh.
Does fleet GPS require Samsara?+
Today, yes. Samsara is the day-one integration. Other ELD/GPS providers (Motive, Geotab, Verizon Connect) are on the integration roadmap; enterprise tenants on alternative ELDs should ask about the timeline before contract.
GPS in one tab, TMS in another?

One map. Every truck. Every load.

Talk to sales

Related

Live load tracking →

The load-level board that consumes the same Samsara feed.

Fuel card tracking →

Fleet One EFS data overlaid on every truck pin.

DOT compliance →

ELD-adjacent compliance that runs against the same truck records.