- Every reading has to reach the cloud before anything happens
- A dead zone means a gap in the record
- Bandwidth use scales with raw data volume
EDGE COMPUTING
Why some decisions happen on the device, not in the cloud.
Edge computing means processing data where it's generated — on the Tracker device or a custom sensor — instead of waiting for a round trip to the cloud. It supports Tracker and Custom IoT devices; it is not a separate product.
What processing at the edge enables
Faster local decisions
A harsh-event or fault signal can be evaluated on-device in the moment it happens, rather than after an upload completes.
Offline resilience
Devices continue capturing and evaluating signals during a connectivity gap, buffering data until the connection returns.
Efficient sync
Only the meaningful, filtered result needs to be sent — reducing bandwidth and keeping data costs predictable.
Cloud-only vs. edge-aware
- Time-sensitive signals are evaluated immediately, on-device
- Data is buffered locally and synced once connectivity returns
- Only the relevant, filtered result needs to be transmitted
How this supports Tracker and Custom IoT
Tracker
Buffers up to 72 hours of data offline and evaluates harsh-event and fault signals locally before they reach FleetOps.
Custom IoT devices
Purpose-built sensors can include the same on-device processing when a specialized requirement calls for it.
See it in the hardware itself.
Tracker ships with this built in — or we can build it around your requirement.