Nothing here is a flaw in Wialon — it is a tracking platform doing tracking. The work that piles up around it is reporting, logbooks and service records, and that is exactly the work FleetTAB takes over.
Where the built-in reports stop →5 min
What one Wialon report run gets before it stops
Today A question asked five ways is five report runs, five exports and a spreadsheet to reconcile them.
With FleetTAB A dashboard that answers it live, rebuilt by dragging cards rather than by re-running a report.
See the dashboard →1 by 1
How trips are assigned and statused in the platform
Today A month of driving, tagged business or private one record at a time — usually in an exported sheet.
With FleetTAB Filter the month, select it, and set driver, status and notes for the whole selection at once.
See the trip log →0 files
What a Wialon service record can carry
Today Intervals tracked in a spreadsheet beside the platform, and the invoice living in somebody's inbox.
With FleetTAB Intervals by mileage, hours or date, with the service history and the invoice attached to the unit.
See maintenance →Every screen below is FleetTAB running against a live Wialon account — 53 vehicles and their real telemetry, under names that belong to nobody. Sign in with a token and the same screens open on your own fleet.
Pick the cards, the metrics and the arrangement — one board for dispatch, another for the monthly review — over any selection of units and any period.
The logbook Wialon does not have: filter the period, select what you need, and write driver, status and notes across the whole selection in a single action.
Scores come from the same Wialon data your account already produces, and every one opens into the violations that made it — so a conversation with a driver is about events, not about a number.
Intervals by mileage, engine hours or date, counted against the odometer Wialon already reports — with what is due, what is overdue, and the paperwork attached where it belongs.
Every unit clustered on one map, online and offline counted, sensors readable without opening a report.
Odometer, engine hours, driver, traffic and mileage settings side by side — sortable, filterable, exportable.
Every section, in detail, on the features page.
There is no migration, no data import and no second platform to keep in sync. FleetTAB is a second interface over the Wialon account you already pay for — setup is minutes, and the first screen already has your own vehicles on it.
In Wialon, not here
An API token with read access, generated in your own account and revocable from it at any moment.
Paste it once
FleetTAB reads your units, groups, trips, sensors and driver assignments as they already are.
Nothing to import
Dashboards, trips, eco-driving and maintenance over the fleet that was already there.
Wialon stays the platform and the source of truth. FleetTAB reads from it and writes back only what you edit in FleetTAB itself — trip statuses, driver assignments, service records. Your dispatchers see the account they saw yesterday.
The setup, step by step, in the docs →On your Wialon account
Asset Track builds Wialon integrations for a living — pipelines, white-label apps and custom work. FleetTAB is what that experience looks like as a product, which is why the setup is a token rather than a project.
See the listing in the Wialon Marketplace →Wialon API expertise comes with the subscription.
New features ship regularly, and what ships next is raised and voted on in the open on the feedback board. Tachograph support and checklists are the modules in front of the queue.
See the feedback board →Ask for something and watch it get prioritised.
The same application under your brand, your colours and your domain, from the login screen on. Individual modules already run standalone — eco-driving, maintenance and utilization each ship as their own app.
Tell us what you need →Your brand, your customers, your pricing.
The same application with your name, your colours and your domain, from the login screen on — or one module as a standalone app. The customer relationship and the pricing stay yours.
How white-label works →Anything else is in the documentation, or ask us directly — the form is at the bottom of this page.
No. Wialon stays the platform and the source of truth: it keeps ingesting from the hardware and FleetTAB reads from it. If FleetTAB is switched off tomorrow, the Wialon account is unaffected.
FleetTAB reads units, trips, sensors, driver assignments and analytics, and writes back only what you edit inside FleetTAB — trip statuses, driver assignments and service records. Wialon expresses access as a flag value on the token, and the token is revocable from Wialon at any moment.
Trip lists in the tens of thousands stay usable. The table is virtualised rather than paginated, which is what keeps filtering, sorting and bulk selection responsive at that size.
Yes. FleetTAB is designed for two audiences at once: dense tables for the office, and a fast, glanceable layout for field staff. It installs as a PWA, speaks English, Spanish, French, Swedish and Russian, and follows the light or dark theme of the device.
Yes. White-label is the configuration partners use most: your brand, your colours and your domain, from the login screen on, with the commercial relationship and the billing yours. Individual modules — eco-driving, maintenance, utilization — also ship as standalone applications.
Tachograph support and checklists are the next modules. Priority is public: the feedback board on the documentation site is where requests are raised and voted on, and what gets built next follows those votes.
FleetTAB itself is free to use on your own Wialon account — there is no per-vehicle fee and no card to enter. What is paid for is white-label and custom work: the application under your own brand and domain, or a module built to your specification.
Questions, a demo, or white-label for your own company — tell us.
A person answers, usually the same working day. No newsletter, and nothing is passed on — see the privacy policy.
Your fleet data is already in Wialon. Put it to work.