White Label Taxi App - Rider, Driver & Dispatch Platform You Own

A white label taxi app is ready-made ride-hailing software that you operate as your own brand. This one is delivered as the rider app, the driver app, a browser version for riders, the admin console and a corporate portal, with a public website on top, all carrying your name.

Launch takes 6 days of Miracuves build time, covering rebranding, deployment to your hosting and publishing of the apps from your developer accounts. Apple, Google and your payment provider run their own approval steps - store review and gateway onboarding - so those fall outside the 6 days. Anything custom is scoped and quoted on its own.

Yes. The apps run separately, driver positions sit in Redis, dispatch runs as queued jobs and websockets carry live updates. Each added city comes down mostly to hosting and configuration, and any work outside the base build is scoped in writing.

Support comes in three periods that all begin at launch: guidance on the platform covers 60 days, bug fixes get priority for 6 months, and the product keeps receiving updates for 12 months. Replies to a first message come within 2 hours, Mon-Sat, between 10:00 and 19:00 IST.

Yes. The branded clone pages on this site describe this same platform as modeled on a well-known app, while this page covers the platform underneath. Miracuves delivers every solution white-label, so your name, logo, icons and color scheme are applied at delivery.

Software like this is generally lawful to build and sell, but running a taxi service depends on licensing where you operate. The platform builds on ordinary marketplace patterns, and no code, design or content has been copied from an existing taxi brand; it launches under your own brand and rules. Choose your own name and logo, and have local counsel check which licensing, driver pay and passenger rules apply to taxi and private hire in each market. Nothing here is legal advice from Miracuves.

You supply what surrounds the software: hosting and a domain, a verified store developer account to list the apps, your branding and business information, a payment gateway already onboarded with KYC done, and keys for services such as Google Maps, an SMS gateway and Firebase. Miracuves does not apply to gateways for you or write your privacy policy and terms.

Yes. You get the full source code, unencrypted, spanning the Laravel backend, the staff console, the company portal and both React Native apps, together with the database schema, architecture notes and deployment configuration. No seat fee or per-trip charge applies.

A white label taxi app from Miracuves is priced at a fixed $3,099, live in 6 working days, with five surfaces working on delivery. Support is included and starts at launch: guidance for 60 days, plus priority bug fixes for 6 months, plus product updates for 12 months. The same base already served Aone, which reused 20 of 25 building blocks unchanged. Miracuves has built software since 2010. Its record: 9,000+ projects delivered, with 6,000+ clients served and 90+ ready-made solutions on the shelf.

Riders can log in using an OTP, Google or Apple, or look around first as a guest. Business riders flip the For Me / Business switch, then everyone picks a service tile (Cab, Parcel, Freight, Ambulance or Find Driver), sets pickup and drop-off, and chooses a vehicle with the fare and ETA shown. The system matches a driver, and the trip starts when the driver enters the rider's OTP.

Yes. A scheduled ride must be booked at least 3 hours before pickup and is released to drivers 15 minutes beforehand. When no driver accepts, the ride is canceled and the rider gets notified.

Yes. The rider app shows the driver moving on the map over websockets, with push alerts at each stage. Riders can also share a live-tracking link, which opens on the rider web app.

Riders pay by cash, wallet or any enabled gateway, 13 in all, and business rides can be billed to the company. You supply your own gateway account, onboarded with KYC finished, and the gateway processes the card details.

Yes. A rider cancels with a reason, and any fee is shown before the cancel is confirmed. Your own cancellation policy decides whether a fee applies after a driver accepts.

A white label taxi app arrives finished and rebranded in 6 days, while a custom build is scoped from scratch per project and usually takes months. Changes to ours are quoted separately.

Before booking, riders see an itemized estimate with fare and ETA for each vehicle type. Surge can vary by vehicle type, zone and time, and ride preferences like a quiet ride or AC are added into the fare.

Dispatch picks the nearest eligible driver and sends a timed offer that rings and vibrates; a decline or timeout hands the ride on.

Drivers keep a wallet, can top it up and ask for withdrawals to a payout account. Subscription plans, referrals, incentives and daily goals are built in too, and the admin sets commissions.

A dispatcher keys in phone bookings on the Ride Requests page and picks the driver manually from the ride or ride-request page. Requests are listed by status, so one desk serves phone and app customers from a single driver pool.

Dispatch offers it to the next nearest driver, or staff can assign one by hand, so the rider is still looked after.

Yes. The system refuses offline drivers and anyone already on a trip, and tells the other drivers who saw the offer that it is gone. Which staff hold the dispatcher role is your call as the operator.

Fleet managers use the driver app or the fleet login. They get a live map of their own drivers, can add or remove drivers and vehicles with their documents, and see fleet earnings by day, week or month.

Fleet owners follow earnings by day, week or month and request fleet withdrawals. You set commissions in the admin console, so each fleet's margin stays under your control.

The admin console has 52 sections: a live KPI dashboard and heat map, zones, surge and airports, coupons, driver documents, commissions, withdrawals, reports, help desk, landing-page editor, staff roles and about 70 switches.

Yes. Surge prices can follow a plain time window, or be set per zone, vehicle type and time window. Peak zones are marked on a map and show live to drivers once switched on.

Yes. Admins get live ride tracking, driver locations on a map and a heat map, and dispatchers get ride lists by status.

You can export transaction, trip, driver, coupon, zone and incentive data to CSV, Excel or PDF. Driver and fleet wallets and withdrawals sit in the console, and company invoices run on a daily cycle.

Fare commission comes first, since the first completed ride already earns it. Driver subscriptions and fleet commission follow when enough cars are on the road. Corporate billing is built in too, as are Google native ads inside the driver app, though what they earn depends on your own client deals and ad setup.

Mostly through supply and trust, not features. Drivers who joined with their documents, vehicle and payout schedule rarely walk away, and riders with past trips and saved addresses have reasons to come back. That build-up begins at launch and stays in your database. Quick dispatch and transparent fares form a second layer, since reliability is hard for others to copy.

The web and admin side runs on Laravel 11 with PHP 8.2 or newer and MySQL; Redis handles queues, cache and driver positions. Rider and driver apps use React Native 0.82 on Android and iOS, and the map provider, OpenStreetMap or Google, is switched in admin.

Yes. Both mobile apps are React Native builds for Android and iOS, and riders can also book in a browser on the rider web app. Publishing happens through your own developer accounts, and app store review lies beyond our 6-day build time.

Usually, because the white label taxi app already runs rider and driver apps, dispatch, fleets, company billing and payouts, and launches with your branding at one fixed price within 6 working days. A custom build starts from nothing. Where your operation needs something the base does not do, that change is scoped and quoted in writing and added to the same code.

A taxi platform earns from several lines at once, and each is a separate setting. You keep a commission on every completed fare, raise fares with surge set per vehicle type, zone and time slot, sell driver subscription plans, take a share from fleet owners, charge cancellation fees and bill company accounts through the corporate portal. Changing one line leaves the others untouched, so you can test pricing per city.

Open the live demo and try the rider app, driver app, corporate portal and admin console. Then send us your brand, domain, hosting, developer accounts, an onboarded payment gateway and third-party keys. We put your branding on every application, deploy them to your servers and get the app builds ready under your own developer accounts, and the taxi platform is up 6 working days after kickoff. Apple and Google store review and payment gateway approval keep their own calendars.