FleetSQL pulls Wialon data into a database you own, so trips, fuel, driver scores and geofence events stop living behind a report builder and start answering SQL. It runs as a managed service on a schedule you set, and it ships white-label for partners who resell it under their own brand.
A real query against the extracted data, in a normal PostgreSQL client.
A dashboard built straight on the database — no export step in between.
Every claim below is published by the platform vendors themselves. Follow the links.
The default history period is 400 days, and messages older than it are automatically removed from the database. The period is extendable only by request to a Partner Success Manager, so a year-over-year comparison built later may have nothing to compare against.
help.wialon.com — account restrictionsAn online report gets five minutes of server time and a detalized report caps at 400,000 rows. When the limit is reached, execution is skipped and no results are returned — an absence rather than an error, which downstream systems record as a period with no activity.
sdk.wialon.com — limitationsWialon ships nothing that writes its data to a database. Fivetran, Stitch, Airbyte and Hevo all have zero Wialon connectors, and flespi's published downstream-integrations list contains no warehouse destination at all.
flespi.com — downstream integrationsGeotab bundles an official Data Connector for Power BI, Tableau and Excel free with its ProPlus and GO plans. Wialon has no equivalent, which makes this a gap in platform parity rather than an optional extra.
marketplace.geotab.com — Data ConnectorTelematics integrators and Wialon partners who need a data layer to sell alongside the platform, under their own brand and without building extraction and sync themselves.
Fleet owners large enough that reporting has become a data problem — where the questions have outgrown the report builder and the answers need to live in a warehouse next to ERP and finance data.
Unit properties, events, trips and report outputs extracted from Wialon and written into relational tables you can join against anything else you hold.
Isolation by default rather than a shared schema with a tenant column, so access control, backups and deletion are per customer.
Runs on a schedule you configure. Sync state is tracked per entity so an interrupted run resumes instead of starting over or duplicating rows.
It is a normal PostgreSQL database with normal credentials. Connect any client, any BI tool, any script — no proprietary query layer in between.
Initial extraction pulls history as deep as the account's Wialon retention period allows, which is why standing the mirror up early matters more than it looks.
Schema migrations, API changes on the Wialon side and failed-run recovery are ours to handle. You get a database, not a pipeline to operate.
Eco-driving scores, harsh braking and acceleration events, idle time — per driver and per trip, queryable rather than locked in a scorecard.
Fill-ups, drains and suspicious losses, each with volume and location, so a fuel investigation is a query instead of a week of manual report comparison.
Enter and exit timestamps, dwell time and zone names — the raw material for site-time analysis, customer SLA reporting and detention billing.
A read-only token is enough. We scope it to online tracking and view access rather than asking for account-wide control.
Choose the entities, parameters and units in scope. The schema is generated from that selection rather than from a fixed template.
Pick a sync cadence and how far back the initial extraction should reach, bounded by your account's Wialon retention period.
Credentials arrive and the database is live. Point a BI tool, a notebook or an application at it the same day.
FleetSQL ships white-label. Partners resell it as part of their own offering, and the end customer sees the partner's brand rather than ours.
Our Wialon API reference covers what this product handles for you. Useful whether you buy it or build it yourself.
As far as your Wialon account retains data, and no further — the platform is the only source. Wialon Hosting defaults to a 400-day history period and removes older messages automatically, though the period can be extended on request to a Partner Success Manager. This is the argument for starting the mirror before you need the history rather than after: once messages age out of Wialon, they are not recoverable from anywhere.
We handle it. Extraction, schema migrations and any adaptation to upstream changes are part of the managed service, which is the difference between this and writing your own sync job.
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.
Yes. Wialon Local is supported alongside Hosting; the extraction targets your server instead of the shared platform, and the retention question usually disappears because you control the history period yourself.
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.
Yes — that is what the white-label configuration exists for. Your brand and domain, your commercial relationship, your billing, with delivery and maintenance handled on our side.
Wialon meters message loading per user, and heavy requests are capped at three simultaneously per session, so a careless extractor can degrade the live interface for everyone on the account. Ours is paced against the published quotas and, where licensing allows, runs under its own account so it competes with nothing.
How FleetSQL began: a passion for telematics reports, years of customer feedback, and the path from one Python script to a full backend service.
Read moreAudit Wialon unit properties, sensors, hardware parameters, and eco-driving settings in Google Sheets with the open-source Wialon Auditor Apps Script.
Read moreA fleet organization moved from static report exports to SQL analytics with governed metrics and daily data quality checks.
Read moreHow a last-mile operator deployed a unified KPI dashboard to cut dispatch response time by 34% and improve route adherence by 18%.
Read moreHow a regional distributor stabilized Wialon to ERP sync and eliminated manual reconciliation for delivery operations.
Read moreHelping businesses to make their fleets safer, teams more productive and processes more efficient.