Where
Every vehicle, one map
Positions arrive as fast as the trackers send them. A vehicle that goes quiet is marked offline instead of being left on the map where it was last seen.
Free to self-host · AGPL-3.0 · in production
Fleet software that stops charging by the vehicle
Live map, trip logbook, fuel analytics and driver scoring — on your infrastructure, with every position in a Postgres you can query yourself. No per-vehicle fee: run it for your own fleet and the licence costs nothing.
The real interface with a sample fleet in it. No account, no install.
Full platform
Everything the fleet asks for
Five screens people open every day, and one thing that matters if you run more than one fleet — all of it on servers you control.
Live map
Every vehicle on one map, as often as its tracker reports. The telemetry never leaves your servers.
4 vehicles live
Trip history
Trips detected automatically, with the route replayed and the distance and duration behind it.
Custom reports
Build the report you need, save it, schedule it. Exports as CSV, Excel or PDF.
Instant alerts
Speeding, geofence and idling, delivered by email or to a webhook you point at your own systems.
!
Speed alert
Van #42 exceeds 80 km/h
Geofences
Polygons or circles, as many as you like, with every entry and exit written down.
One deployment, many fleets
Every customer an isolated organisation, with roles and grants down to a single vehicle, and their own logo on the reports you send them.
A
B
C
D
+12
The interface
Where it is, what it did, what it cost, who drove
One screen for each, below. They are captures of the demo — the same build the product ships, filled with a generated fleet so there is something to look at. Open it and you are clicking the real interface, not a picture of one.
What happened
Trips, classified
Every journey with its route, distance and duration, tagged business, personal or commute — and exported as a spreadsheet when the accountant asks.
What it cost
Fuel, including the theft
Litres per hundred kilometres and what they cost, per vehicle — with a sudden drop flagged as a drain rather than buried in the month’s consumption.
Who is driving how
The board you build
Pick a metric, a grouping and a shape: distance by vehicle, harsh braking by driver, trips by day. Nobody has to ship you a new report to answer a new question.
Why people move
The bill is not the worst of it
Price is what starts the conversation. What ends it is realising that the data, the roadmap and the terms all belong to someone else.
Cost
The meter never stops
Per-vehicle, per-month, forever. Growing the fleet grows the invoice, and nothing you have paid so far reduces the next one.
Ownership
Your history is theirs
Years of positions and trips live in someone else's database, reachable through whatever export they choose to offer.
Control
The roadmap is someone else's
A report you need is a feature request behind a queue you cannot see, for customers you are not.
Who moves
Two readers, one invoice
The three costs above land differently depending on which of you is reading. Here is the version that applies to you, and the part of Routly that answers it.
You operate the vehicles
The meter is an operating cost
- Trailers, gensets and the spare van go untracked, because each one has to earn back a monthly fee before it is worth watching at all.
- Budgeting for growth means budgeting for the invoice that follows it.
- Self-hosted, the hundredth vehicle costs what the first did — disk, not licence.
- And it is one host of ordinary parts to keep running, not a platform team.
You sell the service
The meter is your margin
- Every customer you win arrives already taxed by your supplier, and the tax scales exactly as you do.
- You take the support calls and do the integration work; the platform margin goes upstream regardless.
- One deployment holds every customer as an isolated organisation — their own users, vehicles, geofences and reports.
- Reports go out under each customer’s own logo and colours. How the white-label side works.
Neither of you has to touch the hardware
Routly reads from Flespi, from Traccar, or from any gateway that can POST JSON. The trackers already in the vehicles keep reporting exactly as they do now, which is what lets both systems run side by side while you check the data.
What it costs
Two ways to run it, and you pick
The same code under either licence. Which one you need is decided by what you do with it, not by how many vehicles you have.
AGPL-3.0
Free of chargeYou self-host it for your own fleet
- The whole product: map, trips, fuel, driver scoring, reports, alerts, the mobile app.
- No per-vehicle fee and no seat count — you pay for the servers you run it on.
- The complete source comes with it, which is what the licence guarantees anyone who receives it.
- Running it privately and unmodified triggers no obligation at all.
- Modify it and let others use it over a network, and you publish those changes under the same licence.
Commercial licence
QuotedYou resell it, host it for customers, or cannot take AGPL code
- Removes the source-disclosure obligation, so your branding and integrations stay yours.
- The licence a telematics provider needs to offer Routly under its own name.
- Also the answer when procurement or a security policy rules out AGPL outright.
- Adds warranty, indemnity and a support agreement.
Neither licence obliges you to do the move yourself
Assessment, deployment on your infrastructure and running both systems side by side is work we do with you, quoted on what you already run. It is a service, not a condition — the licence gives you the source either way, and nothing stops your own team doing the deployment.
Switching
Three steps, and you can run both at once
The trackers keep reporting to both systems while the data is compared, so nothing is cut over on trust. You are never without tracking, and never mid-migration without a fallback.
- 01
Assessment
1–2 daysWe go through what you run now — devices, protocols, the reports people actually open, the integrations that must keep working.
- 02
Deploy
1–3 weeksRoutly goes up on your infrastructure with your branding, your users and your geofences configured.
- 03
Migrate
1–2 weeksBoth systems run side by side on the same trackers while the data is checked. You switch when you are satisfied, not before.
What you operate
Ordinary parts, on your hardware
Nothing exotic to run: a Postgres, a ClickHouse, a Redis and one API, brought up with a single compose file.
1
Compose file for the whole stack
0
Map vendor keys
2.9×
Telemetry compressed on disk
PostgreSQL
YoursVehicles, trips, users
ClickHouse
2.9×Measured on production
Redis
OptionalA single node is fine
MQTT
3 pathsFlespi, Traccar or webhook
MapLibre
No keyNo map vendor bill
Docker
ComposeOne file, five services
Fastify
NodeOne service
React 19
ViteA static bundle
Why these parts
No vendor lock-in
Every component is one you could replace
Ordinary components
Postgres and Docker, not a bespoke runtime
Your team knows it
Whoever runs your databases can run this
One host to start
Scale out when the fleet asks for it
Where a position goes
GPS device Flespi / Traccar Tracker rate
Gateway MQTT broker Or webhook
Backend ClickHouse Batch insert
ClickHouse Dashboard Cached 10s
Already running Traccar?
Keep it. Traccar decodes 200+ device protocols and Routly reads from it — the same way it reads from Flespi, or from any gateway that can POST JSON. Traccar gets the bytes off the device; Routly is the part your customer looks at: trips classified, fuel theft separated from ordinary burn, driver scores, and reports that arrive by email on a schedule. The long version.
Talk to us
Tell us what you are running now
Tell us what you run today and how many vehicles are on it — whether that is one fleet or thirty customers’ worth. We answer within one working day.
Or look around first — the demo needs nothing from you. Open it.