Wialon Pricing: Hosting, Local, Platform, Lite

Wialon publishes no price list — only pricing models. Aggregator sites fill the gap with invented per-vehicle figures, which is how a fleet budgets a round number per unit and meets reality later. This guide explains the actual mechanics: the four editions, where the discounts live, the five variables that determine any real bill, and the costs that sit outside the platform invoice entirely. Exact figures come from your Partner Success Manager or your Wialon partner; everything that shapes them is below.

Why there is no price list

Wialon sells to service providers, who sell to fleets. The vendor’s price is a wholesale input negotiated against volume and commitment, and the fleet’s price is a retail service that includes hardware, installation, support and somebody’s margin. Publishing the first would misrepresent the second, and a fleet that finds a per-unit figure on a comparison site is reading a number that was never meant to describe what they will pay.

This is also why two quotes for the same fleet can differ substantially without either being dishonest. They are not quoting the same thing: different service lists, different history depth, different support commitments, different hardware. Comparing the headline figures is the mistake; comparing what is inside them is the work.

The four editions

Wialon Hosting is the multi-tenant cloud: per-unit billing through a partner’s billing plans, no servers to run, updates and backups handled by the vendor. Most fleets land here, and most partner margin math assumes it. Choose it unless something specific pushes you elsewhere — the operational cost of the alternatives is real and recurring.

Wialon Local is the server licence on your own infrastructure: an upfront licence plus your own hardware, monitoring and upgrades. It wins where data must stay in-country, connectivity to the vendor cloud is poor, or the fleet is large enough that per-unit fees exceed server costs over the licence horizon. It loses wherever nobody owns the server after installation — an unpatched Local ages badly, and the second year is when that becomes visible. Before choosing it, name the person responsible for backups, upgrades and certificate renewal. If that person does not exist, the edition is wrong.

Wialon Platform is the newest edition: a builder for service providers who want their own product rather than a rebranded portal — your own data model, your own screens, Wialon’s engine underneath. It is a platform commitment rather than a per-unit line, and it is the edition to ask about when the answer to “can we change this screen” keeps coming back no. If the goal is only your own name on an application that already exists, that is a white-label licence instead.

Wialon Lite is the cut-down tier for basic tracking: fewer services, materially lower cost. It fits subcontractors and light fleets that need position, trips and geofences and nothing else — and it is the wrong choice the moment someone asks for fuel analytics or custom reports, because the missing services are the ones that answer those questions. Treat it as a tier for a segment of your fleet rather than for the whole of it: mixed estates are normal, and a subcontractor’s van does not need what a tanker needs.

How a billing plan is actually built

Partner pricing is not one number, it is a plan. A billing plan attaches to an account and declares which services the units in that account may use, what history depth they keep, and what each of those costs. Activation, plan changes and service bundles all flow through the CMS, which is why two partners can quote the same fleet differently — their plan structures differ, not just their margins.

The consequence for a buyer is that “per unit” is meaningless without the plan behind it. A unit with position and trips is not the same product as a unit with fuel-level analytics, driving-behaviour scoring, video and two years of message history, and both are priced per unit. When comparing offers, ask what is inside the plan — which services, what history depth, what support tier — and only then look at the figure.

The consequence for a partner is that plan design is a pricing decision, not an administrative one. A plan built to cover every eventuality prices you out of small fleets; a plan built too thin means every second client needs a custom one, and a portfolio of bespoke plans is a portfolio of margin leaks.

Where the discounts live

Two mechanics move the totals. Turnover discounts grow with billed volume, so the effective rate falls as the partner’s estate grows — which means a young partner’s cost base is structurally higher than an established competitor’s, and competing purely on price against them is a losing position. Functional terms are tied to how the partnership operates rather than to volume alone.

The practical lesson is about timing. Volume discounts reward consolidation, so a partner running fleets across several accounts or several partner relationships is paying more than they need to. Consolidating before a growth push is cheaper than discovering the tier boundary a year later.

The five variables that set your bill

