.svg){kind=small}
One parser layer brings dozens of GPS tracker brands into Levy.
Most GPS tracker OEMs speak raw TCP or UDP protocols. flespi normalizes those devices into a single API and MQTT stream, and Levy is wired into it — so a tracker brand Levy has never seen before can be live on the fleet map without writing a new listener.
Map
Levy workflow
Alerts
Levy workflow
Recovery
Levy workflow
How it works with Levy
flespi on a tracker-agnostic Levy stack
flespi is the foundation of Levy's tracker-agnostic layer: when a prospect already owns unknown tracker hardware, Levy can light it up through the protocol flespi already parses instead of building per-vendor ingestion.
Multi-vendor tracker support
OEM tracker pilots
Fast protocol onboarding
Hardware at a glance
GPS tracker protocol middleware specifications
The device details Levy maps into the fleet — so operators know exactly how flespi hardware behaves before it ships.
Parses 150+ tracker brands into one JSON schema
REST API + MQTT + webhooks out of the box
One Levy integration covers Teltonika, Queclink, Concox, Ruptela, Meitrack and more
New tracker brand support becomes config, not engineering
| Power model | N/A — cloud middleware, no device of its own |
|---|---|
| Install | No hardware; point tracker traffic at a flespi channel |
| Connectivity | Ingests device TCP/UDP; outputs REST API + MQTT + webhooks |
| Battery life | N/A |
| Update interval | Inherits the source device's reporting cadence |
| Security | Passes through device geofence, movement, and alert events |
| Coverage | 1,000+ device models across 150+ tracker protocols |
| Pricing | Usage-based per active device/message |
Integration motion
Turn tracker data into fleet operations
How the integration works
A flespi channel ingests the selected tracker protocols.
Normalized telemetry forwards into Levy IoT device records.
Levy adds per-device mapping, freshness, battery, movement, and alert handling.
Why operators run it on Levy
Removes per-vendor protocol work across the tracker catalog.
Makes white-label tracker sourcing low-risk.
Gives sales a credible answer when prospects already own unknown hardware.
Good to know
Questions
flespi GPS tracker protocol middleware + Levy FAQ
Which trackers does this cover?
flespi parses 150+ protocols including Teltonika, Queclink, Concox/Jimi, Ruptela, Meitrack, Suntech, Eelink, and Topflytech — all surfaced into Levy through one integration.
What does Levy receive from flespi?
Normalized JSON over REST and MQTT — position, battery, movement, and alert events — mapped straight into Levy IoT device records.
Do I need to know my tracker's protocol?
No. If flespi already supports the device, Levy can onboard it without per-vendor protocol work on your side.
Keep exploring
More supported tracker integrations
Bosch eBike
Native Bosch e-bike location and anti-theft data, live on the Levy map for premium rental fleets.
Open pagePowUnity
Motor-integrated e-bike GPS for Bosch, Yamaha, Shimano, and other premium drives — live on the Levy map.
Open pageTeltonika
Self-powered, no-splice Teltonika asset trackers for recovery on bikes, carts, trailers, and equipment.
Open pageConnect your trackers to Levy
Tell us what tracker hardware your fleet runs and we will get it onto your Levy map and recovery workflows.