Short version. Navixy is a mature white-label telematics platform sold as a licence, deployable in their cloud, on your premises, or as PaaS, with usage-based pricing and eighteen years behind it. Routly is AGPL-3.0: you get the source, the fee stops tracking the fleet, and you take on running it. If you want a supported product with a vendor accountable for it, Navixy. If you want the code and the cost curve, Routly.
Where they overlap
Both are aimed at the same reader: a telematics provider or integrator who wants to sell fleet tracking under their own name rather than resell somebody else’s brand. Both offer multi-tenancy, per-customer branding, and deployment on infrastructure you control. Neither makes you re-flash a tracker.
That overlap is real and worth stating before the differences, because a comparison that opens by listing distinctions makes two products sound less alike than they are.
Where they actually differ
| Navixy | Routly | |
|---|---|---|
| Licence | Proprietary | AGPL-3.0, or commercial |
| Source code | Not provided | Complete, yours to modify |
| Deployment | Cloud, on-premise or PaaS | Self-hosted, one compose file |
| Pricing model | Usage-based, scaling with tracked units | Infrastructure; licence free or quoted |
| Does the fee track the fleet | Yes | No |
| Device protocols | Decoded natively, large certified range | None — reads from Flespi, Traccar or JSON |
| Telemetry store | Theirs | Your PostgreSQL and ClickHouse |
| Track record | 18+ years | Young, and we say so |
| Support | Vendor SLA | Community, or a commercial agreement |
Read the last two rows honestly. Navixy has been doing this since before Routly existed, with the support organisation that implies. That is not a rounding error in a decision about a platform your customers depend on.
The trade, stated plainly
Navixy is a product. You pay, it works, somebody is accountable when it does not. The cost scales with the units you track, and what the platform can do is decided by their roadmap.
Routly is source code. Nobody is accountable unless you buy a commercial licence, and running it is your job. In exchange the cost is your infrastructure rather than your unit count, and the answer to “can you add X” is a scheduling question rather than a support ticket.
Neither is the correct answer in general. They are different positions on the same axis: how much control you want, against how much you want to operate.
The number that decides it
For a reseller the arithmetic is not subtle. A per-unit fee is a percentage of your revenue paid to a supplier, and it does not shrink as you grow — the margin table works it through. Against that sits a roughly flat infrastructure line: a position costs about nineteen bytes on disk, so ten thousand vehicles is tens of gigabytes a year, not a capacity project.
The crossover depends on your unit rate and your ops cost. Below a few hundred units under management, a licensed product is very often cheaper than the attention self-hosting requires. Above a few thousand, the gap compounds every month. Work it out with the cost worksheet rather than taking either vendor’s word.
When to choose Navixy
- You need a vendor with an SLA to point your own customers at.
- Your hardware mix is unusual and you want certified device support rather than a gateway of your own.
- You have no operations capacity and no intention of acquiring any.
- You want the platform to be somebody else’s problem, and the per-unit fee is a price you are content to pay for that.
When to choose Routly
- Your unit count is large enough that a per-unit fee is visibly eating your margin.
- You want to modify the platform — integrations, calculations, exports — rather than request changes.
- Your customers ask where their telemetry physically lives, and “a Postgres we run, which you may audit” is the answer you want to give.
- You already run a gateway — Flespi or Traccar — and want the application layer above it.
- You are coming off Wialon and want a migration that touches no trackers.
What we are not claiming
We have not run Navixy. Everything in the table above comes from their own published material, linked where it matters, and their product will have depth that public pages do not show. If you are choosing between them, get a trial of theirs and open ours — it needs no account — and compare the two in front of you rather than through anybody’s comparison page, including this one.
If we have something wrong here, tell us and we will correct it.
Frequently asked
Can Navixy and Routly read the same devices?
Usually yes, via a shared gateway. Both can sit behind Flespi, so running them side by side to compare is a configuration rather than a project.
Is AGPL a problem if I resell?
It is the case AGPL Section 13 covers, and it needs a decision before you build. The plain-language version is here; the short answer is that a commercial licence removes the obligation.
Which is faster to launch?
Navixy, almost certainly. Buying a working platform beats deploying one on any timeline shorter than a few weeks.
Which is cheaper?
At small unit counts, Navixy. At large ones, self-hosting, by a widening margin. There is no answer that is true at both ends, and anyone giving you one is selling.
