FleetSQL 
FleetTAB 
Ecodriving 
Maintenance 
Fleet Config 
Logbook 
Utilization 
Merger 
RoutlyWialon Reporting Limitations and SQL-First Analytics
When built-in Wialon reports fall short, SQL-first analytics unlocks custom dimensions, historical comparisons, and governed metric definitions.
Read moreYour Wialon data. Your PostgreSQL.
A managed service that mirrors your Wialon account into a PostgreSQL database you own — trips, fuel, driver scores and geofence events, answering SQL and joinable against the ERP and finance data already sitting next to it. Where the fleet is on flespi rather than Wialon, the same service mirrors every message flespi normalises into a self-hosted ClickHouse instead — continuously, over MQTT, rather than on a schedule.
One product, two platforms
Which half you want follows from where the devices already are, and for an integrator running both it is often both. The idea does not change: the platform keeps doing ingestion and normalisation, the history moves into a database you own.
Wialon FleetSQL
Wialon → PostgreSQL
Read through the Wialon API on the schedule you set, landing reporting-shaped tables — trips, fuel and charging events, driver scores, unit properties, sensors and your own report templates — in one managed PostgreSQL database per client.
- Store
- PostgreSQL, one database per client
- Reads
- Wialon Hosting, over the API, read-only
- Cadence
- From every 15 minutes to nightly
- Hosting
- Managed by us, EU-hosted
flespi flespi backup
flespi → ClickHouse
Every message flespi normalises, mirrored into a ClickHouse you host yourself. MQTT 5 with each message fsynced to disk before it is acknowledged, and a reconciler that heals any gap by REST backfill and writes down what it could not heal.
- Store
- ClickHouse, self-hosted
- Reads
- flespi channels, MQTT 5 and REST
- Cadence
- Continuous — seconds, not schedules
- Measured
- ~1,470 devices, ~1,400 msg/min at peak
What it fixes
History has a horizon
Wialon Hosting keeps 400 days by default and removes the rest, so a year-over-year comparison built later finds nothing to compare.
Reports run to a budget, quietly
Five minutes of server time, 400,000 rows. Past either the run is skipped and no rows come back — which downstream reads as a quiet week.
There is no switch to flip
Fivetran, Stitch, Airbyte and Hevo carry no Wialon connector. A database copy is something you build or buy.
What it does
50+ data points
Unit properties, events, trips and report outputs, in relational tables.
One database per client
Isolated rather than a shared schema, so access, backups and deletion are per customer.
Daily automatic sync
On the schedule you set, resumable per entity after an interrupted run.
Full SQL access
Normal Postgres credentials: Power BI, Metabase, Grafana, Tableau, pandas, n8n.
Historical backfill
The first run reaches as deep as your Wialon retention period allows.
flespi as well as Wialon
The same mirror against flespi: every normalised message into self-hosted ClickHouse, continuous over MQTT rather than scheduled.
What it costs
One figure, sized against the account it will run on and quoted on the free call — and resold under your brand where you want it.
Managed service
Quoted
Priced on the free call, against the account it will run on. A 40-vehicle fleet mirrored once a day and a 4,000-vehicle fleet mirrored every hour are not the same service, so there is no list price to print — but there is a figure by the end of the call, and it does not move afterwards.
Ask what yours would cost- The size of the account: units, drivers and how many entities the sync touches
- How often it runs — daily is the default, more often is a decision
- How deep the first backfill reaches, up to whatever Wialon still retains
- Whether it ships under your own brand, for your own customers
- On flespi, message volume rather than unit count — and the ClickHouse you host
The mechanics, written out
FAQ
How far back can the initial backfill reach?
As far as your Wialon account retains data, since the platform is the only source. Wialon Hosting defaults to a 400-day history period and removes older messages automatically, and the period can be extended on request to a Partner Success Manager. It is worth standing the mirror up before you need the history rather than after: once messages age out, they are not recoverable from anywhere.
What happens when Wialon changes its API?
We handle it. Extraction, schema migrations and adaptation to upstream changes are part of the managed service rather than work that lands on your team.
What happens to the sync after an outage?
Sync state is tracked per entity, so an interrupted run resumes from where it stopped rather than restarting or duplicating rows. Gaps caused by a longer outage are backfilled on the next successful run.
Who owns the database?
You do. It is a normal PostgreSQL database with normal credentials, and the data in it is yours. If the service ends, the database and its contents go with you rather than being switched off.
Can we resell FleetSQL to our own customers?
Yes, that is what the white-label configuration is for. Your brand and domain, your commercial relationship and your billing, with delivery and maintenance handled on our side.
Will extraction slow down our Wialon account?
Wialon meters message loading per user and caps heavy requests at three at a time per session, so an unpaced extractor competes with the live interface. Ours is paced against the published quotas and, where licensing allows, runs under its own account so it competes with nothing.
Does this only work with Wialon, or does flespi count too?
flespi counts, and it is the second half of the product. Wialon is read through its API on a schedule and lands reporting-shaped tables in a managed PostgreSQL database. flespi is consumed continuously over MQTT 5, with every message written to disk before it is acknowledged, and lands in a ClickHouse cluster you host yourself — your region, your retention, your hardware. The flespi side runs today against about 1,470 devices at roughly 1,400 messages a minute in the peak hour. Which half you want follows from where the devices already are, and for an integrator the answer is often both.
Related
Wialon to PostgreSQL Pipeline: Production Blueprint
Build a reliable Wialon to PostgreSQL pipeline: immutable staging, schema governance, validation checks, replay-safe backfill. 50+ tables, daily sync.
Read moreWialon Sensors From Systems Wialon Cannot See
Message Merger writes probe, weighbridge or ERP readings onto a Wialon unit that keeps its tracker, so they become sensors, report columns and alerts.
Read more
