Technology
White-Label vs Custom-Built Sharing App: Which Should Operators Choose?
By Axons Mobility Team · · 6 min read
The short answer
Most operators should choose a white-label sharing app: it carries your brand, needs no engineering team, and goes live as soon as your vehicles, store listing and payment account are ready. A custom build takes months and a team of engineers to create a rider app for two app stores, an operator console, device integration, payments, ID checks, accounting and security, and that team stays for as long as the service runs. Custom makes sense when software itself is your edge and you can fund the team for years.
For most operators, a white-label scooter sharing app is the better choice. You launch under your own brand without hiring a software team, and you pay a monthly fee instead of funding a build. A custom-built app makes sense only when software itself sets your business apart and you can pay engineers for years, not just until launch.
What does white-label mean?
A white-label product is made by one company and sold under another company’s brand. In shared mobility, it means a ready-made rider app, operator console and device connection that carry your name, logo and colours. Riders download your app, pay you, and never see the provider’s brand.
White-label is not the same as buying an app script. With a script, you buy the code and run it yourself, so hosting, fixes and updates become your job. With a white-label platform, the provider keeps the software running and up to date, and you run the fleet.
What does building your own sharing app really involve?
The rider app is the part people picture, but it is only one piece. A working sharing service needs all of these:
- A rider app on two stores. Separate builds for iOS and Android, each passing Apple’s and Google’s reviews, with maps, sign-up, unlock, payments and ride history. New phone models and system updates can break things at any time.
- An operator console. A web tool for your team, with a live map, remote lock and unlock, zones, pricing, riders, support tickets, repairs and reports. It is often bigger than the rider app.
- Device integration. Talking to the device on every vehicle over mobile networks, coping with lost signal, confirming that a lock or unlock really happened, and making sure nobody else can send commands.
- Payments. Cards, Apple Pay and Google Pay, deposits, refunds, failed payments, wallets and passes, with rules that differ from country to country.
- ID checks. Checking age and identity, and handling riders who fail the check or try again with someone else’s ID.
- Accounting. Matching every ride, refund and payout to your books, with VAT and reports your accountant will accept.
- Maintenance. Bug fixes, store updates, server upgrades, and someone on call when unlocks fail late at night.
- Security. Protecting rider accounts, payment flows and device commands, and testing that protection regularly.
- GDPR. If you have riders in the EU: lawful data handling, export and deletion requests, agreements with every supplier that touches rider data, and records of who accessed what.
None of this is impossible. But each item needs people who understand it, and none of it ends on launch day.
White-label vs custom-built: how do they compare?
| Factor | White-label platform | Custom-built app |
|---|---|---|
| Time to launch | As soon as your vehicles, devices, store listing and payment account are ready | Months of design, building and testing before the first paid ride |
| Upfront cost | A setup fee, if the provider charges one, plus devices | A team of engineers, or an agency, paid for months before you earn anything, plus devices |
| Ongoing cost | A monthly fee, usually per vehicle | A team of engineers, hosting, security testing and app updates for as long as you operate |
| Control | You control brand, prices, zones and rules; the provider controls the code | Full control of every feature and the code |
| Risk | Provider risk: price rises, lock-in, slow support | Build risk: delays, launch-day bugs, key engineers leaving |
| Updates | The provider builds new features and ships store updates | Your team plans, builds, tests and ships every update |
White-label costs are easy to estimate before you sign. Published prices checked in September 2026 put mid-market white-label platforms at about $6–18 per vehicle per month, with monthly minimums around $250–900. A custom build’s cost depends on your team, your country and your scope, so get real quotes from engineers or agencies before you compare the two.
Which costs stay the same either way?
The choice between white-label and custom only changes the software line of your budget. Everything else stays the same whichever way you go:
- vehicles, spare batteries and parts
- connected devices and their data plans
- insurance, permits and city fees
- card processing fees from your payment provider
- staff to charge, move, fix and support vehicles
- marketing and launch offers
That matters, because a custom build does not make any of these cheaper. It adds a second business to run, a software team, on top of the fleet. Before choosing custom, ask whether your riders would notice the difference, or whether the money would do more as extra vehicles, better parking or faster repairs.
When does a custom-built app make sense?
A custom build can be the right call when most of these are true:
- Software is your edge. Your business depends on something no platform offers, and you expect it to be the reason riders choose you.
- You already have the team. Engineers with mobile, backend, device and security experience are already on staff.
- You can fund it for years. The money covers the team after launch, not just until the first ride.
- Your vehicles are unusual. No platform supports your vehicles or devices, and none plans to.
- Your scale justifies it. Per-vehicle fees would cost more than a permanent team, and you have checked that with real salaries.
If only one or two of these are true, a sensible middle path is to launch on a white-label platform, learn what your riders actually need, and decide later whether a custom build is worth it.
Can you start with white-label and build your own later?
Yes, if you protect three things from the start. First, your rider relationship: if the app sits in your own store listing and riders pay into your own account, a future app of yours can ship as an update to the same listing, so riders do not have to find a new app. Second, your data: make sure the contract lets you export riders, rides, payments and repairs in a standard format. Third, your devices: prefer devices you own and that can be connected to other software.
With those in place, white-label is not a dead end. It gives you real rides, real costs and real rider feedback, which is exactly what you need to write a good brief for a custom build, if you still want one.
What should you demand from a white-label provider?
A white-label deal is only as good as its terms. Ask for these in writing:
- Your brand only. Riders should not see the provider’s name in the app, on receipts, in emails or in the store listing.
- Your store listing. Ask whether the app can be published under your own Apple and Google developer accounts, so the listing and its reviews stay yours if you ever move.
- Your Stripe account. Rider payments should go into your own account, so you are the seller and the money reaches you directly.
- No feature tiers. Published prices checked in September 2026 show some platforms locking sobriety tests, RFID card unlock and work orders to a $5,000-a-month top tier, and another selling invoicing and loyalty as paid add-ons on lower plans. Ask for every feature on the plan you pay for.
- A trial on your own vehicles. A demo with sample data shows screens; a trial shows whether unlocks work on your streets. Some platforms charge €12,500–15,000 for a pilot of up to three months, so ask for a free trial first.
- Know where rider data lives. Ask where rider data is stored and processed, and ask for the data processing agreement.
- Clear exit terms. Contract length, notice period, and how you export your data if you leave.
How does Axons Mobility handle white-label?
Axons Mobility covers most of that list. The rider app runs on iOS and Android under your brand in 8 languages, with ID checks with a selfie, a helmet photo check, a 20-second sobriety check, card, Apple Pay and Google Pay payments, and a wallet. Riders pay into your own Stripe account.
The operator console covers the live map, zones, pricing, passes, promos, a support desk, work orders and full double-entry accounting, and every feature is on every plan. Each connected device has its own encryption keys; read more on our security page. For prices, see our pricing page.
The quickest way to decide is to try a white-label app on your own streets before you plan a build. Axons Mobility offers a free 15-day trial on your own vehicles: a private fleet in a shared trial workspace, with your login emailed to you by an Axons Mobility person.
Frequently asked questions
What is a white-label scooter sharing app?
A ready-made rider app that carries your brand: your name, logo, colours and payments. Riders see only your brand. It usually comes with an operator console for your team and works with the connected devices on your vehicles, while the provider keeps the software running and updated.
How long does it take to build a custom scooter sharing app?
Months, with a team of engineers. You need a rider app on iOS and Android, an operator console, device integration, payments, ID checks, accounting and security, each tested on real vehicles before launch. After launch, the team stays to fix bugs and ship updates.
Is a custom sharing app cheaper in the long run?
Not automatically. A custom build avoids per-vehicle fees but adds engineer salaries, hosting, security work and app updates for as long as you run the service. It can pay off when software is your main edge and your fleet is large enough to fund a permanent team. Do the sums with real salaries first.
Will riders know my app is white-label?
They should not. A good white-label app shows only your name, logo and colours, and takes payments into your own account. Ask the provider where its own name appears, including receipts, emails and the store listing, and ask for it to be removed.
What should I demand from a white-label sharing platform?
Your brand only, your own store listing, rider payments into your own Stripe account, every feature on every plan, a trial on your own vehicles before you pay, clear answers on where rider data is stored, and clear terms for exporting your data if you leave.
