Hoppvia sells white-label taxi and ride-hailing software and publishes this guide. Use it as a buying checklist, not as an independent ranking.
Start with the trips your business runs
Write down one normal booking and one common problem. For example, follow a ride from request to driver offer, acceptance, pickup, drop-off and the trip record. Then ask what happens when the driver says no, or nobody accepts. If you need airport pickups, company accounts or shared shuttles, add those to the list.
Ask a white-label supplier to show the flow working today. Ask a custom developer what already exists, what they must build and how you'll test it. In both cases, a product preview is not the same as a live system connected to your services.
Compare what you must do, not just the features
| Question | White-label platform | Custom build |
|---|---|---|
| Starting point | An existing product, set up for you | A written spec, often built with existing frameworks |
| Branding | Check which screens, store listings and messages carry your brand | Agree the design and brand work in the project |
| Unusual workflows | Check settings and any paid extensions | Describe the behaviour, problem cases and tests |
| Source code | Read the licence. Your brand on the app does not mean you get the code | Read the contract. Paying for the work does not settle every ownership question |
| Integrations | Check each provider works in a live setup | Budget for building, testing and maintaining each one |
| Updates and support | Check what's included and how upgrades work | Decide who fixes bugs and pays for updates |
| Leaving the supplier | Agree data exports and account access | Agree code, documents, accounts and handover |
Settle these questions with each supplier. Every contract is different.
When white-label fits
A ready-made platform makes sense when its main flow matches your service and you know what's left to do. You might need your own branded customer and driver apps, your own ride types and a dispatch process that follows each booking.
Ask which parts of your launch the supplier can show working today, not how long their feature list is. Confirm app stores, service areas, languages, payment methods and outside accounts. Put any changes in the proposal, with an owner and a test.
For Hoppvia, see the white-label taxi app page and the customer, driver and dispatch walkthrough. The public app screens use sample data. Every plan includes branding, hosting and updates. Source code is not included.
When custom fits
A custom build makes sense when no platform you've tested can handle a must-have workflow, or when owning that workflow is central to your business. Define it clearly first: who acts, what data changes, what happens when a service fails and what your team needs to see.
For example, seat booking and multi-stop routes for a shared shuttle are very different from a private car booking. Ask each supplier to show or spec that difference. A new logo is also a much smaller job than a new dispatch process.
A custom app still depends on outside services. Maps, notifications, payment providers, phone operating systems and app store review all stay part of your setup. Budget for maintenance and a handover plan.
Hoppvia itself started this way. It began as a custom platform built for one fleet operator, at a five-figure cost. It now runs with 5,000 drivers and 20,000 customers at peak traffic. We turned it into a ready-made product so other operators don't have to pay for a custom build.
Compare costs over the same period
Compare written quotes for the same needs and the same number of trips. Split one-time work from yearly hosting, maintenance and support. Then add usage fees and provider accounts. If something isn't priced, list it as open, not as free.
Published prices help you understand each pricing model. They don't tell you what a custom build will cost. The taxi app cost guide has sourced vendor prices and a worked twelve-month example. Use it to ask better questions about setup, subscriptions, trip limits and branding fees.
For a custom quote, ask for each deliverable, the assumptions, how changes are priced and what you must maintain. A one-off project price is hard to compare with a subscription until both cover the same work and time.
Hoppvia's plans are published: $1,990 a year for up to 50 drivers, $3,990 a year for 51–200 drivers, or a one-time licence from $4,499 plus $990 a year for hosting and updates. All plans have unlimited trips and 0% commission.
Confirm app store accounts and submission
Ask who owns the developer accounts, signs releases, prepares store listings and answers review questions. Help with submission is not the same as approval.
Apple's App Review Guidelines, including section 4.2.6, cover apps made from commercial templates or app builders. Check the current rules with your supplier. Buying a branded app does not guarantee an approval date.
Write a short decision record
| Need | What to collect | What to record |
|---|---|---|
| Normal booking and problem case | A demo or an agreed test | Included, needs setup, needs custom work or not available |
| Customer, driver and staff access | The apps and dispatch views you need | App stores, staff roles and who owns each account |
| Connected services | Named providers and test results | Account owner, setup work and usage fees |
| Software and data rights | Written terms and an export plan | Access, what you may do, handover and exit |
| Cost and support | An itemised quote for the same period | One-time costs, yearly costs and who handles support |
Pick the option that runs your must-have flow and whose ongoing work your team can manage. If a must-have item is still open, give it a next step before you call the plan done.
Bring your workflow to a Hoppvia demo
Share your country, fleet size, booking channels and one problem case. See the dispatch walkthrough, then ask to follow your own trip through the customer, driver and dispatch views.
Book a Hoppvia demo and see Hoppvia's published pricing. Your launch plan will show what's included, which services you connect and what your team runs after launch.
Frequently asked questions
Is a white-label taxi app always cheaper than a custom build?
Not always. You can only compare once both quotes cover the same features, time period, trip volume and ongoing work. Compare full quotes, including integrations, provider fees, updates and support.
Does white-label software include the source code?
It depends on the supplier. Branding, the right to use the software, code access and ownership are separate questions. Hoppvia plans license the platform for your brand. Source code is not included.
Should I build or buy my taxi app?
Test ready-made platforms against your main booking and dispatch flow first. If they fit, compare setup, rights and running costs. If they don't, ask for a specific custom quote with clear tests and maintenance terms.
Sources and method
Written on 2 November 2026 and updated on 10 November 2026, using Hoppvia's published product scope, sample walkthroughs and cost guide, plus Apple's App Review Guidelines linked above. The examples are needs to check, not measured customer results or legal advice about a contract. Hoppvia publishes this guide and sells taxi software.
