Pricing

What the price depends on, before you ask for one

We do not publish a per-vehicle number, because it would not answer your question: a 40-vehicle fleet pulling one daily table and a 900-vehicle multi-client integrator pulling events with three years of history are different products. Here is what the quote is actually built from, so you can size it yourself first.

Priced on
Fleet size and scope
Includes
Hosting, sync, backfill
Quote
Within 24 hours
Exit
Full export, no lock-in

The four things that move the number

Every quote is built from the same four inputs, and each of them is something you already know about your own fleet.

  • Units under sync — how many vehicles land in the database, which sets both API cost and storage.
  • What you extract — the daily table alone is the cheapest configuration; fuel events and eco-driving violations add rows and API calls.
  • History depth — a three-year backfill is a one-off cost in extraction time; how much you keep afterwards is an ongoing one.
  • Databases — one per client. An integrator serving eight customers is running eight isolated databases, not one with a tenant column.

What is included rather than billed separately

Hosting and management of the PostgreSQL database, the scheduled sync, the initial backfill, credentials for your tools, and support in English or Polish. There is no separate onboarding fee and no charge for connecting a BI tool — it is a connection string, and charging for one would be odd.

What sits outside the subscription is custom work: bespoke transformations, joins into your ERP, dashboards built for you. That is an Asset Track engagement rather than a product tier, priced as a project so it can be scoped honestly.

Where the cost lands compared with the alternative

The comparison worth making is not against another SaaS subscription but against what you do today. A recurring export-and-reshape cycle typically consumes a few working days a month in a fleet of a few hundred vehicles, and the output is not reproducible. Building the same pipeline in-house is a straightforward but real engineering project — API limits, retries, idempotency, timezone handling, backfill, monitoring — and then it needs an owner for as long as it runs.

That is the honest frame: this is worth paying for when the export cycle is costing you real hours or real trust, and not before. FleetSQL versus Wialon reports sets out where that line falls.

What to send for a quote

Four lines is enough for a concrete answer within 24 hours, and none of them require a call first.

  • Number of units, and whether they belong to one fleet or several clients
  • What you want extracted — daily telemetry only, or fuel and eco-driving events as well
  • How much history you want backfilled, and how long you need it kept
  • Which tools will connect: a BI tool, notebooks, an agent, your own application

Leaving

The data is in your database in standard PostgreSQL tables, so leaving means taking a dump of it — no export request, no proprietary format, no period during which access is withdrawn while a ticket is processed. Deletion on request drops the database rather than flagging rows, and is confirmed in writing for your own GDPR records.

Saying this on the pricing page is deliberate. The entire premise of the product is that data locked inside somebody else's interface is a liability, and it would be a poor joke to solve that by locking it inside ours.

Frequently asked questions

Why is there no public price list? +

Because the same subscription covers a 40-vehicle fleet pulling one table and an integrator running eight client databases with three years of history each. A single published number would be wrong for both. The four inputs above are what the quote is built from, and a quote takes a day.

Is there a minimum fleet size? +

Not a hard one, but there is a point below which the maths does not work in your favour. If nobody in your organisation is exporting Wialon reports on a schedule today, the honest answer is that you do not need this yet.

Is the backfill charged separately? +

No, the initial history load is part of getting started. It is worth running early regardless of commercial timing: Wialon retention decides how much history exists to load, and what has already aged out cannot be recovered later.

What happens to the database if we stop? +

You take a standard PostgreSQL dump before the end of the term — plain tables, no proprietary format. On request the database is dropped rather than retained, and confirmed in writing so your own GDPR records are complete.

Can we trial it on part of the fleet? +

Yes, and it is the usual way in. A subset of units with the full configuration shows you your own data rather than a demo account, and answers the only question that matters before signing: whether the queries you need are answerable from these tables.

Worth reading

Why and how to extract your Wialon fleet data

Four reasons to get telematics data out of Wialon — and three ways to do it: by hand, a custom ETL pipeline, or FleetSQL straight to PostgreSQL.

Contact

Interested in FleetSQL?

Why FleetSQL

Your Telematics data in a PostgreSQL database you control — queryable, joinable, and yours.