Does FleetTAB replace Wialon?
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 connects to an existing Wialon account and adds four things on top of it: KPI dashboards you assemble yourself, trips worked through in bulk, driver behaviour scored from the same data, and service intervals with their history. Nothing moves off Wialon. It stays the source of truth, and FleetTAB reads from it with a single API token. It ships white-label for partners who put it in front of their own customers.
An online report gets five minutes of server time and a detalized report caps at 400,000 rows. Continuous execution for one user from one IP is capped at ten minutes, and crossing it pauses reporting for a further ten. That suits a scheduled report. Answering a question by trying five variations of it is a different pattern, and it is the one a dashboard is for.
Reviewing a month of trips, assigning the driver on each and setting statuses happens one record at a time, which is where the exports to a spreadsheet usually start. FleetTAB filters the list and applies the change to the whole selection at once.
Wialon Hosting keeps unit history for 400 days by default and removes older messages automatically. Analysis that reaches past that window needs the data mirrored somewhere else first, which is a different product and a different decision.
Wialon partners and integrators who want more to offer alongside the platform, under their own brand and without building and maintaining a front end themselves.
Fleet operators already running Wialon whose daily routine has drifted into spreadsheets: reviewing trips, assigning drivers and chasing service intervals.
A card builder rather than a fixed layout: choose the card type, the metric and the arrangement, and keep the dashboards each role actually looks at.
Filter the trip list, then act on the whole selection: assign drivers, set statuses and export, instead of opening records one at a time.
Driving behaviour scored from the same Wialon data, with the underlying violations visible so a score can be explained to the driver it belongs to.
Service intervals with history and attached files, so the next service is a date in the system rather than a note in a calendar.
Trip lists of 10,000 and above stay responsive through virtual scrolling, which is the size at which a spreadsheet stops being an option.
Any view exports to CSV or Excel as it is filtered, so the version someone emails matches the version they were looking at.
Logbook with filtering, bulk driver assignment and statuses, exportable as filtered. The module most of the daily work happens in.
Scores and the violations behind them: acceleration, braking, cornering and speeding, as configured on the Wialon side.
Intervals and services, with history and file attachments per asset.
Enter a work email and the one-time code sent to it. No separate password to manage or reset.
Wialon issues the token from its own authorization page, so credentials never pass through FleetTAB. The token is 72 characters and is validated on entry.
Paste the token once. The connection is maintained from that point on, and the token can be revoked in Wialon at any time.
Units, trips, sensors and driver assignments appear as they exist in Wialon. Nothing is duplicated or re-entered.
FleetTAB ships white-label. Partners deploy it under their own brand and domain, and the customer sees the partner's product rather than ours.
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. Wialon expresses access as a flag value on the token, and the flag to issue is the narrowest one that covers reading. Our Wialon API token reference has the flag table and what each value grants. Whatever you issue, the token is revocable from Wialon at any moment.
Trip lists in the tens of thousands stay usable. The list is virtualised rather than paginated, which is what keeps filtering and bulk selection responsive at that size.
Yes. White-label is the configuration partners use most: your brand, your domain, optionally a standalone deployment, with the commercial relationship and billing yours.
Tachograph support and checklists are the next modules. Feature priority is public: the feedback board on the documentation site is where requests are raised and voted on, and partner requests carry weight in what gets built.
They answer different questions. FleetTAB is the interface for running the fleet day to day, reading live from Wialon. FleetSQL mirrors Wialon into a PostgreSQL database you own, for questions that reach past the platform's retention window or need joining against ERP and finance data. Fleets commonly end up with both.
Ecodriving is live on the Wialon Marketplace: 0–100 vehicle and driver scores from your own Wialon criteria, violations on a map, export to Excel, CSV, PDF.
Read moreHow FleetSQL began: a passion for telematics reports, years of customer feedback, and the path from one Python script to a full backend service.
Read moreFleet Configuration Tools is live on the Wialon Marketplace: rename or delete a sensor across every unit, and set each odometer from its mileage sensor.
Read moreA fleet organization moved from static report exports to SQL analytics with governed metrics and daily data quality checks.
Read moreHow a last-mile operator deployed a unified KPI dashboard to cut dispatch response time by 34% and improve route adherence by 18%.
Read moreHow a Wialon reseller launched a white-label fleet platform with phased delivery and controlled customization.
Read moreHelping businesses to make their fleets safer, teams more productive and processes more efficient.