Flespi + FleetERP
Protocol-normalisation gateway for long-tail and unusual devices.
How it works
For device models FleetERP has not yet implemented natively, Flespi acts as a universal translator. We consume its normalised message stream over MQTT, which means an obscure tracker in one depot never blocks a rollout.
Flespi MQTT stream and REST API with token authentication.
FleetERP has no commercial relationship with hardware vendors and earns nothing on devices. If you later switch away from Flespi, your history, reports and workflows stay exactly where they are.
What flows across
What Flespi data lights up in FleetERP
Integration data is not stored in a separate silo — it feeds directly into the operational modules that use it.
Flespi integration FAQ
Do we need to replace our Flespi setup to use FleetERP?
No. FleetERP is device-agnostic and does not sell hardware. Your existing Flespi deployment stays exactly as it is — flespi MQTT stream and REST API with token authentication.
What data does FleetERP receive from Flespi?
Normalised telemetry from 1,000+ device models; Device registry and channel health; Calculated intervals and trips.
How long does the Flespi integration take to set up?
Standard integrations are connected during week three of a normal 30-day rollout, alongside device onboarding. Most take a few hours of configuration rather than a project.
Telematics platforms & maps
Already running a tracking platform? Keep it. FleetERP layers the ERP on top instead of replacing it.
Already running Flespi? You're most of the way there.
Book a demo and we will show you your own device data flowing into the platform during the call.
No per-user pricing · No hardware to buy · Deploy on your VPS or ours
Prefer to write? sales@fleeterp.in