fleetstracker pulls your Samsara GPS, TrackFleet reefer data and Alvys loads into a single operations board — then tells you about the drifting trailer or the missed appointment while you can still do something about it.
Read-only API keys · No TMS migration · Your brokers need no login
The data already exists — it's just scattered across your telematics, your reefer portal and your TMS. So nobody sees the problem until it's a claim or an angry phone call.
Every broker wants a check call. Dispatch burns hours retyping the same location and ETA into email threads instead of moving freight.
A setpoint drifts overnight. Nobody's watching the portal at 3am. The first time anyone notices is when the load gets rejected — and a rejected reefer load is the most expensive email you'll ever read.
By the time a truck is visibly behind, the appointment is already gone. Nobody had a number that said "this one is going to be tight" four hours earlier.
A stack of vendor PDFs, hand-keyed into maintenance software line by line, with the totals never quite matching.
fleetstracker sits on top of the tools you already run. Nothing to install in the cab, no new hardware, and your TMS stays exactly where it is.
Add your Samsara, TrackFleet and Alvys API keys once, in the app. They're encrypted with a cloud KMS the moment they arrive, never shown again, and revocable in a click.
Every truck with a driver appears automatically: position, miles left, ETA, stage, setpoint versus actual temperature, and a plain-English status line — refreshed on every sync and pushed straight to the screen.
Turn on updates for a trip and your broker gets threaded email replies as the load moves. Reefer drift and late appointments page your team by email on their own.
Running below with sample trucks. Watch unit 4412 — its trailer is drifting out of range, and you'll see exactly what your team would see.
| Truck | Driver | Trip | Status | Status note | Req °F | Set | Act |
|---|
fleetstracker checks the return air temperature against the setpoint on every trailer, every sync, all night. Drift past 6°F and your team hears about it.
Setpoint from the reefer, the return air temperature it's really holding, and the load's required range from your TMS — all on one row.
Every unit currently out of range goes into a single email with its required range, setpoint, actual and deviation — repeating on a set interval while it stays out, not once per sync.
Dry loads simply show "DRY LOAD" instead of firing false alarms — the board stays quiet so real alerts get noticed.
Your customer sees the maintained temperature in the same email that tells them where the truck is. Proof, unprompted.
Turn updates on for a trip and fleetstracker replies straight into the existing email thread your broker started — same subject, same recipients, threaded underneath the rate confirmation. They don't sign up for anything.
Pick the interval. Updates run from arrival at the shipper through the delivery, then stop on their own.
Every trip starts with updates off. One toggle on the board arms the loads you actually want narrated.
Arrived at the shipper, miles out and rolling, maintained temperature, arrived at the receiver. No dashboards to click, no tracking links to install.
Position, movement, miles left, ETA and stage for every truck with a driver — updated on every sync and pushed live to the browser.
Return air measured against setpoint every sync. Drift past 6°F and the unit lands in one grouped email, with the load's required range shown alongside.
Every load is scored against its next appointment — on time, tight, or late — and colour-coded so the problem row finds you.
Threaded email replies into the broker's own chain, per trip, with position and maintained temperature. No portal for them to learn.
Harsh braking, acceleration, cornering and speeding events from the last 24 hours surface as a warning beside the driver's name.
Where and when each truck frees up, in one compact list you can copy straight into an email to brokers looking for capacity.
Drop in vendor repair PDFs and AI reads them into Fleetio work orders — reconciled to the cent, reviewed by you before anything is written.
Owner, admin, dispatcher and viewer. Invite by email, they set their own password, and integrations stay locked to the owner.
The full board on a handset as tap-through cards, so the answer is the same whether you're at the desk or in the yard.
Provider keys are envelope-encrypted with a cloud KMS on arrival. The API is write-only — once saved, a key can be rotated or revoked, never read back.
Every record carries its company, enforced both in the application and by row-level security in the database itself.
Samsara, TrackFleet and Alvys are read-only. Nothing is pushed back into your TMS. Work orders are the one exception, and only after you approve each one.
We keep one current snapshot per truck, not a history archive, and secrets are stripped from every log line.
Fleets differ — how many trucks, which integrations, how much of the automation you want switched on. Rather than guess at a number on a web page, we'll walk your board with you and quote it properly.
A screen-share on your actual fleet data, not a canned deck.
Read-only keys, and you can revoke them the second the call ends.
You'll leave the call with a per-truck price for your fleet size.
No. fleetstracker reads from Alvys and never writes back to it. Your dispatchers keep booking and billing exactly where they do today — this is the operational view on top, not a migration.
GPS, reefer and TMS are pluggable interfaces rather than hardcoded vendors, so additional providers are an adapter, not a rebuild. Tell us what you run on the call and we'll tell you honestly whether it's ready today or a short piece of work.
A sync cycle runs on a schedule — every 15 minutes by default — and the moment new data lands it's pushed to any open board without a refresh. You can also force a sync from the screen whenever you want to see right now.
They're encrypted with a cloud KMS the moment they arrive and stored only as ciphertext with a wrapped key. The credential API is write-only, so nothing — not the browser, not our logs, not support — can read a key back out. Rotate or revoke at any time from settings.
Never. Updates arrive as ordinary email replies inside the thread they already started with you. There's no portal, no login, and no tracking link for them to click.
Each integration is isolated behind its own circuit breaker, so a failing reefer API doesn't stop GPS or loads from updating — and one company's expired key never affects anybody else. Sync health is visible so you know what's stale rather than guessing.
The connection itself is minutes — paste three read-only keys and the roster populates on the first sync. Most of an onboarding call is spent deciding who should receive which alerts.
Fifteen minutes, your trucks, your loads. If it doesn't tell you something you didn't already know, we'll have wasted a quarter of an hour and nothing else.
Read-only access · No install · Cancel anytime