Your 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.

The FleetSQL console: completed extraction runs with their unit and row counts, the fleets it runs for, and one fleet's Postgres host, database and credentials

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.

  • Managed for you

    Schema migrations, Wialon API changes and failed runs are ours, not your team's.

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

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.

Related

Let's connect

  • “Our client needed a data pipeline. It came back working, plus a few Wialon fixes we had not asked for. That client trusts us more now.”
    Faiz K. Customer Manager · Trakpro Limited