1. Units and mix — tracked vehicles, trailers, machinery and personnel trackers bill differently; count them separately. A fleet of “200 assets” that turns out to be 120 vehicles, 60 trailers and 20 personnel trackers prices differently from 200 vehicles.
2. Services per unit — fuel, driving behaviour, video and reports are services, not defaults. A “cheap” quote often just excludes them, and the exclusion is invisible until the first month someone asks for a fuel report.
3. History depth — the default retention window versus extended storage changes both price and what analytics remain possible a year later. Year-on-year comparison needs more than a year of history, and buying it retroactively is not possible.
4. Support tier — who answers the driver at midnight, and whether that is priced in or billed by the hour. This is the line most often left ambiguous and most often disputed.
5. Hardware and connectivity — trackers, sensors, installation and SIM plans sit outside the platform bill but inside the project budget, and dwarf it in year one.

Run any quote against these five before signing. A proposal that cannot itemise them is not a proposal.

The costs that are not on the platform invoice

Year one is where budgets break, and the platform is rarely the reason. Six lines belong in the model next to it:

• Devices, including the spares you will need because some percentage fails and some vehicles are sold with the tracker still fitted.
• Sensors — fuel-level probes, temperature sensors, CAN adapters, driver identification readers — each of which is hardware plus an installation plus a calibration.
• Installation, priced per vehicle type rather than per vehicle: a van and a refrigerated trailer are different jobs.
• Connectivity, one SIM per device per month, plus the administrative cost of managing them.
• Configuration and calibration, which is the labour that turns a device reporting numbers into a fuel report someone trusts. Skipping it is the single most common cause of a deployment that is technically live and commercially dead.
• Integration, if the data has to reach an ERP, a BI tool or a payroll system — see the integration page for how that work is scoped and priced.

Add training. A platform nobody was taught to use produces the same reports for three years and none of the value that justified it.

Build the model yourself, in six lines

You do not need anybody’s price list to produce a defensible budget. You need six lines and the discipline to fill each one from a quote rather than a guess:

1. Platform, recurring. Units by class, multiplied by the plan rate for the service list each class actually needs. Two or three classes, not one blended number.
2. Connectivity, recurring. One SIM per device per month, plus a small allowance for the ones that need replacing.
3. Hardware, one-off, amortised. Device plus sensors per vehicle type, spread over the contract length you intend to sign, with a spares percentage on top.
4. Installation, one-off. Per vehicle type, with an explicit line for the awkward categories — trailers, refrigeration, heavy machinery.
5. Setup labour, one-off. Configuration, calibration, report building and training. This is the line that gets cut and the line whose absence causes the deployment to underperform.
6. Support, recurring. Either a tier you are buying or a headcount you are staffing. If it is neither, it is a cost you have hidden from yourself.

Two ratios tell you whether the model is sane. Year-one one-off costs usually exceed year-one recurring costs, often by a wide margin — if your model says otherwise, something is missing from lines three to five. And the platform line is normally a minority of the total, which is why choosing a provider on the per-unit figure alone optimises the smallest variable in the budget.

Run the same six lines against three years rather than one, and the edition decision usually answers itself.

Migrating between editions

Moving from Lite to Hosting is a plan change. Moving between Hosting and Local is a project: an export, an import, re-pointed devices, re-created users and rights, and a window where both are running. Nothing about it is exotic, but it is work, and a partner who quotes it as an afternoon has not done it.

The planning lesson is to choose the edition against a three-year view rather than a first-year one. The cases where Local genuinely wins — data residency, poor connectivity, scale — are visible at the start. The cases where a fleet moves to Local because a spreadsheet said so in month two, and back eighteen months later after nobody patched the server, are also visible at the start if anyone asks who owns the server.

The questions that make a quote comparable

Take these to every partner conversation:

• Which services are in the plan, name by name, and which are chargeable extras?
• What history depth is included, and what does extending it cost?
• What is the support tier, with response times, and what falls outside it?
• Is hardware sold, rented or lent, and who owns it at the end?
• What does installation cost per vehicle type, and what happens if a vehicle is not available on the day?
• What is the exit: export format, retention, and who pays for it?
• What does a change to sensor configuration or report definitions cost after go-live?

Seven questions, and the quote that answers all seven is usually not the cheapest headline figure. It is usually the one that turns out to be true.

The honest next step

If you are budgeting a fleet rollout or choosing between the four editions, the numbers depend on your unit mix and service list — which is a thirty-minute conversation, not a blog post. Our consulting does exactly this costing for partners and fleets, and the integration practice builds on whichever deployment you pick. Ask — the call is free, and you will leave with arithmetic even if you buy from someone else.