Wialon Driving Logbook: Business or Personal
Every trip Wialon recorded in one table — classified business or personal, written back to the trip, and exported to Excel for a mileage claim.
Read moreRebrand an application we already ship for $500 a month, live in days — or have a platform built around your own data model, tenants and roadmap. This page is mostly about the second.
A branded web app on your domain covers the buying decision; the store listing is phase two.
Provisioning and roles in an admin screen, or the product stops scaling at the fifth customer.
Your data model stays yours, so the layer below can be replaced without a rebuild.
Phase one is scoped to the workflows that close a sale, not to the roadmap. These are the parts it is built out of.
The login page, the domain, the support link, the URL in the address bar.
Provisioning, roles and per-tenant settings without engineering time.
Tenants, users and business objects in your database, not the platform's.
Telemetry through an integration layer that can be swapped out later.
Tenant isolation, access control, and an event log you can hand to a customer.
We onboard the first customers alongside your team, then work your roadmap.
Then the roadmap you set, as milestones rather than a backlog we own.
Quoted before anything is built, against a scope written down on the call.
$500 / month
Per application, live in days. Priced on each product's own page.
Quoted
After the free call, and phased — each phase priced on its own.
$500 a month per application, stated on each product's own page rather than here — rebranding something we already ship is a licence, and this page is about a platform built to scope. The price is per application per month, so a second and a third are decisions made once there are customers for them.
Yes, but it is priced on the call rather than here. FleetSQL is a managed extraction service running against a database per client, so what it costs depends on the fleet and the schedule — unlike the four applications, which are the same product whoever runs them.
Anything the application does not already do. A feature built for you is a fixed-scope build, quoted on its own — and it starts from a working product rather than from nothing, which is usually the cheaper half of the decision.
Yes, and most launches do. A branded web application on your domain covers the buying decision; a store-listed app under your name is a later phase with its own review and release overhead. Deciding that in phase one keeps the launch date realistic.
That is what the tenant model buys you. Provisioning, role assignment and per-tenant settings belong in an admin interface your operations team can use. If onboarding needs a developer, the product cannot scale past a handful of customers regardless of how good it looks.
Keeping your data model and your own database separate from the platform is what preserves that option. Your product owns its tenants, users and business objects; the platform supplies telemetry through an integration layer that can be replaced without rebuilding the front end.
Yes. We implement against your priorities and keep delivery transparent through milestone-based planning.
Yes. We usually launch with a practical baseline and then extend by business priority.
We define tenant-level boundaries for data, access policies, and operational controls at architecture stage.
Every trip Wialon recorded in one table — classified business or personal, written back to the trip, and exported to Excel for a mileage claim.
Read moreThe Wialon partner model explained: billing plans and margin, where leads come from, statuses, and where new partners get stuck.
Read moreA practical build-vs-buy model for white-label fleet products: 18-month total cost, differentiation layers, and staged launch planning.
Read more