Litres per 100 km, by vehicle class, by quarter
Trips and fuel events sit in the same database, so the metric is defined once and re-run by anyone who needs it.
Your Wialon data. Your PostgreSQL.
The problem
The number your board sees is made by hand.
Someone exports a Wialon report to CSV, reshapes it in a spreadsheet and sends it on. It works — until the follow-up question arrives, until two versions of the number disagree, or until the history it needs has aged out of the platform.
Today
Wialon report
run by hand
CSV export
one period
Spreadsheet
reshape, VLOOKUP
The chart
emailed on
With a copy
PostgreSQL
history already there
One query
in version control
The chart
refreshed by the tool
-
400 days
Wialon Hosting's default retention
What ages out of the platform cannot be recovered later, by any tool.
-
5 min · 400k rows
The budget one report run gets
Past either limit the run comes back empty rather than failing loudly.
-
No connector
Fivetran, Stitch, Airbyte, Hevo
None of them carry a Wialon source. A copy is built, or bought.
What changes
Questions that stop needing an export.
FleetSQL keeps a PostgreSQL database in sync with your Wialon account — trips, speedings, fuel events, sensors, vehicle properties and your own report templates. Nothing is written back to Wialon, and your dispatchers see exactly what they saw before.
Cost per delivery, per customer
Your contracts and cost centres live in tables beside the telemetry. This is the join a reporting screen cannot do at any price.
Which trucks idled more than three hours yesterday
The rule is a query on a schedule: reviewable, kept in version control, and testable against last year before you trust it.
The same metric, the same definition, since 2023
History outlives the platform's retention window, because it was copied out before it aged.
How it works
From a token to a connection string.
Setup is an afternoon, not a project: nothing to install, nothing to host, and nothing added inside Wialon. Four steps, all of them in one console.
- 01
Connect
A Wialon API token you generate
Read-only, verified on entry, revocable in a click.
- 02
Choose
Properties, events, your reports
Only the sources you will actually query.
- 03
Backfill
3 years, then every 15 min
Every run recorded, a failed one re-run.
- 04
Query
A PostgreSQL connection string
Power BI, Grafana, psql — whatever you already run.
What setup ends with
Four lines, and from there it is a PostgreSQL database like any other — no FleetSQL SDK to install, no query language to learn, no part of your stack that has to know FleetSQL exists. Access is per person, read-only, and revocable on its own.
The same four steps, screen by screen →The connection you are handed
- Host
- pg.fleetsql.app
- Database
- fs_meridian_continental
- User
- fs_meridian_continental_user
- SSL
- required
The same four lines are what Power BI, Metabase, Grafana, Tableau, DBeaver, psql and pandas each ask for.
Dashboards
Your dashboards, in the tool you already report in.
The board below is Grafana, because that is the one we can show you running. The database does not know which tool is asking: Power BI, Metabase, Tableau and Excel connect to the same host with the PostgreSQL connector they already ship, and every number is a SQL query rather than an export somebody refreshes by hand.
Power BI
Get Data → PostgreSQL database
Host and database from the console. Import pulls the tables into the model; DirectQuery leaves the history in Postgres and pushes each visual down to it.
Metabase / Superset
Add database → PostgreSQL
Self-service questions for the people who will not write SQL, over the same tables your analysts query.
Tableau / Looker Studio
Connect → PostgreSQL
A live connection or an extract, whichever the team already runs. Nothing about it is specific to fleet data.
Grafana
Add data source → PostgreSQL
The board above, plus threshold alerting off the same queries — a drain over 20 litres becomes a notification.
The same connection string also serves psql, DBeaver, pandas, n8n and an LLM agent — what connects and how.
See it on your own fleet before you decide.
We set up a trial database on your Wialon account, backfilled with your own history. You look at your own numbers rather than a demo's.
What the price depends on → Two products
The same idea, against two platforms.
Both take a telematics platform you do not own and put its data in a database you do. Which one you want depends on where your devices already send their messages.
FleetSQL Wialon → PostgreSQL
Trips, speedings, fuel and charging events, vehicle properties, sensors and your own report templates, extracted through the Wialon API into one PostgreSQL database per client. Managed: the schedule, the schema migrations and the upstream API changes are ours.
- Store
- PostgreSQL, one database per client
- Reads
- Wialon Hosting, over the API, read-only
- Cadence
- From every 15 minutes to nightly
- First run
- Backfills up to three years
flespi backup flespi → ClickHouse
Every message flespi normalises, mirrored into self-hosted ClickHouse you run where you choose. Real-time over MQTT with a disk spool that fsyncs before it acknowledges, plus a reconciler that heals any gap by REST backfill and writes down what it could not heal.
- Store
- ClickHouse, self-hosted
- Reads
- flespi channels over MQTT 5 and REST
- Cadence
- Continuous — seconds, not schedules
- Measured
- ~1,470 devices, ~1,400 msg/min at peak
Questions
The things people ask before signing.
Anything else, ask us directly — the form is at the bottom of this page.
Does it replace Wialon? +
No. Wialon stays the operational system: live positions, alerts, dispatch. FleetSQL is a queryable copy for analysis, synced on the cadence you set — as often as every 15 minutes. The routing rule is simple: happening now goes to Wialon, happened before goes to SQL.
How much history do we get? +
The first run backfills up to three years, bounded by what your Wialon deployment still retains. Whatever has already aged out of the source cannot be recovered later by any tool, which is why the first extraction is worth running early.
Is our data separated from other clients? +
Every client gets a separate PostgreSQL database rather than a shared table with a tenant column, so a query written for one client cannot return another's rows. Databases are EU-hosted and encrypted at rest and in transit.
What do we need to connect a BI tool? +
A connection string. It is a standard PostgreSQL database, so Power BI, Metabase, Grafana, Tableau, DBeaver, pandas and every ORM connect with the driver they already ship — Power BI reaches it through Get Data → PostgreSQL database, in Import or DirectQuery. There is no FleetSQL SDK to install.
Do you do the same thing for flespi? +
Yes, as a separate product. flespi backup mirrors every message flespi normalises into self-hosted ClickHouse — real-time over MQTT with a disk spool that fsyncs before it acknowledges, and a reconciler that heals gaps by REST backfill. It is described at /flespi-backup/ on this site.
Who is this not for? +
Fleets whose questions are fully answered by Wialon's built-in reports. If nobody in your organisation is exporting a report to CSV on a schedule, a database is overhead bought for nothing — and we would rather say so before an invoice than after one.
Contact
Interested in FleetSQL?
Why FleetSQL
Your telematics data in a PostgreSQL database you control — queryable, joinable, and yours.
- Managed, not installed
- We run the extraction and the database. You get a connection string.
- One database per client
- Your own PostgreSQL, hosted in the EU, TLS required.
- Your tools, unchanged
- Power BI, Grafana, Metabase, psql, pandas — anything that speaks Postgres.
- An evaluation first
- A trial database on your own fleet before anything is signed.
Or write to us directly: [email protected]