Wialon reports are not the problem. Their ceiling is.

This is not a replacement. Wialon stays the system of record for operations and keeps every real-time workflow: positions, alerts, dispatch. The database answers the questions that need history, arbitrary grouping, or data Wialon does not hold.

There is a simple test, and it is not about fleet size. Does someone in your organisation export a Wialon report to CSV on a schedule, reshape it in a spreadsheet, and send the result to someone else? If not, you do not need this product. If yes, count the hours that cycle takes in a year — that number is the entire business case, and it usually surprises people.

The second cost of that cycle is not time but trust. Because the transformation lives in one person's workbook, two versions of the same number disagree, nobody can reproduce last quarter's figure, and the analysis stops being evidence. A query in version control does not have that failure mode.

Honesty about the trade matters more than a feature grid, so: the database is a copy, synced daily. It is not live. If your question is "where is that vehicle now", Wialon answers it and this does not — by design, since chasing real time here would add cost and still lag the source.

You also take on something. SQL is a skill your team needs, or a BI tool that hides it. A database is a thing with credentials, access rules and a bill. For a fleet whose questions are fully answered by the built-in reports, that is overhead bought for nothing, and we would rather say so before an invoice than after one.

Nothing about how your fleet is operated. FleetSQL reads with a token you can revoke, never writes back, and adds no configuration inside Wialon — no notifications registered, no report templates created, no unit properties touched. Dispatchers keep working exactly as they do today and never see the difference.

It also does not lock the data up again. It is your database, exportable and replicable with standard tools, which is precisely the property that was missing when the data lived only behind someone else's reporting screen.