Product

Your Wialon data. Your PostgreSQL.

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.

Why this exists

  • History is kept for a set period

    The default history period on Wialon Hosting is 400 days, and older messages are removed automatically. The period can be extended on request to a Partner Success Manager. Either way there is a horizon, so a year-over-year comparison built later can find nothing to compare against.

  • Reports run to a budget, and say so quietly

    An online report gets five minutes of server time, and a detalized report caps at 400,000 rows. When a limit is reached the execution is skipped and no rows come back, which a downstream system can read as a quiet period rather than a truncated one.

  • There is no off-the-shelf path to a database

    The API is the integration surface, and the general-purpose ETL tools do not carry a Wialon connector: Fivetran, Stitch, Airbyte and Hevo have none, and flespi's published downstream-integrations list has no warehouse destination. A database copy is something you build or buy rather than switch on.

  • Direct database access is a normal expectation now

    Fleet buyers increasingly expect to point Power BI, Tableau or Excel straight at their telematics data; Geotab, for one, bundles a Data Connector for exactly that. FleetSQL is that path for a Wialon account.

Who it is for

  • Telematics 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 sit in a warehouse next to ERP and finance data.

What you get

  • 50+ data points

    Unit properties, events, trips and report outputs extracted from Wialon and written into relational tables you can join against anything else you hold.

  • One database per client

    Isolation by default rather than a shared schema with a tenant column, so access control, backups and deletion are per customer.

  • Daily automatic sync

    Runs on a schedule you configure. Sync state is tracked per entity so an interrupted run resumes instead of starting over or duplicating rows.

  • Full SQL access

    A normal PostgreSQL database with normal credentials, and no query layer of ours in between. Metabase, Grafana, Power BI, Tableau, Superset and Looker connect to it, as do Python, pandas, Jupyter and R, and automation tools like n8n, Zapier and your own webhooks.

  • Historical backfill

    Initial extraction pulls history as deep as the account's Wialon retention period allows, so standing the mirror up early is worth more than it looks.

  • Managed for you

    Schema migrations, API changes on the Wialon side and failed-run recovery are ours to handle. You get a database to query rather than a pipeline to operate.

The data itself

  • Driver behaviour

    Eco-driving scores, harsh braking and acceleration events and idle time, per driver and per trip, queryable rather than locked in a scorecard.

  • Fuel events

    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.

  • Geofence events

    Enter and exit timestamps, dwell time and zone names: the raw material for site-time analysis, customer SLA reporting and detention billing.

How it connects

  1. Step 1: Connect a Wialon token

    A read-only token is enough. We scope it to online tracking and view access rather than asking for account-wide control.

  2. Step 2: Configure the extraction

    Choose the entities, parameters and units in scope. The schema is generated from that selection rather than from a fixed template.

  3. Step 3: Set the schedule and backfill

    Pick a sync cadence and how far back the initial extraction should reach, bounded by your account's Wialon retention period.

  4. Step 4: Query from anything

    Credentials arrive and the database is live. Point a BI tool, a notebook or an application at it the same day.

White-label

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.

  • Your branding and your domain on everything the customer touches.
  • The database and its credentials belong to your customer, so data ownership is an argument you can make.
  • You hold the commercial relationship and the billing.
  • Delivery, schema migrations and Wialon API changes are handled on our side, so reselling it creates no engineering commitment for your team.

Security and access

  • One database per client, isolated rather than sharing a schema.
  • Encrypted in transit and at rest.
  • Audit logs of extraction runs and access.
  • Deletion on request, covering the database and its backups.
  • Read-only Wialon access. The token we ask for cannot modify your account.

The mechanics, written out

Our Wialon API reference covers what this product handles for you. Useful whether you buy it or build it yourself.

Also from Asset Track

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

Guide · Analytics

The Story Behind FleetSQL

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 more
Contact

Let's connect.

About Us

Helping businesses to make their fleets safer, teams more productive and processes more efficient.