Developers
Built by developers, for developers.
If you're integrating Wialon, building on top of telematics protocols, or looking for solid map and geo utilities, we have a few ways to help.
Service
Paid consult slot. We've shipped Wialon integrations across 19 markets — auth, units, sensors, messages, reports, geofences, custom commands. Skip the SDK trial-and-error.
Get in touch →
Sister project
Geo and map utilities for developers. Reverse geocoding, custom tiles, distance calculation, route APIs. Spun out of work we do internally for fleet platforms.
Visit mapsfordevs.com →
Protocols & hardware
What we work with.
Custom binary protocol parser. CRC-16 Modbus, TLV tags, multi-segment TCP framing.
Codec 8 / 8E AVL parser. We've mapped the IO element catalogue end-to-end, including the long-tail (panic, ICCID, crash).
Full SDK integration — login, search items, messages, reports, sensors, custom commands, admin fields, geofences.
On-vehicle MDVR + terrestrial cameras. Digest auth, event subscription, live preview, clip retrieval.
Edge-deployed APIs and form handlers. We host this site on Cloudflare Pages.
Time-series storage for GPS messages, sensor reads, events. Hypertables, continuous aggregates, retention policies.
Questions
Common questions from devs.
Do you publish a public API?
Per-tenant APIs are issued on request. We don't publish a generic public API — most integrations are point-to-point and we scope auth and rate limits to your usage.
Can you help us migrate off Wialon?
Yes. We can either wrap Wialon (white-label it under your brand) or migrate you onto the DataPortal stack — units, drivers, geofences, history. We've done both.
Do you do paid consulting on telematics protocol work?
Yes — get in touch via the form and tell us what you're wrestling with.
Is MapsForDevs a separate company?
Separate project, same team. It's open dev tools spun out of internal work.
Have a tricky integration on your hands?
Tell us what protocol or platform you're working with. We come back within one working day.