IoT fleet tracking doesn’t have to mean renting a dot on a map forever. Most commercial fleet tracking products charge per vehicle, per month, indefinitely. That model works fine for a company happy to rent visibility into its own fleet. It works less well for a company that wants to own the platform, customize how geofences trigger alerts, or serve fleet tracking as a feature inside its own product.
Folder IT built a real, open-source example of the alternative. It’s a real-time GPS tracking system running on infrastructure a company actually owns. In practice, the system ingests live GPS positions from ordinary phones, renders them on a multi-tenant map, and fires geofence events — all on top of Losant and Traccar, not a commercial fleet tracking SaaS. As a result, the full build is public on GitHub.
Why Off-the-Shelf IoT Fleet Tracking Falls Short
Commercial fleet tracking platforms solve the basic problem well: a dot on a map, updated in real time. However, what they solve less well is everything past that. For instance, custom geofence logic and white-labeling for a company’s own customers usually means working around the vendor’s platform. So does integrating fleet data into an existing product.
Cost also compounds the issue. Per-vehicle SaaS pricing scales linearly with fleet size. So a company tracking 500 vehicles pays 500 times the per-unit rate, indefinitely. By contrast, a real-time GPS tracking system built on owned infrastructure has a different cost curve. Losant charges by device and data volume instead of a marked-up per-vehicle SaaS fee. As a result, every part of the logic — geofence rules, event types, tenant isolation — stays fully customizable.
How This Build Handles Multi-Tenancy
The core design decision treats an Experience Group in Losant as an organization. Specifically, every device, geofence, and event carries an organizationId tag. Every API endpoint also scopes its query to the signed-in user’s own group. That way, one multi-tenant IoT platform supports many isolated fleets, with no cross-tenant data leakage by design.
Devices don’t get created by hand, either. Instead, the first time a phone reports through Traccar, Losant creates the matching device from a shared template. That template defines four attributes: location, speed, heading, and battery level. So every tracked device carries the same shape of data, no matter which organization owns it.
From Phone to Map: The Real-Time Data Path
The architecture stays deliberately simple: four parts, one direction of data flow. First, a phone running the Traccar Client app reports its position to a public Traccar server. Then, Losant holds a live connection to that server and receives every new position as it arrives. Next, a workflow matches the position to the right device, updates its state, and checks it against any active geofences. Finally, the Fleet Map page polls Losant’s experience endpoints. Those endpoints return only the devices that belong to the signed-in user’s organization.
This is real Losant IoT development, not a mock demo layered on top of fixed data. For testing without a physical phone, a route simulator script ships in the repo. In addition, the Fleet Map page has a ?demo=1 mode. That mode runs the entire interface in the browser with no backend at all — useful for checking the UI before wiring up real devices.
When Custom IoT Development Makes Sense
Not every fleet tracking need justifies a custom build. Instead, the decision mostly comes down to how much a company plans to extend or resell the platform.
An off-the-shelf tracker holds up well for a company that just needs visibility into its own vehicles. It fits best with no need to customize the interface or resell it to customers. In that case, cost stays predictable at small fleet sizes, and there’s no infrastructure to maintain.
On the other hand, the case for working with an IoT development company gets stronger in a few situations. For example, a company may need white-labeled tracking inside its own product. Or it may need custom geofence logic tied to its own business rules. Or it may want a cost structure that doesn’t scale linearly with fleet size. Likewise, multi-tenancy from day one — the way this repo handles it — matters for any company planning to serve more than one customer organization from a single deployment.
Frequently Asked Questions
What is IoT fleet tracking? IoT fleet tracking uses connected devices — typically GPS-enabled phones or hardware trackers — to report vehicle or asset locations in real time to a platform that displays them on a live map, tracks routes, and triggers alerts based on rules like geofences.
How does multi-tenancy work in this build? Every device, geofence, and event carries an organization ID. Every API call an organization’s users make returns only their own data, scoped through their Losant Experience Group membership.
Can this run without physical GPS devices? Yes. The Fleet Map page includes a demo mode that simulates a fleet, geofences, and events entirely in the browser, and a route simulator script can drive a real Losant device along a predefined path for testing.
What does Losant do versus Traccar in this architecture? Traccar handles GPS ingestion from the phone — it’s the entry point for raw location data. Losant handles everything after that: device state, workflow logic, geofence evaluation, data storage, and the multi-tenant experience layer that renders the map.
Is this repository production-ready? No. It’s a versioned reference example meant to document the approach and let a technical evaluator reproduce it, not a maintained production dependency.
A Different Way to Own Fleet Visibility
IoT fleet tracking doesn’t have to mean a growing per-vehicle SaaS bill and a platform a company can’t fully customize. This build shows the alternative end to end — real GPS ingestion, real multi-tenancy, real geofence logic — running on infrastructure a company actually controls.
Folder IT builds IoT systems and platform integrations for enterprises that need more control than an off-the-shelf SaaS tool allows. The same proof-over-claims approach runs through Folder IT’s AI development work — real, verifiable builds instead of marketing claims. Get in touch to scope what a custom IoT build would look like for a specific fleet or asset-tracking use case.
