--- title: White Label Ride Bidding App description: "Own a white label ride bidding app with the full source code: fare bidding, rider and driver apps and dispatch on your brand. $3,099 once, live in 6 days." url: https://miracuves.com/white-label-ride-bidding-app date_modified: 2026-11-11 author: miracuves language: en_US --- Rider-Priced Taxi App · Production Ready # White Label Ride Bidding App - Fare Offers, Rides & Dispatch You Own Miracuves' ready-made, white-label ride bidding app is yours outright: a Flutter rider app and driver app for both Android and iOS, fleet-owner mode inside the driver app, one Laravel console for admins, dispatchers and fleet owners, plus your public website, running in six working days. The rider offers a fare and drivers nearby take it or propose their own; the rider then picks who drives. Bidding is switched on service by service in the admin, so it can be tried in one city without a second codebase. Permits, trip insurance and driver licensing stay yours. Partner API keys or payouts posted straight to your ledger are scoped customizations, priced in writing; most take 2-8 weeks. [Get Now**$3,099**](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0)[Check Our Demo](#demo) Launch in **6 Days** with - Source Code - Rider App - Driver App - Fleet-Owner Mode - Web Booking - Android + iOS StackFlutter · Inertia · Vue 3 · Laravel 12 · MySQL · Firebase Operator console · Dispatch*Illustrative* Switchable services**11**Roles**11**Gateways supported**24+** Sample feed of fare offers The app at work **Bidding plus fixed fares**on one fare engine and console - **11****Service Modules**taxi, delivery, rental, delivery rental, outstation, delivery outstation, shared ride, outstation shared and three bidding - **4****Dispute Priorities**targets of 2, 8, 24 and 72 hours, flagged two hours early - **0%****Revenue Share With Miracuves**no royalty on any fare, offered or fixed, or on parcels - **2****Dispatch Views**God's Eye and the heat map, inside the dispatcher console - **6****Days to Launch**and if the delay is ours, we keep going free - **$3,099****Paid Once, Not Rented**source code yours, no per-seat fee, no monthly rental Live in **six working days**, or we keep working free until you launch. Every build carries **60 days** guidance, **6 months** bug fixes and **12 months** updates.[Verify every figure](https://miracuves.com/facts/) Wave App Launched on This Base Wave App's bid-and-ride service for Bmore On Demand Technologies went live in 2024 after six working days, reusing 18 of 23 platform blocks. Fare Cards When Bidding Is Off With bidding off, fares come from zone cards: base price and distance, per-distance and per-minute charges, waiting time and cancellation fees. Tokens Instead of Card Numbers Card details go into the gateway's hosted flow and saved cards stay as tokens, never numbers; cash, wallet and wallet-plus-cash also work. **Ready to run your own ride bidding app in your city?**[Book Your Free Strategy Call](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) 6,000+ companies around the world choose Miracuves to build ![Miracuves recognised as an expertise provider](/wp-content/uploads/2024/03/Miracuves-Expertise-Provider.webp)![Miracuves official member of the Forbes Technology Council](/wp-content/uploads/2024/03/Mircuves-Official-Memeber-Forbes-Council.webp)[![DesignRush top design agencies in India badge](/wp-content/uploads/2024/03/DesignRush-Top-Design-Agencies-in-India.webp)](https://www.designrush.com/agency/profile/miracuves#reviews)[![Trustpilot top software development company badge](/wp-content/uploads/2025/04/Miracuves-TrustPilot-Top-Software-Development-Company.webp)](https://www.trustpilot.com/review/miracuves.com)[![The Manifest top managed software development company badge](/wp-content/uploads/2025/04/Miracuves-The-Manifest-Top-Managed-Software-Development-Company.webp)](https://themanifest.com/company/miracuves-solutions)[![DesignRush top software development company badge](/wp-content/uploads/2025/04/Miracuves-Designrush-Top-Software-Development-Company.webp)](https://www.designrush.com/agency/profile/miracuves#reviews)[![GoodFirms top software development company badge](/wp-content/uploads/2025/04/Miracuves-GoodFirms-Top-Software-Development-Company.webp)](https://www.goodfirms.co/company/miracuves-solution)[![Clutch top 1000 company badge](/wp-content/uploads/2024/03/Miracuves-Clutch-top-1000-company.webp)](https://clutch.co/profile/miracuves-solutions#reviews)[![Clutch top managed service provider in the US badge](/wp-content/uploads/2024/03/Miracuves-clutch-top-managed-service-provider-US.webp)](https://clutch.co/profile/miracuves-solutions#reviews) 01Watch it run Hands-On Preview ## White Label Ride Bidding App Demo - Rider, Driver, Operator & Website Every surface in this demo is the shipped build itself, open for you to explore. Miracuves seeds this demo with sample riders, drivers and trips, so every screen shows a working ride instead of an empty list. On two Android phones, load the rider app and the driver app, and send a request from one to the other. Then open the admin console and follow that same trip from the operator side. ![MXDrive rider app home screen with a live map, a Taxi and Delivery toggle and a services grid listing taxi, rental, outstation, bidding, bidding outstation and shared rides](/wp-content/uploads/2026/10/mxdrive-rider-home-screen.webp)![MXDrive rider app ride details with the route on a map, pickup and drop-off, a fare breakdown, an invoice download and an issue report option](/wp-content/uploads/2026/10/mxdrive-rider-ride-details.webp) Rider app ### Fare Bidding Taxi App - Book, Offer a Fare & Pay The rider side opens on a home screen with a map, plus Taxi and Delivery options. A services grid lists Bidding and Bidding Outstation alongside Taxi, Rental and Outstation, and each ride has a fare breakdown and an invoice. A language switch, SOS contacts, saved places, ride history and a wallet with saved cards complete the app. 1. 1Put the rider app on an Android phone 2. 2Sign in using the rider login below 3. 3Explore: Services, Ride details, Wallet Use:`9876543210 | User_321` [Rider App (Android)](https://mas.mimeld.com/apps/mxdrive-indriver-clone)[Web Booking](https://mxdrive.mimeld.com/login/user-login) ![MXDrive driver app home screen with an online toggle, a live map of nearby requests and today's earnings](/wp-content/uploads/2026/10/mxdrive-driver-home-screen.webp)![MXDrive driver app weekly earnings with trip count, wallet, total earnings and a day-by-day earnings chart](/wp-content/uploads/2026/10/mxdrive-driver-earnings-screen.webp) Driver app ### Driver App - Go Online, Respond & Earn This is the supply side, built as a full app rather than an add-on. Drivers switch online and offline with background location, and they see incoming requests with trip details, route and fare. Earnings are shown weekly, and a wallet displays the platform commission. A fleet-owner login, a leaderboard, incentives and vehicle and document records live there too. 1. 1Put the driver app on an Android phone 2. 2Sign in using the driver login below 3. 3Explore: Home, Earnings, Wallet, Vehicle Use:`9876543212 | Driver_321` [Driver App (Android)](https://mas.mimeld.com/apps/mxdrive-driver-indriver-clone)[Fleet Owner Login](https://mxdrive.mimeld.com/login/owner-login) ![MXDrive operator console ride request queue with trip status, transport type and payment method, beside the price management, geofencing and promotions menus](/wp-content/uploads/2026/05/Indrive-Clone-Rides-Request-Admin-Panel.webp) Dispatch backoffice ### Back Office - Admin, Dispatch & Settings This is where the operator runs the platform. Trip and delivery requests list their status, transport type and payment method. Operators also manage the bid-ride settings, surge, peak zones, fare cards, zones and service locations. The heat map and God's Eye are in the same place. Driver records and documents, promotions, wallets and withdrawals sit alongside them. The dispatch desk handles bookings taken by phone. 1. 1Sign in to the admin console from any browser 2. 2Sign in using the admin login below 3. 3Explore: Requests, Zones, Fares, Bid settings Try:`admin@demo.com | Admin_$321` [Open Admin Demo](https://mxdrive.mimeld.com/login/admin)[Dispatcher Login](https://mxdrive.mimeld.com/login/dispatch) ![MXDrive public website showing how a negotiated ride works in three steps: post your route and offer a fare, drivers respond, agree and go](/wp-content/uploads/2026/10/mxdrive-landing-05-bidding-steps.webp) Website & partners ### Public Website, Franchise and Agent Accounts A public website comes with the platform, and the admin CMS is where you edit it. Pages cover services, a three-step explainer on how fair rides work, and driver sign-up. Two partner logins sit behind it in the demo. A regional licensee gets a franchise console, and an agent console lets staff book rides for customers. 1. 1Visit the public website 2. 2Browse the services and fair-ride parts 3. 3After that, test the franchise or agent login Franchise:`franchise@demo.com | Franchise_321` [Open the Website](https://mxdrive.mimeld.com/)[Agent Login](https://mxdrive.mimeld.com/login/agent-login)![White Label Ride Bidding App platform shown across a laptop, tablet and phone: the MXDrive admin trip requests console, the public booking website and the rider app with taxi, rental, outstation and bidding services](/wp-content/uploads/2026/10/Indrive-Clone-Cross-Platform.webp) Watch Offers Play Out ## Fare Negotiation App Video Demo: Rider Offers, Driver Replies & the Ride The video gives a short tour of the fare-offer model this platform is built on. The rider offers a fare, drivers take it or propose their own, and the rider picks. The ride then goes ahead at the fare both parties settled on. Treat it as an orientation rather than a complete walkthrough, enough to judge whether the model suits your market. After that, use the demo above to follow the same flow through the rider app, the driver app and the admin console. Want one area covered in more depth? Book a call and we will go through it with you screen by screen. [Book Your Free Strategy Call](https://miracuves.com/schedule-consultation/) Rider and Driver Screens, Mapped Out ## Fare Bidding App Screens - Rider App, Driver App & Website Miracuves ships two Flutter ride-hailing apps with a website behind them, all running on the same Laravel API. Both apps are native builds on one Laravel API rather than web views inside a wrapper. The driver app has a fleet-owner mode too, which lets a vehicle owner manage drivers without installing anything else. The third surface is the public website, edited through the admin CMS. Use the tabs to follow a single trip. The rider selects a service and sends the ride request, and an online driver accepts it. Both see an identical route and fare breakdown, and the rider settles up from the wallet or with cash. Earnings and commission are credited in the driver wallet. Franchise, agent, dispatcher, fleet-owner and admin consoles are all live in the demo, and their screens are added here as they are captured. Rider SideDriver SidePublic Site![MXDrive rider app home screen with a live map, a Taxi and Delivery toggle and a services grid listing taxi, rental, outstation, bidding, bidding outstation and shared rides](/wp-content/uploads/2026/10/mxdrive-rider-home-screen.webp)![MXDrive rider app ride details with the route on a map, pickup and drop-off, a fare breakdown, an invoice download and an issue report option](/wp-content/uploads/2026/10/mxdrive-rider-ride-details.webp)![MXDrive rider app ride history showing completed, upcoming and cancelled trips with pickup, drop-off, vehicle and total fare](/wp-content/uploads/2026/10/mxdrive-rider-booking-history.webp)![MXDrive rider app wallet with the balance, add money and transfer actions, saved cards and recent transactions](/wp-content/uploads/2026/10/mxdrive-rider-wallet-screen.webp)![MXDrive rider app saved locations screen for home and work addresses used for quicker booking](/wp-content/uploads/2026/10/mxdrive-rider-favourite-location.webp)![MXDrive rider app account page with the rider rating and links to personal information, saved locations, documents, notifications and outstation trips](/wp-content/uploads/2026/10/mxdrive-rider-accounts-page.webp)![MXDrive rider app personal information screen with editable name, mobile number and email](/wp-content/uploads/2026/10/mxdrive-rider-personal-info.webp)![MXDrive rider app settings for theme, map appearance, layout, FAQ, privacy policy and account deletion](/wp-content/uploads/2026/10/mxdrive-rider-settings.webp)![MXDrive rider app sign-in screen with mobile number or email login and a one-time password option](/wp-content/uploads/2026/10/mxdrive-rider-login-screen.webp)9 screens · swipe →![MXDrive driver app onboarding screen explaining why background location is used to track trips and match ride requests](/wp-content/uploads/2026/10/mxdrive-driver-onboarding-screen.webp)![MXDrive driver app sign-in screen with mobile number or email login and a fleet owner login link](/wp-content/uploads/2026/10/mxdrive-driver-login-screen.webp)![MXDrive driver app home screen with an online toggle, a live map of nearby requests and today's earnings](/wp-content/uploads/2026/10/mxdrive-driver-home-screen.webp)![MXDrive driver app instant activity panel with street pickup, help centre, appear on top and preference settings](/wp-content/uploads/2026/10/mxdrive-driver-instant-activity-panel.webp)![MXDrive driver app weekly earnings with trip count, wallet, total earnings and a day-by-day earnings chart](/wp-content/uploads/2026/10/mxdrive-driver-earnings-screen.webp)![MXDrive driver app wallet showing the balance, withdraw and transfer actions, and the platform commission deducted for each completed trip](/wp-content/uploads/2026/10/mxdrive-driver-wallet-screen.webp)![MXDrive driver app ride history showing completed, upcoming and cancelled trips with pickup, drop-off and fare](/wp-content/uploads/2026/10/mxdrive-driver-ride-history.webp)![MXDrive driver app trip details with the route map, rider, vehicle, fare breakdown, invoice download and issue report](/wp-content/uploads/2026/10/mxdrive-driver-ride-details.webp)![MXDrive driver app vehicle information with vehicle type, make, model, number and colour](/wp-content/uploads/2026/10/mxdrive-driver-vehicle-info-page.webp)![MXDrive driver app personal information screen with editable name, mobile number and email](/wp-content/uploads/2026/10/mxdrive-driver-profile-info.webp)10 screens · swipe →![MXDrive public website hero with the headline fair choices and chances for all and app store download buttons](/wp-content/uploads/2026/10/mxdrive-landing-01-hero.webp)![MXDrive public website services section covering city rides, city to city trips, delivery and freight](/wp-content/uploads/2026/10/mxdrive-landing-02-services.webp)![MXDrive public website fairness section: the rider sets the fare, drivers choose their rides, and riders and drivers rate each other](/wp-content/uploads/2026/10/mxdrive-landing-04-fairness.webp)![MXDrive public website showing how a negotiated ride works in three steps: post your route and offer a fare, drivers respond, agree and go](/wp-content/uploads/2026/10/mxdrive-landing-05-bidding-steps.webp)![MXDrive public website driver recruitment section inviting drivers to join and set their own terms](/wp-content/uploads/2026/10/mxdrive-landing-06-drive.webp)5 screens · swipe →[Book Your Free Strategy Call](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) 02Proof Client Voices ## Ride Bidding App Client Feedback - Live Platforms, Results to Date Four ride-hailing founders and teams who launched on a Miracuves base, quoted word for word from our testimonials page. The first is the Wave App founder, whose bid-and-ride platform was built on this exact product; the full engagement is told in the case study below. 01Marsha Williams*M*Founder, Bmore On Demand Technologies, LLC02Aone Team*A*Founding team, Aone03caninord Team*c*Founding team, caninord04OtoKab Team*O*Founding team, OtoKabM**Marsha Williams**Founder, Bmore On Demand Technologies, LLC > “Live GPS tracking, bookings, driver and customer apps and the admin dashboard were all in place. We reshaped the workflows to our bid-and-ride model and wired in our own payments and notifications. Live inside a month on infrastructure that was already proven.” A**Aone Team**Founding team, Aone > “Fares, the city and the payment partner were ours to bring. Everything underneath - matching, live tracking, driver payouts, the operations console - came ready. From kickoff to real trips was under a month, which is the only reason we made our window.” c**caninord Team**Founding team, caninord > “We did not need a global platform, we needed one that worked in our city with our drivers. The base covered matching, tracking and payouts, so the rest was configuration. Delivered under a month at a fraction of a custom quote.” O**OtoKab Team**Founding team, OtoKab > “The base gave us matching, tracking and payouts. We reshaped dispatch around our existing driver network and their working patterns rather than forcing them onto a generic model. Live in under a month.” [**Read More Client Testimonials**Founders, CTOs and operator teams on our testimonials page](https://miracuves.com/client-testimonials/) Client Case Study ## Ride Bidding App Case Study - Wave App, Running a Bid-and-Ride Service Wave App wanted a fare-bidding ride service, and the platform already had the mechanics in place: dispatch, live tracking, payments, the admin and the rider and driver apps. Wave App's own cities, zones, service types and bid rules were what set it apart, so that is where the work went. Deployment took 6 working days. The figures here come from the published case study. It gave no outcome numbers, so this page shows none. OverviewChallengesGoalSolution by MiracuvesIn Their Words MXDriveClient Case Study **Wave App Bid-and-Ride Platform** A fare-bidding ride-hailing platform for Bmore On Demand Technologies, LLC, built on the InDriver Clone base (MXDrive) in 6 working days, with the source code transferred to Wave App’s own account. **Bmore On Demand Technologies, LLC**Client**InDriver Clone · MXDrive**Base**2024**Delivered **6 days**Working days to build on the base**18 of 23**Platform blocks reused unchanged**100%**Source code transferred to the client ![MXDrive public website showing how a negotiated ride works in three steps: post your route and offer a fare, drivers respond, agree and go](/wp-content/uploads/2026/10/mxdrive-landing-05-bidding-steps.webp)**Challenges** - A fare-bidding platform is 23 distinct pieces that all have to work before the first rider is served - Building dispatch, payments and the admin from zero would have used up the launch window - A bid-and-ride model that a fixed-fare ride-hailing flow does not cover **Goal** - Launch on mechanics already proven on other engagements - Spend the engagement on what was theirs: cities and zones, service types, bid rules - Own the source code, with a launch date in writing before work started **🛠 Marketplace by Miracuves** - Rider app: name your fare, pick a bid - Driver app: see requests, bid back - Dispatcher with manual assignment - 18 of 23 platform blocks reused unchanged - Development, staging and production environments - Full repository history transferred, with a 60-day support window Live GPS tracking, bookings, driver and customer apps and the admin dashboard were all in place. We reshaped the workflows to our bid-and-ride model and wired in our own payments and notifications. Live inside a month on infrastructure that was already proven. Marsha Williams, Founder, Bmore On Demand Technologies, LLC **Read the full case study**The whole Wave App engagement, block by block, is in the [Miracuves portfolio](https://miracuves.com/portfolio/wave-bid-n-ride-bidding-app/). [Book a Free Strategy Call](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) **Map this against your own market**We will take your cities and zones, service types and bid rules through the same three decisions Wave App made.[Book a consultation](https://miracuves.com/schedule-consultation/) 03The platform The Basics ## What Is a White Label Ride Bidding App? Miracuves sells a white label ride bidding app as a one-time purchase: ride-hailing software under your brand, hosted on a server of your choice. The rider names a price, nearby drivers can accept that price or answer with a different one, and the rider decides who drives. The fare is settled by the two people sharing the trip, not by an algorithm. Bidding is one switchable module, with fixed-fare rides, hourly rentals, intercity journeys and parcel delivery next to it, so one platform carries both pricing models in the same city. ![White Label Ride Bidding App platform shown across a laptop, tablet and phone: the MXDrive admin trip requests console, the public booking website and the rider app with taxi, rental, outstation and bidding services](/wp-content/uploads/2026/10/Indrive-Clone-Cross-Platform.webp) ### Rider and Driver Apps, Console, Website Rider and driver apps are both Flutter, and the driver app has fleet-owner mode built in. A Laravel 12 admin and dispatch console is also behind the public website and web booking. Everything runs from a single database, with eleven roles defined once for all three surfaces. ### Turn Bidding On Where You Want It Three of the eleven service modules are bidding ones: Bidding, Bidding Outstation and Delivery Bidding. Each is enabled or disabled from the admin. With them disabled, drivers see only fixed-fare offers, so trying the model in a single city does not require a second codebase. ### Adding a City Is Just Setup Airport tariffs, peak zones, surge windows, fare cards, zone types, polygon zones and service locations are all stored as records in the console. Launching a second city means configuring those records, not shipping new software. Bidding Beside Fixed Fares, One Platform ### Why the Setting Counts for More Than the Screen On a fixed-fare platform, the operator has to get the price right in every zone and at every hour, and has to explain each surge to riders who spot it. With bidding, the price talk moves to the two people on the trip. The rider states what the ride is worth, and the driver decides if it is worth taking. The operator keeps control of the pricing rules, because the commission on an agreed fare and the rules in the bid-ride settings are yours to set. Bidding can be turned off for any service with no code changes. In practice you gain a second way to price rides to try out, not a second product to maintain. ![MXDrive public website showing how a negotiated ride works in three steps: post your route and offer a fare, drivers respond, agree and go](/wp-content/uploads/2026/10/mxdrive-landing-05-bidding-steps.webp) 1. 01**Rider-offered fares, driver replies** 2. 02**Eleven services, each with an on/off switch** 3. 03**24+ gateways alongside cash and wallet** 4. 04**Fleet-owner mode built into the driver app** 5. 05**28+ languages, with right-to-left Arabic and Urdu** When comparing bid based ride hailing software, a bidding screen proves little. What counts is whether bidding and fixed fares share a single fare engine and console, and whether either can be disabled for a service without a developer. The demo shows it: the rider home screen has Bidding and Bidding Outstation tiles beside Taxi, Rental and Outstation. All in the Base Build ## White Label Ride Bidding App Features - Fare Bidding, Dispatch & Payouts Everything Miracuves lists below ships in the base build, and the demo lets you test each item. Fare bidding comes first because it is what this page is about; next come the ride services and fare types around it, then the roles that run the business day to day: dispatchers, fleet owners and drivers. Fare Bidding, Switched On Per Service01Eleven Services, Each Optional02A Complete Fare Engine for Fixed Fares03Cities, Zones and Your Choice of Map04Dispatcher Console, God's Eye, Heat Map05Fleet Owners and Corporate Clients0624+ Payment Gateways, Cash, Wallet07Driver Levels, Rewards and Subscription Plans08SOS, Ratings, In-Ride Chat and Disputes09Promo Codes, Segments and Notifications10Rider and Driver Flutter Apps11Public Website and Web Booking12Feature 01 of 12 ### Fare Bidding, Switched On Per Service This is the main reason to pick a bidding platform. The rider posts a trip with a fare offer. Drivers nearby can accept it or put forward a price of their own, and then the rider picks. The operator enables bidding service by service and manages the rules in the bid-ride settings. With bidding disabled, drivers get fixed-fare offers only. - Three bidding modules: Bidding, Bidding Outstation, Delivery Bidding - Rider picks from the drivers who reply - Guardrails managed in the bid-ride settings - Only fixed-fare offers while bidding is disabled Feature 02 of 12 ### Eleven Services, Each Optional Shared Ride, Outstation Shared Ride, Bidding Outstation, Delivery Bidding, Bidding, Delivery Outstation, Outstation, Delivery Rental, Rental, Delivery and Taxi arrive seeded, so outstation rides sit beside the rest. Every one has an on/off switch in the admin. Booking for someone else, multi-stop trips and scheduled rides come on top of them. - 11 pre-seeded service modules - Every module switched in the admin - Book now or schedule ahead - Multi-stop trips and booking for others Feature 03 of 12 ### A Complete Fare Engine for Fixed Fares With bidding off, fares come from cards defined per zone type. A card holds a base price and base distance, charges per distance traveled and per minute of the trip, waiting charges with a few free minutes, and a cancellation fee. Ride-now and ride-later are priced on separate cards. Surge windows by time, geofenced peak zones and flat airport fees can be layered on top, and each of those is optional. - Fare cards per zone type, now and later - Surge windows set by time and zone - Geofenced peak zones, flat airport fees - Rental package prices for each zone type Feature 04 of 12 ### Cities, Zones and Your Choice of Map The places the platform serves, and the prices charged there, come from service locations, polygon zones and zone types. Each trip stores its own currency and distance unit. The apps work with Google Maps, or with OpenStreetMap using Nominatim and OSRM, so the map bill is something you choose rather than something you are stuck with. - Locations drawn as polygon zones - Kilometers or miles for each trip - Choose Google Maps or OpenStreetMap - Adding a city is setup, not coding Feature 05 of 12 ### Dispatcher Console, God's Eye, Heat Map The dispatch monitor lists requests still searching, and lets staff assign, reassign or unassign a driver and book for a caller. Alongside sit a demand heat map, a peak-zone view and a live map of all drivers. The operator decides whether offers reach drivers one by one or all at once. - Manual assign, reassign, unassign - Live map of drivers plus demand heat map - Offers sent singly or to every driver - Phone bookings entered by staff Feature 06 of 12 ### Fleet Owners and Corporate Clients Vehicle owners and fleet companies have their own approved records and documents, plus a fleet dashboard, owner booking, an owner wallet and hired drivers. In the driver app they flip into owner mode, which means one install covers fleet management too. - Documents on owner and fleet records - Wallet and booking for owners - Dashboard and reports for fleets - Owner mode within the driver app Feature 07 of 12 ### 24+ Payment Gateways, Cash, Wallet Twenty-four named payment gateways come with the platform, among them Xendit, Mercado Pago, Paystack, Flutterwave, PayPal, Razorpay and Stripe. Cash, wallet and wallet-plus-cash are available too. Card entry happens in gateway-hosted flows and saved cards are kept as tokens, so card numbers never reach the platform. - Cards, cash, wallet, or wallet plus cash - Gateways keep the card numbers - Rider, driver and owner wallets - Withdrawal requests need admin approval Feature 08 of 12 ### Driver Levels, Rewards and Subscription Plans Drivers move through levels and a leaderboard, earn incentives and rewards, and can buy subscription plans the operator sells. Referral programs for riders and drivers run on conditions like ride count or earnings, which turns driver retention into settings instead of a spreadsheet. - Levels, a leaderboard, rewards - Targets that earn incentives - Subscription plans drivers pay for - Referral conditions for both sides Feature 09 of 12 ### SOS, Ratings, In-Ride Chat and Disputes Riders save SOS contacts, each trip gets a rating from both sides, and riders and drivers can chat during the ride. Disputes have four priorities, each with a response target: 2, 8, 24 or 72 hours. A dispute marks itself at risk two hours before its deadline. Support tickets and complaints run next to them. - SOS contacts saved by riders - Both sides rate each trip - Chat between rider and driver - Dispute response times of 2 to 72 hours Feature 10 of 12 ### Promo Codes, Segments and Notifications Promo codes can be limited to a service location, a user list or a segment, and they lapse automatically. Six retention segments, for example riders who churned at 30 or 60 days, point you at riders worth winning back. The platform comes with 42 seeded notification events that follow a trip from request to receipt. - Promo codes that expire by themselves - Six segments for rider retention - Batched push to a segment - 42 notification events, seeded Feature 11 of 12 ### Rider and Driver Flutter Apps Riders get an app with 40-plus screens and drivers get one with 48. Both apps are built in Flutter for iOS and Android, sharing the admin's API. The driver app holds presence in the background and records delivery proof as a signature. Each app supports 28-plus languages, and Arabic and Urdu are laid out right to left. - 48 driver screens, 40+ for riders - Drivers stay online in the background - Signature capture as delivery proof - 28+ languages, RTL for Arabic and Urdu Feature 12 of 12 ### Public Website and Web Booking Banners and onboarding screens are managed in the admin CMS together with the landing site that ships with the platform. Web booking is open to riders too, alongside the app. Tooling for renaming the app packages puts both apps under your own store identity. - Public website run from a CMS - Riders can book on the web - Admin controls banners, onboarding, theme - Rename app packages to your brand **Buyer briefing:** the software arrives complete, yet every deployment is tailored to its operator. During delivery we configure with you fare cards and cities, map keys, an SMS provider, payment gateway accounts and your Firebase project, along with whether bidding is on and the rules around it, as well as the go-live hardening described below. None of these come pre-enabled. [Book Your Free Strategy Call](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) Run It Without a Developer Team on Staff ## Ride Bidding App Admin Panel - Zones, Bid Settings, Payouts & Dispatch Miracuves puts the running of the entire platform inside a single Laravel console. Each of the eleven roles gets only the menus its permissions open up. Start with service modules and bid-ride settings, since they define the kind of ride business you operate. Day-to-day work then moves to zones and fares, dispatch, drivers and payouts. ![MXDrive operator console ride request queue with trip status, transport type and payment method, beside the price management, geofencing and promotions menus](/wp-content/uploads/2026/05/Indrive-Clone-Rides-Request-Admin-Panel.webp)![MXDrive public website driver recruitment section inviting drivers to join and set their own terms](/wp-content/uploads/2026/10/mxdrive-landing-06-drive.webp) ### What Dispatchers Take Care Of - 01 ### Service Modules and Bid-Ride Settings You decide which of the eleven service modules are active, whether bidding is on and the rules around it in the bid-ride settings. Also here: the live payment methods and the languages offered in the apps. This screen determines what sort of ride business you operate. - 02 ### Locations, Zones and Fare Cards Each city is a service location divided into zone types and polygon zones. Ride-now and ride-later fare cards, rental package prices, airport polygons, peak zones and surge windows are all records you edit, not code you release. - 03 ### Dispatch Monitor, God's Eye View Staff can see requests still looking for a driver, assign or reassign by hand, and create bookings for callers. A live map of all drivers and a demand heat map sit beside them, and the dispatcher role is limited to exactly this screen. - 04 ### Driver Onboarding, Vehicles, Documents Drivers are onboarded through document upload and approval, with vehicle types and records and expiry tracking on documents. Levels, incentives and subscriptions give them reasons to stay on the platform. - 05 ### Driver Wallet and Payouts, Plus Commission Rider, driver and fleet-owner wallets; withdrawal requests the admin can approve or decline; commission set as a flat amount or a percentage; and the commission owed on cash-paid trips recovered from the driver balance. - 06 ### Disputes, Support Tickets, SOS Disputes carry priorities and SLA deadlines, alongside support tickets, complaints and SOS contacts. Each canceled trip also keeps its cancellation reason, whether the canceller was the rider, the driver, a dispatcher or the system. - 07 ### Promos, Referrals and Segments The 42 notification events that the apps send, retention segments with push campaigns, referral conditions for riders and drivers, and promo codes limited by location, user list or segment. - 08 ### Reports and Exports Seven report families: franchises, fleets, finance, owners, driver duty, drivers and users. Also available: the trip-level ride report, a pricing-audit export, an event-log export and invoice PDFs. ### Owner-Operated Fleets and Corporate Accounts Owners and fleet companies hold full accounts of their own, with documents, drivers and a wallet. So corporate mobility and owner-operated fleets can run alongside individual drivers on one platform. - Approval for owner and fleet records - Drivers hired under an owner - Wallet and booking for owners - Reports for owners and fleets ### Staff Roles and Permissions Eleven roles run from super admin through dispatcher and fleet owner to franchise owner, and 134 permission keys decide which sidebar entries each one sees. Everyone gets the section of the platform that their job requires. - 11 roles included - 134 permission keys, sidebar-gated - Dispatchers see dispatch screens only - Virtual login to assist a user **Running several dispatchers?** Your roles turn into your operating model during delivery. Decide who can see the dispatch board, who releases a withdrawal, who may edit a fare card and who signs off a driver’s documents; those decisions are mapped onto the permission keys, not left at the defaults. [Book Your Free Strategy Call](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) 04Package contents and cost The Complete Package ## What's Included - Ride Bidding App Source Code, App Builds & Hosting A single Miracuves price covers each component in this list. The software sends nothing home to us, rides are never metered, and after go-live Miracuves charges no ongoing fee. ![MXDrive public website hero with the headline fair choices and chances for all and app store download buttons](/wp-content/uploads/2026/10/mxdrive-landing-01-hero.webp)01 ### The full codebase is yours Delivery covers the Laravel admin, the API, the website and both Flutter apps as one complete repository, not a bundle of compiled builds. None of it is hidden in encrypted modules. - Source code delivered for every surface - Complete repo history moved to your account - No fee per ride or per driver - No runtime license renewals ![MXDrive operator console ride request queue with trip status, transport type and payment method, beside the price management, geofencing and promotions menus](/wp-content/uploads/2026/05/Indrive-Clone-Rides-Request-Admin-Panel.webp)02 ### The Admin and Dispatch Back Office A single Laravel 12 console built with Inertia and Vue 3 serves admins, dispatchers and fleet owners. Also included: Dispatcher Pro plus franchise and agent consoles, with access controlled by eleven roles and 134 permission keys. - Service toggles and bid settings - Zones, fares, surge windows, airports - Dispatch board, God's Eye, heat map - Exportable reports 03 ### Rider-Side App Built in Flutter for iOS and Android, the rider app has 40-plus screens: booking, services, fare offers, saved places, ride details, wallet, history, SOS and settings. - 40+ screens for riders - Book by bidding or at a fixed fare - Pay by card, cash or wallet - 28+ languages, RTL included ![MXDrive rider app ride details with the route on a map, pickup and drop-off, a fare breakdown, an invoice download and an issue report option](/wp-content/uploads/2026/10/mxdrive-rider-ride-details.webp)04 ### Driver-Side App A 48-screen Flutter app: online status with background presence, incoming requests, trip flow, wallet, earnings, documents, incentives and fleet-owner mode. - 48 screens for drivers - Bidding screens and an offer inbox - Earnings, wallet, withdrawal requests - Fleet-owner mode included ![MXDrive driver app weekly earnings with trip count, wallet, total earnings and a day-by-day earnings chart](/wp-content/uploads/2026/10/mxdrive-driver-earnings-screen.webp)05 ### Eleven Seeded Services Bidding, delivery, outstation, rental, taxi and shared-ride modules come seeded, and the admin switches each one on or off. - Bidding in three modules - Parcel delivery, proof by signature - Rental packages by the hour - Rides scheduled or multi-stop 06 ### Database Schema Its MySQL-compatible schema is generated by 413 migrations. Zones use spatial columns, and bill, quote and pricing-audit records sit behind each fare. - 413 migrations rather than a dump - Spatial zones with geohash - Records of quotes and final fares - Seeders so the first run works 07 ### Handover Documentation Ten documents arrive with the code: the whitepaper, technical dossier, feature catalog, API collection, schema reference, ERD, PRD, solution overview, the developer-facing security handbook and the VAPT compliance review. - Developer security handbook, VAPT review - API collection your engineers can use - Schema and ERD documents - Notes on deployment and setup 08 ### Hosting and Your Branding Translated app strings, renamed app packages and the CMS-driven website arrive with your logo, colors and app theme. The installation is single-operator and runs on a server you control. - Your branding and app theme - Website managed in the admin CMS - Renamed app packages for your stores - Runs on infrastructure you control **A frank note:** Miracuves, an app development company, hands you a complete platform along with the documents that an engineer or reviewer will request. A running business is not part of the delivery. You open your own store accounts, map keys, SMS provider, gateway merchant accounts and Firebase project, and working through the go-live list found in the security section takes genuine effort. [Book Your Free Strategy Call](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) Pricing in Plain Terms ## How Much Does a White Label Ride Bidding App Cost in 2026? The ride bidding app development cost is one fixed figure for the core platform. That single figure buys the full source code, deployment on your own server, and every surface: rider app, driver app with fleet-owner mode, admin and dispatch console, and the public website with web booking. Miracuves takes no per-ride fee and there is no runtime license. Dispatcher Pro, Agent and Franchise modules come in the price as well. Third-party charges (app stores, maps, SMS, payment gateways, Firebase) are billed by those providers directly. Picked by most operators Professional Ride Service Launch Kit **$3,099**one-time payment Live in 6 days **Best fit:** new ride services, taxi operators moving online and regional mobility brands The delivered build matches the demo you tried, carrying your branding and hosted on servers you control. [Get Started](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) Enterprise Custom, Multi-City & Large-Scale**Custom**quoteTimeline depends on the final scope **Best fit:** operators with fleets, franchise networks and mobility groups spanning several cities Order a custom build fitted to your circumstances and to what your business needs. [Ask for a Quote](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) Still deciding? **Unsure which route suits you?** Talk to our team. We begin with your goals, timeline and budget and recommend the option that suits you. Expect plain advice, not a sales pitch. - Free 30-minute call - We answer within 24 hrs - No pressure and no obligation [Chat on WhatsApp](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0)[Book a Meeting](https://miracuves.com/schedule-consultation/)No obligation to buy. Development Cost ### White Label Ride Bidding App Development Cost in 2026 Miracuves sets white label ride bidding app development cost at $3,099, paid once. It buys the complete repository: Laravel console and API, website and both Flutter apps, plus Dispatcher Pro, Agent and Franchise consoles, standing on your own hosting after six working days, free of any per-ride or per-driver fee. **$3,099** Paid once **6 working days** Rebranded and live **0%** Revenue share What moves your total sits outside the software invoice - Your server and domain - Apple and Google developer accounts - Map access, SMS and email providers - Firebase and payment gateway accounts, with their own fees Partner API access, ERP links and other extras get a written quote first, and most take two to eight weeks. Compare Your Options ## Ready-Made White Label Ride Bidding App vs Custom Development vs SaaS A fare-bidding service reaches the road three ways: buy it finished from Miracuves, commission an agency, or subscribe to a hosted ride tool. Here they are, row by row. | Criteria | MiracuvesReady-Made White Label Ride Bidding App | Custom Development | SaaS | | --- | --- | --- | --- | | Launch time | Running on your own server in 6 working days | Quoted in writing, often 2-8 weeks of work | Quick to sign up, slow to make your own | | Upfront cost | $3,099 once, every module included | Set by a written quote after scoping | A monthly subscription from day one | | Source code ownership | The whole repository with history, yours to keep | Depends on the contract you sign | Stays on the provider servers | | Customization | Rebrand and tune bidding rules whenever you like | Built to your brief, priced per change | Limited to the settings screens offered | | Ongoing fees | No per-ride, per-driver or license fees | Hosting plus any maintenance you agree | Recurring fees, often per driver or ride | | Branding & app-store listing | Rider and driver apps listed under your name | Your name, once the apps are finished | Provider branding may stay visible | | Best for | Operators launching negotiated fares quickly | Unusual rules no ready base handles | Short pilots before committing | Same product, other editions: [inDrive Clone](https://miracuves.com/indrive-clone/) · [Browse all Ride-Sharing solutions](https://miracuves.com/solutions/ride-sharing/) Ownership ## What White Label Means on This Platform The phrase white label ride bidding app is stretched to cover rented dashboards, while Miracuves means source, brand and servers all yours. On this platform the line is plain: you hold the source code, the brand and the servers. **What carries your brand** Your logo, colors and app theme go onto the rider app and the driver app, and the package-rename tooling puts both under your own store identity. The public website, its banners and the onboarding screens are edited from the admin CMS, and the app strings come translated. The whole installation is single-operator and is hosted on your own server. **What you own for good** You own the full repository, history included: the Laravel 12 console and API, the website, the Flutter rider app and the Flutter driver app, plus the ten-document technical set. No module is encrypted. Miracuves takes no share of any ride and charges no runtime license, per-driver fee or per-ride fee. **What white label does not mean** You are buying code, not renting a seat: nothing here lapses when a subscription stops. The Firebase project, payment gateways, SMS provider, map keys and your Apple and Google developer accounts are registered to you and billed to you. Penetration testing and admin-login hardening get a place in the go-live plan we draft with you, while transport licensing and store approval run through your own entity. Where It Fits ## Ride Bidding Use Cases - City, Intercity, Parcels & Fleets 01**Rider-Offered City Fares**02**Intercity and Outstation Rides**03**Parcel Delivery at an Offered Price**04**Fixed Fares for Riders Who Want One**05**Fleet and Corporate Travel**06**Hourly Hire and Rental Packages***Bidding**City rides***Rider-Offered City Fares** This is the main scenario the platform is built around. Miracuves' main scenario starts with a rider who posts a cross-town trip and names the fare they would pay. Nearby drivers can take it, or put forward a different fare, and the rider picks. The trip goes to the chosen driver at the agreed fare, and the operator earns its commission on that fare. 01![MXDrive rider app home screen with a live map, a Taxi and Delivery toggle and a services grid listing taxi, rental, outstation, bidding, bidding outstation and shared rides](/wp-content/uploads/2026/10/mxdrive-rider-home-screen.webp)*Bidding Outstation***Intercity and Outstation Rides** A flat per-kilometer rate rarely feels fair to both sides on a long trip. With Bidding Outstation the rider offers one price for the whole journey, drivers accept it or quote their own, and the rider settles on a driver before departure. The driver app shows outstation requests on dedicated screens. 02![MXDrive driver app trip details with the route map, rider, vehicle, fare breakdown, invoice download and issue report](/wp-content/uploads/2026/10/mxdrive-driver-ride-details.webp)*Delivery Bidding**Proof***Parcel Delivery at an Offered Price** Couriers price every job differently. Delivery Bidding puts goods through the same fare offer flow as rides, and the driver app takes a signature as proof of delivery at the drop-off. 03![MXDrive public website services section covering city rides, city to city trips, delivery and freight](/wp-content/uploads/2026/10/mxdrive-landing-02-services.webp)*Taxi**Rental**Airport***Fixed Fares for Riders Who Want One** Some riders want the price on screen and a car within minutes. Taxi and Rental price rides from fare cards set by zone type, with airport fees, peak zones and surge, alongside the bidding modules. 04![MXDrive operator console ride request queue with trip status, transport type and payment method, beside the price management, geofencing and promotions menus](/wp-content/uploads/2026/05/Indrive-Clone-Rides-Request-Admin-Panel.webp)*Owners**Fleets***Fleet and Corporate Travel** A fleet company or corporate client can book and pay through an owner account that has its own wallet and reports. Drivers work in owner mode inside the standard driver app. 05![MXDrive driver app wallet showing the balance, withdraw and transfer actions, and the platform commission deducted for each completed trip](/wp-content/uploads/2026/10/mxdrive-driver-wallet-screen.webp)*Rental**Packages***Hourly Hire and Rental Packages** A car and driver booked for a fixed block of hours or kilometers. Package fares are set per zone and include free distance and free minutes. The rider books it in the same app used for city rides. 06![MXDrive rider app ride history showing completed, upcoming and cancelled trips with pickup, drop-off, vehicle and total fare](/wp-content/uploads/2026/10/mxdrive-rider-booking-history.webp) Business Model ### White Label Ride Bidding App Business Model: Three Ways to Run It One platform serves three kinds of operator, and each leans on bidding, fixed fares and the fleet tools in its own way. Rider-priced city service A startup launches a taxi brand where the rider offers a fare, nearby drivers accept it or answer with a fare of theirs, then the rider decides who drives. Taxi company going digital An established cab firm keeps fixed fares for regulars, trials bidding in one zone and learns from reports which model riders favor. Fleet and intercity operator A vehicle owner manages drivers through fleet-owner mode in the driver app, and prices long outstation trips and parcel runs by offered fare. Zones, services and bidding rules are all settings, so the code stays the same in every model. If you cannot tell which pricing model your city prefers, run both together. Offered fares suit riders who like to set the price themselves; fixed fares suit airport runs and riders in a rush. The reports show how each performs before you commit. Each service is a module, so one deployment can launch with city rides only. Rentals, intercity rides or parcels can be switched on when your operations team is ready, with no second platform to set up. [Book Your Free Strategy Call](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) Industries ## Sectors a Ride Bidding Platform Serves Ride-hailing is the core, but bid based ride hailing software of this kind fits any business that matches a person or a parcel to a driver and agrees a price. Eleven service modules let one deployment run city rides, intercity rides, hourly rentals and deliveries - one system, not four. The same loop applies wherever a trip must be priced, assigned, tracked and paid. What differs from market to market is which cities you serve, which services are switched on, and whether riders offer a fare or pay a fixed one. All of that is configuration; the code stays the same. 1. 01Ride Services 2. 02Taxi & Cab Companies 3. 03Intercity Trips 4. 04Parcels & Couriers 5. 05Rentals & Hourly Hire 6. 06Fleet Owners 7. 07Business Travel 8. 08Airport Runs 9. 09Tourist Transfers 10. 10Phone-Booking Dispatch 11. 11Franchise Groups 12. 12Agent Bookings 06Behind the screens Fare Offer to Payout ## How the White Label Ride Bidding App Works - Offer, Choose, Ride & Get Paid In Miracuves' ride bidding app, six steps carry a trip from fare offer to driver payout: the rider offers a fare, one driver is picked, the ride runs and the money lands, all under your operator rules. ### The Trip Cycle 1. ![MXDrive rider app home screen with a live map, a Taxi and Delivery toggle and a services grid listing taxi, rental, outstation, bidding, bidding outstation and shared rides](/wp-content/uploads/2026/10/mxdrive-rider-home-screen.webp)1**Rider Offers a Fare for the Trip** The rider enters pickup and drop-off, chooses a service like Bidding or Bidding Outstation, reads the platform's fare estimate, then posts the trip with the fare they offer. - Pickup, drop-off and added stops - Estimated fare shown before posting - Bidding and fixed-fare services together - Book for later or for another person 2. ![MXDrive driver app home screen with an online toggle, a live map of nearby requests and today's earnings](/wp-content/uploads/2026/10/mxdrive-driver-home-screen.webp)2**Drivers Nearby Take the Fare or Name Their Own** Online drivers in the zone receive the request either one by one or all together, depending on the operator's setting. Each driver sees the route and the rider's offer, then takes it or proposes a different fare. - Sent to drivers singly or all at once - Route and offer visible up front - Take the fare or propose another - Operator rules for how offers run 3. ![MXDrive rider app ride details with the route on a map, pickup and drop-off, a fare breakdown, an invoice download and an issue report option](/wp-content/uploads/2026/10/mxdrive-rider-ride-details.webp)3**Rider Picks a Driver by Price, Rating or Vehicle** From the drivers who responded, the rider picks one by price, rating and vehicle. The trip then goes to that driver at the fare agreed. When bidding is switched off for a service, the request goes out at a fixed fare instead. - Pick by price, rating and vehicle - Driver assigned at the agreed fare - Remaining offers cleared - Fixed-fare requests where bidding is off 4. ![MXDrive driver app trip details with the route map, rider, vehicle, fare breakdown, invoice download and issue report](/wp-content/uploads/2026/10/mxdrive-driver-ride-details.webp)4**Pickup, Trip Code and Live Ride Tracking** The driver reaches the pickup, the ride starts once the rider's code checks out, and both apps display the route live. For deliveries the driver collects a signature at the drop-off. - Arrival, start and completion events - Start confirmed with a trip code - Route live in both apps - Signed proof on deliveries 5. ![MXDrive rider app wallet with the balance, add money and transfer actions, saved cards and recent transactions](/wp-content/uploads/2026/10/mxdrive-rider-wallet-screen.webp)5**Payment by Card, Cash or Wallet, Then Ratings** The rider settles by card, cash, the wallet, or part wallet and part cash. The rider gets an itemized invoice, both sides rate each other, and the bill lists commission to the platform and the driver’s portion as separate lines. - Cards, cash, wallet or a blend - Invoice showing the fare breakdown - Both sides rate after the trip - Commission logged on every ride 6. ![MXDrive driver app weekly earnings with trip count, wallet, total earnings and a day-by-day earnings chart](/wp-content/uploads/2026/10/mxdrive-driver-earnings-screen.webp)6**The Driver Withdraws Ride Earnings** Earnings go into the driver wallet with commission visible, the driver asks for a withdrawal, and the admin approves the payout. When a trip is paid in cash, the commission due is taken from the driver’s balance. - Earnings viewed by week - Wallet showing commission - Admin signs off on withdrawals - Cash-trip commission recovered Fare Offer FlowchartRider Posts Trip & FareDrivers Take It or ProposeRider Chooses a DriverTrip Code & PickupLive TripPayment & RatingsDriver Payout Inside the Build ## Fare Bidding Taxi App Architecture & Server-Side Logic [Book Your Free Strategy Call](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) 1. Layer 01 ### Three Surfaces on One Laravel Core One Laravel application on one database runs the admin panel, the dispatcher console, the website and the API both apps call, so a trip, a driver or a payment is the same record wherever it appears. 2. Layer 02 ### Each Fare Keeps a Quote and a Final Each trip stores its quote and two pricing-audit records, one at the estimate and one at the final fare. The bill separates platform commission from the driver’s share, and a fare dispute is settled from those records. 3. Layer 03 ### Offers Follow Operator Rules The admin decides whether drivers receive a request singly or all together. Drivers also have an inbox that holds several offers, and none of this needs a code change. 4. Layer 04 ### Firebase Runs Live, MySQL Keeps Records Offers and driver presence, the live side of a trip, travel through Firebase, and MySQL holds the permanent record. Without Firebase set up, booking, the trip lifecycle and settlement continue over HTTP. 5. Layer 05 ### 134 Permission Keys Eleven roles are mapped to 134 permission keys. A dispatcher sees dispatch, a fleet owner sees only their fleet, the super admin sees everything, and the same Laravel app enforces it. 6. Layer 06 ### Cron and Queue Drive Dispatch Scheduled jobs on a supervised queue worker handle driver assignment, canceling stale requests, promo and subscription expiry, and document reminders. That is why every deployment includes cron. Stack Details ## Ride Bidding App Source Code - Laravel, Vue, Flutter, MySQL & Firebase Miracuves chose a conventional stack deliberately, because a ride operator needs developers it can hire locally. Laravel and Vue power the console and website, Flutter builds both apps, MySQL stores the records and Firebase handles the live side of each trip. Talent for all of these is easy to find in most places. 01Console & Website02API03Data04Mobile05Realtime06Maps ### Console, Dispatch & Website Laravel 12 Vue 3 Inertia PHP 8.2+ - Admin, dispatch and website in one app - Console users sign in via Jetstream sessions - Bootstrap and Vite for the front end - Pages and banners edited in the admin CMS ### Mobile API 9 Route Families Sanctum Tokens /api/v1 - Routes for auth, user, driver, request and payment - Both apps use Sanctum tokens - - JSON responses shaped with Fractal ### How Data Is Stored 413 Migrations MySQL / MariaDB Spatial - Seeders ship with 413 migrations - Zones use spatial columns and geohash - Redis supported; database queue is the default - S3-compatible supported, local disk default ### Rider and Driver Apps Flutter Dio BLoC Drift - iOS and Android apps for riders and drivers - State in BLoC, networking in Dio, storage in Drift - Driver presence runs as a background service - Gateway payments open in an in-app web view ### Realtime & Push FCM Firebase Realtime Database - Driver presence and live offers - FCM carries push notifications - Phone sign-in via Firebase - Trips still run over HTTP without it ### Maps & Providers 24+ Gateways 9 SMS Google Maps or OpenStreetMap - Google Maps, or OSM tiles from Mapbox, Thunderforest or Stadia - OSRM routing and Nominatim geocoding - Twilio, Infobip, Msg91 plus six other SMS providers - Stripe, Razorpay, PayPal plus 21 other gateways **Why we chose this stack:** it is ordinary on purpose. You can hire Laravel, Vue and Flutter developers in each market you target, most hosting teams already run MySQL, and the apps do not change whichever map layer you use, Google Maps or OpenStreetMap tiles. [Book Your Free Strategy Call](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) Growth Planning ## Scaling a Bid Based Ride Hailing Platform - Dispatch Jobs, Live Offers & Zone Data Ride demand comes in spikes: the commute, weekend nights and bad weather all hit together. Three things must keep pace, and they are what you size infrastructure for: driver assignment, live offers and the map. Whether the platform feels fast depends mostly on driver assignment. Assignment relies on cron and a supervised queue worker, so the deployment checklist lists both as essential. Without cron it stalls, even though the admin panel looks fine. Firebase, not the application server, carries live offers and driver presence. The second-by-second traffic of a busy hour goes to infrastructure designed for it, and MySQL stores the records. Out of the box, the install is one server using local disk storage and a queue held in the database, which is enough to launch. Extra application servers call for S3-compatible object storage for files and Redis for the queue and cache. Both are supported, and each is planned as a separate piece of work. Assignment puts more load on the database as fleets grow. The documents advise planning capacity once you pass roughly 500 vehicles; sharding assignment is a customization, not a default setting. 01 ### Driver Matching Jobs Regular rides are matched by scheduled assignment jobs, and unmatched requests that have gone stale are canceled every minute. That is processor and database load that scales with the fleet, so size for it. 02 ### Live Offers and Driver Presence Firebase Realtime Database carries offers, presence and live trip data, which keeps the busiest traffic away from the application server. 03RouteGeocodeTiles ### Maps and Location Quota Each route, geocode and map tile counts as a call to the provider. At volume a Google Maps quota turns into a cost line, whereas the OpenStreetMap stack shifts that cost to the tile source you pick. 04Promo expiryDocument remindersRequest cleanup ### Scheduled Housekeeping Scheduled commands expire promos and subscriptions, send document reminders and clear old requests. The scheduler is therefore a core part of the platform, not an optional extra. 05 ### Zones and Spatial Queries Zones, peak zones and airports are stored as spatial geometry with geohash lookups, which makes locating a pickup's zone an indexed query instead of a scan. 06 ### Media and Documents Every signup adds driver, vehicle and owner documents. By default they sit on local disk, and for anything larger than one server they move to private S3-compatible object storage. Map calls are the cost that creeps up at volume. Each route, geocode and live map view goes to the map provider. This is why the platform also supports OpenStreetMap with Nominatim and OSRM in place of a metered map API. **An honest limit:** this is a description of how the platform is built; it is not measured throughput. The documentation gives no request-rate or uptime figures and we quote none; we run load tests at the volumes you expect as part of delivery. [Book Your Free Strategy Call](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) 07Security and your duties Open to Review ## Ride Bidding App Security - Documented Controls, Configuration & Go-Live Hardening Security claims here rest on documents, not on assurances. The platform ships with a security handbook for developers and a VAPT compliance review, which give your security team something concrete to assess. The cards below set out the items it assigns to you. 1. **01** · Documented ### Written Down, Not Just Claimed The technical set has ten documents, among them a VAPT compliance review laid out as a control catalog and a security handbook written for developers. Your security team gets them to assess, and this page reports what they leave open instead of calling the platform passed. - **No Pen Test, No Certification:** The VAPT document reviews source code, not your live deployment. Nothing here is certified to SOC 2 or ISO 27001, and PCI DSS and GDPR certification are not claimed either. Before launch we advise getting an outside penetration test done, and we will help with it. 2. **02** · Sessions ### Sessions, Tokens and Throttling Console users log in through Laravel Jetstream sessions while the apps authenticate with Sanctum tokens. Riders and drivers verify with a mobile or email OTP or by social login, and the API is throttled across five rate-limit tiers. - **Production Settings Before Launch:** The example environment ships with developer defaults such as session cookies that are not secure, debug output and permissive CORS. Each one is changed to its production value, and trusted proxies are configured, before the first real user signs in. 3. **03** · Payments ### Card Numbers Stay Off the Platform Card details are entered on gateway-hosted pages or an in-app web view, and a saved card exists only as the gateway token, so no card number ever touches MXDrive forms or its database. - **Firebase Rules and Webhook Signing:** The review rates two integration mistakes High: a trial Firebase project whose rules were left open, and a gateway webhook that is never verified. You lock the rules and check each gateway’s signing secret in your own accounts. 4. **04** · Roles ### 134 Permission Keys Across Eleven Roles The roles include super admin, dispatcher, fleet owner, franchise owner and agent, plus six more. Each sees only the menus its permission keys allow, and a virtual login for support stays within the same permission model. - **Admin Access and Least Privilege:** Place the admin console behind network controls, trim admin roles to what each person needs, and add multi-factor login, which the base build lacks, if your policy calls for it. 5. **05** · Records ### Records That Stand Up to a Complaint Trip events from request to completion, cancellation reasons recorded per rider, driver, dispatcher or system, pricing-audit records at the quote and the final fare, and disputes tracked against SLA deadlines. - **Encrypted Backups, Tested Restores:** By default backups are unencrypted, and soft-deleted records remain inside them. Encryption, a restore that has been tested and a retention policy matching the erasure commitments you make are put in place during go-live. 6. **06** · Launch ### Items the Review Assigns to You The review ends with a residual-risk register of twenty items. Eight are labeled High and none Critical, and all eight are configuration or operations work that falls to the operator. They make up the go-live work in these cards and are not unexpected finds saved for later. - **Demo Auto-Approval and KYC Files:** Driver and owner documents are taken off the public disk and put in private storage, and the demo jobs that approve documents automatically every five minutes are turned off. Document review then goes back to a person. The platform carries the controls a ride operator is usually asked about: authentication through sessions for the console and tokens for the apps, API rate limits, card entry kept on gateway-hosted flows, eleven roles mapped to 134 permission keys, plus trip, fare and dispute records that hold up in a complaint. [Take Security & Compliance Questions to Us](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) Licensing in Plain Terms ## White Label Ride Bidding App Compliance - Software Scope, Local Licensing and Your Obligations A ride bidding platform is software, and software never doubles as a permit for a ride-hailing business. The platform layer from Miracuves covers apps for riders and for drivers, an admin and dispatch console, handling of fares and offers, driver and vehicle records whose uploaded documents are reviewed, payments via the gateways you connect, and logs covering trips, cancellations and disputes. Regulation applies to several activities: operating a taxi, courier, private-hire or ride-hailing service, insuring trips, licensing drivers and their vehicles, and for holding or paying out customer funds. Responsibility for them lies with your company, under whatever permits your city or country demands, or with licensed partners you hire. Miracuves is neither, and the software cannot act as a transport operator or a payment institution. **Card data stays with your payment gateway, held there as tokens, never on the platform.** Card details are typed into pages hosted by the gateway or into in-app web views, with saved cards kept as gateway tokens. That keeps card numbers off the platform and shrinks what an assessor must examine, and card fields stay on the gateway side in every flow. ### What the Software Covers Included: eleven service modules covering bidding and fixed fares, plus rider and driver apps and an admin and dispatch console. Zones, fare cards, driver and vehicle documents with an approval step, cash and wallet payments and 24+ gateway integrations are in too. So are trip, fare, cancellation and dispute records. All of it arrives as source code and runs on your own server. ### What Only a Permit Allows The right to run a courier, taxi, private-hire or ride-hailing operation; licenses for your drivers and vehicles; insurance that covers a trip; and whatever fare rules your city sets. That authority belongs with your own company, or with a licensed partner you work with. No software can replace it, and the platform supplies tools, not compliance. ### Driver Checks and Customer Money Driver documents and their approval are recorded on the platform, while background checks are carried out by you or a screening provider of your choice. Wallet balances are customer money. If your market regulates stored value, route it through a licensed payment partner, or accept card and cash only. ### Local Rules Decide the Route Rules differ by market. In the US, transportation network companies answer to individual states, and in California the regulator is the CPUC. London private hire operators are licensed by TfL. India’s states each adopt the Motor Vehicle Aggregator Guidelines, and Dubai licenses ride-hailing through the RTA. Privacy law, such as India’s DPDP Act or the GDPR, applies too. Confirm the right route with transport counsel or a licensed partner; legal, licensing and regulatory advice sits outside what Miracuves provides. 08Extend the platform Included in the base**MXDrive** - Apps for riders and drivers - Fare bidding and fixed fares - Eleven services as modules - Admin and dispatcher console How add-ons proceed 1. 1**Harden and connect first** The first two items come before any real money moves. 2. 2**Quoted per request** Every request gets its own written scope and fixed price. 3. 3**Delivered into your repo** As with the core product, you receive it as source code that is yours. [Ask Us About Custom Modules](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) Go Further ## Ride Bidding App Add-Ons - Hardening, Providers, Integrations & Assurance Everything listed above is already in the base package. What follows is scoped together with you: go-live work no deployment carrying real rides should skip, integrations the base build leaves to you, and assurance work enterprise buyers ask for. Dispatcher Pro, Agent and Franchise are not listed because the package includes them. - Needed before go-live ### The Go-Live Hardening Work Production settings replace the example defaults, the admin console goes behind network controls, Firebase rules are locked, gateway webhooks are verified, driver documents move to private storage, demo auto-approval is turned off and backups are encrypted. Security · Go-Live Check - Needed before go-live ### Live Provider Connections Each of these goes under your own accounts: a Firebase project that carries live offers and push, the payment gateways with their webhooks, SMTP for email plus an SMS provider for OTPs, plus map access through Google Maps keys or, instead, the OpenStreetMap stack. Providers · Live Setup - Channels & operations ### API Access for Partners API keys for machines and an OpenAPI export, for partners that need to plug into your platform. The base build signs apps in via user tokens and ships a ready API collection; partner-grade access is scoped custom work. Integration · Partner Access - Assurance & enterprise ### ERP and Accounting Integration Bills, payouts and withdrawals can flow straight into your ledger or accounting software. The base build exports reports and invoices, and posting them directly into a ledger is a customization scoped to the system you actually use. Integration · Finance - Assurance & enterprise ### Monitoring, Alerts and Log Shipping Uptime monitoring, alerting and log shipping to your SIEM come as an add-on. We connect them to your operations team before growth arrives, and most operators book it ahead of their first busy weekend. Operations · Monitoring - Channels & operations ### Store Release Both Flutter apps, Android and iOS, are built from the source you receive and renamed to your own package identity. Our team can also run release management, signing, store listings and background-location review for you, with each store keeping its own review calendar. Mobile · Store Submission - Assurance & enterprise ### Admin SSO and Multi-Factor Login Outside the base build. Institutional and corporate buyers usually want multi-factor login on the admin console, or the console placed under their identity provider, and that is delivered as a defined customization. Enterprise · Console Access - Assurance & enterprise ### Support for External Penetration Tests The VAPT document is a review of source code and does not test your deployment. We work alongside an outside penetration test ahead of launch, fixing whatever it turns up with the handbook and review the platform ships with. Assurance · Pen Testing Other Ride-Hailing & Mobility Platforms ## Not Sure a Fare Negotiation App Fits? Browse the Wider Mobility Lineup Bidding is one way to price rides. If riders in your market expect a fixed fare upfront, or rides are only one service inside a wider app, the platforms below may suit you better. ![Commuter opening a car door at the kerb, the Uber Clone ride-hailing use case](/wp-content/uploads/2025/02/successful-young-asia-businesswoman-commuter-in-fa-2021-09-04-11-40-20-utc-768x512.webp)01Pick it if: The platform should set every fare**Uber Clone** A taxi platform that quotes a fixed fare before booking, matches drivers automatically, tracks the trip live and keeps a history. It fits cities where riders want the price shown and a car nearby fast. [Explore Solution](https://miracuves.com/uber-clone/)![Bolt Clone admin dashboard with trip counts, earnings chart and cancellation figures](/wp-content/uploads/2025/10/Bolt-Clone-Admin.webp)02Pick it if: Speed and plain fares win your city**Bolt Clone** A ride-hailing build covering live GPS, driver matching, payments, fare calculation and admin control, aimed at a quick launch in a crowded city. [Explore Solution](https://miracuves.com/bolt-clone/)![Lyft Clone rider and driver app screens on stacked phones](/wp-content/uploads/2025/02/PhoneMockup-9-1.webp)03Pick it if: Riders want a fare estimate first**Lyft Clone** A ride-hailing build with payments and ratings, fare estimates, live tracking and driver matching, shaped around a rider experience of quoted, fixed fares. [Explore Solution](https://miracuves.com/lyft-clone/)![Passenger using a phone in the back of a car, the Grab Clone super app use case](/wp-content/uploads/2024/01/young-man-using-smartphone-in-car-2021-09-24-04-15-17-utc-scaled-1-768x512.webp)04Pick it if: Rides are only part of your plan**Grab Clone** One super app for booking rides, ordering food and more under a single account, for operators planning beyond rides. [Explore Solution](https://miracuves.com/grab-clone/)[Catalog**See all 90+ solutions**](https://miracuves.com/solutions/) 09The revenue case Where the Money Comes From ## White Label Ride Bidding App Revenue Models - Subscriptions, Commission, Channels & Premiums On a Miracuves platform, rider and driver settle the fare between them and the operator earns on a price it never had to set. Commission on that agreed fare is the base. Subscriptions, fixed-fare premiums, rentals, deliveries and partner channels sit beside it as extra income lines. Every rate in this section is yours to choose. Miracuves takes no share of any ride and charges nothing per driver or per trip. Your Firebase, map, SMS and payment gateway providers bill you separately for their own services. 1. 01 ### Commission on Each Agreed Fare The base of the model is a platform share of each completed ride, set as a flat amount or a percentage and written into the bill alongside the driver’s cut. When a ride is bid, the platform's share is deducted from the agreed fare between rider and driver, so the platform earns without having set the price. 2. 02 ### Subscription Plans for Drivers Drivers can buy paid plans to work on the platform. Plans can carry discounts and expire automatically when they run out. A plan is a flat fee instead of a cut of each fare, which suits drivers who prefer to know their costs in advance. 3. 03 ### Zone Surge, Peak Zones and Airport Fees Fixed-fare rides can carry time-windowed surge per zone, peak zones drawn as geofences and a flat airport charge. These lift fares in the areas where demand peaks, and the commission rises along with them. Each one is a per-zone setting, not a rule buried in code. 4. 04 ### Rentals, Outstation Rides and Parcel Delivery Hourly rental packages, intercity rides on the outstation module, and parcel delivery that has goods types of its own each carry separate prices. One rider base can therefore buy several kinds of trip, and every kind earns on its own terms. 5. 05 ### Paid Extras and Added Charges Amenities can be priced by zone type, with added charges and service tax applied on top of the fare. All of it is itemized on the fare breakdown shown to the rider, so extras read as choices, not as unwelcome add-ons. 6. 06 ### Fleet, Corporate, Franchise and Agent Accounts Corporate and fleet clients get their own wallet and owner booking. There is also a web booking channel, plus franchise licensee and booking agent accounts, both included in the package, each with its own wallet, commission and withdrawals. | Revenue stream | How it is charged | Take rateTypical range | What sets the ceiling | | --- | --- | --- | --- | | Commission on the Agreed Fare | A cut of each completed trip's agreed fare, recorded beside the driver's share in the bill. | inDrive: 10% in Botswana, 0.01% in a Nepal campaign. Uber Mobility revenue: about 30% of bookings. | India's 2025 aggregator guidelines require at least 80% of the fare to reach a driver who owns the vehicle, capping the platform near 20%. Where the aggregator owns the car, the floor is 60%. | | Driver Subscription Plans | A flat daily or monthly fee for platform access, with no share taken from each fare. | Namma Yatri: Rs 25 a day for autos, Rs 90 for cabs. Rapido: from Rs 9. | A flat fee works only while it undercuts commission. Outlook Business puts typical aggregator commissions at 20% to 40%, and that is the number a daily fee has to beat for drivers. | | Surge and Peak-Zone Premiums | A multiplier on the fixed fare for a zone or time window; commission rises with the fare. | India: fares may range from 50% to 2 times the state-set base fare. | The regulator owns the cap. The 2025 guidelines lifted peak pricing from 1.5 times to 2 times base fare, and states set the base fare, so premium revenue is bounded by figures you do not control. | | Paid Preferences and Extra Charges | Itemized add-ons shown in the fare breakdown, such as amenities, cancellation charges and tax. | India: cancellation fee capped at Rs 100. | Rules decide how much of this line survives. The same guidelines also require a state-set base fare that covers dead mileage over the first 3 km, so extras cannot be used to rebuild a lower fare. | **How to read this.** The inDrive figures are reported rates, not a rate card: [TechCabal](https://techcabal.com/2024/03/01/indrive-botswana-commission/) on its 10% Botswana fee and [ShareSansar](https://www.sharesansar.com/newsdetail/indrive-introduces-001-service-fee-initiative-to-boost-driver-earnings-in-nepal-2026-02-11) on the 0.01% Nepal campaign, both of which vary by market and date. The Uber ratio is computed from its [FY2025 10-K](https://www.sec.gov/Archives/edgar/data/1543151/000154315126000015/uber-20251231.htm): Mobility revenue of $29,670 million over summed quarterly bookings of about $97,497 million. Subscription prices are from [Outlook Business](https://www.outlookbusiness.com/start-up/explainers/why-are-ride-hailing-platforms-like-namma-yatri-uber-ola-embracing-a-zero-commission-model) and [MediaNama](https://www.medianama.com/2024/02/223-rapido-subscription-model-auto-drivers/). The Indian caps are reported by [SCC Online](https://www.scconline.com/blog/post/2025/07/04/motor-vehicle-aggregators-guidelines-pricing-safety-morth-india-2025/) and [TeamLease RegTech](https://www.teamleaseregtech.com/updates/article/44140/motor-vehicles-aggregator-guidelines-2025/). Use all of it as scenario input only; it predicts no driver or platform earnings. Revenue Model ### White Label Ride Bidding App Revenue Model, Stage by Stage Miracuves' white label ride bidding app earns on a fare the rider and driver settle between them, so commission is the base and every later income line is another switch in the console. Launch Start in one city with bidding on for city rides and take commission on each agreed fare, either a flat sum or a percentage of the fare, shown on each bill. Traction Add driver subscription plans, fixed-fare rides at a premium and hourly rentals, then read the reports to see which pricing riders and drivers favor. Scale Open intercity journeys and parcel delivery, bring in fleet owners and agent channels, and sell corporate travel while one console tracks every income line. Firebase, map, SMS and gateway providers bill you directly, and Miracuves takes no share of any ride. [Request a Free Strategy Call](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) Market Benchmarks ## Independent Ride-Hailing Market Benchmarks - 2025-2026 Figures The revenue models higher up are our own work, whereas the numbers below were produced by others: Statista, plus the 2025 annual reports of Uber and Lyft, which are filings with the US Securities and Exchange Commission. Read together, they show the share of each booking that fixed-fare incumbents keep, a yardstick for a fare-bidding operator judging its own commission. Statista01 ### $188.6bn in Ride-Hailing Revenue in 2026 Statista Market Insights projects worldwide ride-hailing revenue of US$188.60 billion in 2026, growing at 5.08 percent a year to US$229.98 billion by 2030, with user penetration rising from 24.6 percent to 28.7 percent and 2.34 billion users by 2030. Uber 10-K02 ### About 30% of Uber Mobility Bookings Becomes Revenue Uber's 2025 annual report shows Mobility revenue of US$29.67 billion against US$97.5 billion of Mobility gross bookings across the four quarters, about 30 percent. Across all its segments Uber recorded 13.57 billion trips and 202 million monthly active platform consumers. Lyft 10-K03 ### About 34% at Lyft, on 945.5 Million Rides Lyft's 2025 annual report shows revenue of US$6.32 billion on US$18.51 billion of gross bookings, about 34 percent, from 945.5 million rides, with 29.2 million active riders in the fourth quarter. Uber 10-K04 ### 15% of Uber Mobility Bookings Touch an Airport Uber reports that in 2025 it generated 15 percent of its Mobility gross bookings from trips that started or ended at an airport, which is why airport zones and airport fees are worth configuring from the first day in any city that has one. **Published sources, cited.** Statista Market Insights, *Ride-hailing - Worldwide*, market outlook, accessed October 2026 - [statista.com](https://www.statista.com/outlook/mmo/shared-mobility/ride-hailing/worldwide) Uber Technologies, Inc., *Annual Report on Form 10-K* for the year ended 31 December 2025, filed 13 February 2026 - [sec.gov](https://www.sec.gov/Archives/edgar/data/1543151/000154315126000015/uber-20251231.htm) Lyft, Inc., *Annual Report on Form 10-K* for the year ended 31 December 2025, filed 11 February 2026 - [sec.gov](https://www.sec.gov/Archives/edgar/data/1759509/000162828026006960/lyft-20251231.htm) Each number is the publisher’s own, shown as it was published. We worked out the 30 and 34 percent figures ourselves from the revenue and gross bookings every company reported, and neither is a commission rate, since reported revenue covers more than commission. What they depict is the market, not how any platform built by Miracuves performs, and none of it projects revenue for your business. Launch Timing ## Why Launch a White Label Ride Bidding App in 2026? Because rides are an established product, Miracuves gives a new city platform one clear reason to exist: riders name the fare they want to pay. Letting riders offer the fare is one, because it moves the pricing decision to the people in the trip. The operator no longer guesses a fare for every zone and hour. Instead, the operator sets the rules inside which rider and driver settle on it. 01 ### A Fare Negotiation App Puts Price First Riders compare cost before anything else when they pick an app. When the rider names the fare and watches drivers respond, price becomes the product itself instead of a surprise that arrives after booking. 02 ### Drivers Pick Their Platform Too Drivers are the scarce side of any ride market. When they see the route and the fare upfront and choose which rides to accept, they get a reason to join and stay. The driver app adds levels, incentives and subscriptions on top. 03 ### Two Pricing Models, One Build Bidding and fixed fares are separate modules on one platform. That lets your own city's data answer the pricing question instead of a guess made before launch. When the answer is clear, switch either one off for a given service. 04 ### New Cities Are a Settings Job Opening a city means adding one service location with its zones and a fare card, not launching a project. That makes the places bigger platforms reach last easy to open. The platform suits an operator who enters markets one at a time. 05 ### Ownership Changes the Arithmetic No platform vendor takes a per-ride fee on top of your own commission. You decide what drivers pay. What you keep is whatever the gateways and service providers do not bill you for. 06 ### Disputes Need a Record Ride operators in taxi businesses lose riders and drivers over fare disagreements, cancellations and complaints. Cancellation reasons are logged for each trip, and with pricing-audit records plus dispute SLAs every conversation starts from a record, not from memory. ### The Platform in Numbers **11** Service Modules **48** Driver Screens **24+** Payment Gateways **134** Permission Keys Bidding does not run the business for you. Someone still vets drivers, draws the zones and answers riders when a trip goes wrong, and every agreed fare must still be paid, split and recorded. The platform handles those tasks. Doing them well is the actual work of operating. Why Operators Buy In ## Taxi Bidding App Market Appeal, Revenue Potential & Operator Outlook Demand for rides is rarely the question for a ride platform. The real test is whether it can keep enough drivers in a city for acceptable wait times, at a commission both sides accept. Letting rider and driver settle the fare changes that math, since the operator earns on the price they agree. 1. 01 ### Commission on Rider-Offered Fares The platform share comes out of the price the rider and driver settled on, set as a flat amount or a percentage and printed on each bill. The operator earns without needing to predict the right fare for every zone and hour. 2. 02 ### Bidding and Fixed Fares Together Both pricing models are modules that sit side by side, so a city can try each. Reports then show which one riders and drivers favor, before the operator commits to either. 3. 03 ### Drivers Who Stay Subscription plans, referral rewards, incentives, leaderboards and driver levels are retention tools the operator configures. They target the supply side, which is the hardest part of a ride market to replace. 4. 04 ### Demand Beyond the App Fleet owners and corporate accounts, web booking, dispatcher phone bookings, franchise licensees and booking agents bring in demand that the rider app alone would miss. **Core Revenue Lines** - Platform Commission on Agreed Fares - Subscription Plans for Drivers - Zone Surge, Peak Zones and Airport Fees - Rentals, Outstation Rides and Parcel Delivery - Paid Extras and Added Charges - Fleet, Corporate, Franchise and Agent Accounts **Long-Term Upside** The lasting advantage is to be the platform drivers pick and keep working on. 1. 01**A first city with drivers available at peak times** 2. 02**A one-time purchase that hands over the source code** 3. 03**Trip, fare and dispute records a buyer could review** 4. 04**Drivers paid accurately and on time, week after week** **Worked Earnings Examples** The three setups below are illustrations, not guarantees or client figures. The levers are named in each, so you can enter your own numbers, and every rate shown is one you set yourself. Single City, Bidding Led**1***City Live* **City bidding rides with a fixed-fare taxi beside them.** One operator tests the model in a single city, with bidding on city rides, plus a taxi service at fixed fares for anyone wanting a set price upfront, and every other module off. Commission on the agreed fare drives revenue, while the effort goes into drivers: onboarding, approving documents and incentives that keep them online during peak hours. Rides, Rentals and Parcels**4***Services Live* **Four services on one rider and driver base.** The city stays the same but the income lines multiply: hourly rentals, outstation trips and parcel delivery turned on next to city rides. Every service has its own prices and commission, and none calls for another app, another driver pool or another payment setup. Many Cities and Fleets**11***Available Service Modules* **Many cities, fleet owners and channel partners.** The platform was built around this setup: each service location has its own zones and fares, franchises and agents have their own channels, fleet owners run their drivers in owner mode, and subscriptions for drivers run beside commission. The console, not a developer, decides the economics of each. [Request a Free Strategy Call](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) 10Why Choose Us Why Miracuves ## Miracuves vs Other Fare Bidding Taxi App Vendors Why Operators Choose Us · How We Differ - 01 ### A Fare-Bidding Build Already Delivered Wave App took a fare-bidding service live on this same base in 6 working days, reusing 18 of its 23 platform blocks as they were, and the source code was transferred to the client’s own account. The full case study, with its figures, is in our portfolio. - 02 ### Two Fare Models, One Console Many scripts lock you into a single pricing model. On this platform one fare engine and one admin console serve both bidding and fixed fares as modules you toggle per service, so your city, not the vendor, decides which pricing wins. - 03 ### Numbers Your Engineers Can Verify The code you receive has 413 migrations and 11 service modules, plus 48 driver-app screens and 11 roles across 134 permission keys. Your engineers can verify each figure themselves rather than trusting us. - 04 ### Go-Live Hardening Mapped Upfront Every go-live step is mapped before launch. An external penetration test, multi-factor admin login, certificate pinning and the production settings are scheduled into the deployment, so the platform meets its first real riders ready. - 05 ### Ride Bidding App Source Code You get the whole repository, history included, moved to your account, and the platform is hosted on your own server. Nothing is metered per ride, no module is encrypted, and no runtime license needs renewing. - 06 ### Made for the Operator Side Too Seven report families, disputes with SLAs, withdrawals, driver documents, fleet owners, God's Eye and the dispatcher console are all in the base build. An in-house project tends to reach this operating half last. Development Company ### How to Choose a White Label Ride Bidding App Development Company Choose a ride bidding provider who can show a bid-and-ride service already running on the same code. What to look for Miracuves - **Proven delivery** Wave App's bid-and-ride launch on this base reused 18 of 23 blocks in six working days - **Code you hold** The whole repository with history, no encrypted modules - **Figures to verify** 413 migrations, 11 service modules, 48 driver screens, 11 roles over 134 permission keys - **Two fare models** Bidding and fixed fares, toggled per service - **Support after launch** Two months of guidance, then six months of fixes and twelve months of updates Walk away from any vendor who - Rents a dashboard while keeping the source - Charges per ride or per driver - Locks you into a single pricing model - Hides modules inside encrypted code ### Compare Bid Based Ride Hailing Software Options, Then See Why Operators Pick Miracuves | Criteria | MiracuvesMiracuves Ride Bidding App | Off-the-Shelf Script | Custom Dev Shop | | --- | --- | --- | --- | | Launch Speed | 6 days, deployed under your brand | Unclear, or DIY | Months: 6-9+ | | Who Owns the Code | Whole repository handed over | Often restricted or encrypted | Usually yes | | Fare Models | Bidding or fixed fares, set per service | Typically only one of them | Whatever budget allows | | Service Types | 11 modules, each switchable | Taxi only | Quoted and billed one by one | | Dispatch | Monitor, God's Eye, heat map and manual assignment | A plain trip list | Often added late, if ever | | Payments | 24+ gateways plus cash and wallet | Just one or two gateways | Whatever the spec says | | Languages | 28+, with Arabic and Urdu right-to-left | English only | Charged per language | | Driver App | 48 screens, fleet-owner mode built in | Only a slim companion app | Another project | | Security Posture | Documented: handbook and VAPT review | Undisclosed | Depends on the project | **The difference between a bid-and-ride platform you can operate and a booking app that just has a price box added.**[Request a Free Strategy Call](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) Changelog ## Ride Bidding App Release Log - Version History & Updates | Version | Date | What Changed | | --- | --- | --- | | v2026.1 | Oct 2026 | Rebuilt on the current design. This release puts fare bidding next to fixed fares in eleven service modules. It includes a Flutter rider app and a Flutter driver app that has fleet-owner mode, a Laravel 12 admin and dispatch console, right-to-left layouts across 28+ languages, 24+ payment gateways, and a ten-document technical set that covers the security handbook and VAPT review. | Start Building With Us We can take your concept all the way to a live ride-hailing platform. Name your first city, say whether it should run bidding, fixed fares or both, and list the services you want live at launch. We will work out the rest together. [Chat on WhatsApp](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0)[Book a Meeting](https://miracuves.com/schedule-consultation/) - Response in 24 hrs - Free consultation - No contract lock-in - Source code is fully yours 11Learn more Blog & Resources ## Ride Bidding Platform - Latest Reading Shelf Longer articles on the choices behind a fare-bidding platform: how agreed pricing affects retention, why a ready-made base can beat a custom build, and what building one from scratch involves. [![Rider with a phone beside a driver in a yellow taxi, a map route on screen and fare bubbles above](/wp-content/uploads/2025/06/ChatGPT-Image-Jun-5-2025-12_41_47-PM-1024x683.webp)](https://miracuves.com/blog/indriver-clone-maximizes-retention-returns/)[Ready-Made Apps](https://miracuves.com/ready-made-apps/)[**From Bids to Bookings: How Our InDriver Clone Maximizes Retention and Returns**](https://miracuves.com/blog/indriver-clone-maximizes-retention-returns/)Key Takeaways What You’ll Learn An inDriver clone can increase retention by giving riders and drivers more control over pricing…[![Illustration comparing a ready-made ride-hailing app with custom development](/wp-content/uploads/2025/06/Indriver-Clone-image-1024x683.webp)](https://miracuves.com/blog/indriver-clone-over-custom-development/)[Ready-Made Apps](https://miracuves.com/ready-made-apps/)[**Reasons startup choose our Indriver clone over custom development**](https://miracuves.com/blog/indriver-clone-over-custom-development/)Key Takeaways What You’ll Learn An inDrive clone can be a smarter startup choice when speed, budget control, and early market entry matter…[![Illustration of app development: code, a phone with a car on a map, a shield and a payment card](/wp-content/uploads/2025/07/App-Development-Interface-and-Elements-1024x683.webp)](https://miracuves.com/blog/build-app-like-indrive-developer-guide/)[Ready-Made Apps](https://miracuves.com/ready-made-apps/)[**How to Build an App Like Indrive - A Full-Stack Developer's Guide**](https://miracuves.com/blog/build-app-like-indrive-developer-guide/)Key Takeaways What You’ll Learn Building an app like inDrive requires a full-stack approach that combines real-time ride logic, geolocation, fare negotiation… FAQ ## White Label Ride Bidding App FAQ - Fares, Apps, Launch & Compliance The questions ride operators ask most often, including those about licensing and legal duties. All**24**Fares & bidding**4**Platform & apps**4**Going live & compliance**4**Launch, code & Miracuves**12** **Can’t find your question?** Technical questions get a plain answer in 24 hours. [Ask us on WhatsApp](https://api.whatsapp.com/send/?phone=919830009649&text&type=phone_number&app_absent=0) Fares & bidding*4 questions* 01**How does fare bidding work in a white label ride bidding app?** The rider names the fare, drivers accept it or quote their own, and the rider chooses. In the app, a rider enters the two addresses, opens a bidding service and submits the request together with the price on offer. Drivers online nearby get the route and that price on screen. The rider then compares the responses by price, rating and vehicle, the trip runs at the agreed fare, and the platform commission is taken from it. 02**Can I run fixed-fare rides next to bidding on the same platform?** Yes. Three of the eleven service modules - Bidding, Bidding Outstation and Delivery Bidding - are bidding services, and the admin switches each on or off. The Taxi and Rental modules use fare cards by zone type, carrying surge, peak zones and airport fees. A single city can therefore serve both a negotiated ride and one at a fixed fare. Turn bidding off and drivers receive fixed-fare offers only. 03**What is a white label ride bidding app?** It is ride software, ready to brand, in which the rider names a price, drivers accept it or quote their own, and the rider chooses. This platform includes rider and driver apps plus admin and dispatcher tools, runs on your own server, and is delivered under your brand with the full source code. 04**Does bidding work for intercity rides and parcel delivery?** Yes, they are separate modules. Bidding Outstation serves intercity rides, where a set per-kilometer fare seldom works for both sides. Delivery Bidding serves parcels, recording goods types and capturing a signature at drop-off. Each one has its own on/off switch, independent of city-ride bidding. Platform & apps*4 questions* 05**What apps and panels does the ride bidding platform include?** The package has two Flutter apps and one Laravel 12 console. The rider app runs to 40-plus screens, while the driver app has 48 screens and adds a fleet-owner mode. The console covers the admin panel, dispatcher tools and the public website, which offers web booking. Eleven roles are pre-seeded, including super admin, dispatcher and fleet owner, and the Dispatcher Pro, Agent and Franchise consoles come with the package. 06**Which payment gateways and methods can riders use?** A trip can be paid by card, in cash, from the wallet, or partly from the wallet and partly in cash. The platform lists twenty-four gateways, Stripe, PayPal, Razorpay, Paystack, Flutterwave, Paymob, Xendit and Mercado Pago among them. Cards are entered on gateway-hosted pages and stored only as gateway tokens, so the platform never holds a card number. You open the merchant account for each gateway you use. 07**Can one platform serve several cities, languages and currencies?** Yes. Each city is set up as a service location carrying surge, fare cards, zone types and polygon zones of its own, so adding a city is configuration, not code. Distance units and currency are stored per trip, and maps run on Google Maps or OpenStreetMap. Arabic and Urdu are laid out right to left among the 28-plus languages in the apps. 08**How does a white label ride bidding app differ from a custom build?** A white label ride bidding app is finished software you deploy and brand, while a custom build starts from a written brief. Bidding, fixed fares, rentals, outstation, parcels, dispatch and both apps already exist here, and the demo shows them working before you pay. A custom agency build typically runs 6-9+ months, against 6 days to deploy this platform. Going live & compliance*4 questions* 09**Is a license required to run a ride bidding service?** Almost always, and the operator obtains it from the local authority. Courier, private-hire, taxi and ride-hailing services need licenses from cities, states or countries - for example the RTA in Dubai, the Motor Vehicle Aggregator Guidelines in India, TfL private hire licensing in London and state-by-state transportation network company rules in the US. Drivers, vehicles and trip insurance have their own requirements. Take advice from transport counsel on your route before you launch. 10**Has the platform been penetration-tested or security-certified?** The platform comes with a handbook for developers on security and a VAPT review of the source code that lists the controls in place. An external penetration test of your live deployment is the natural next step before launch, and we support it. 11**What setup is needed before the first real ride?** A few third-party accounts and a scheduled go-live pass. You supply a Firebase project for live offers and push notifications, plus merchant accounts and webhooks for each payment gateway. Also required: SMS for OTPs, email, either map keys or the OpenStreetMap stack, plus Apple and Google developer accounts. Hardening then covers encrypted backups, private storage for driver documents, locked Firebase rules, production settings and demo auto-approval turned off. 12**How does the platform verify drivers?** An admin approves or rejects the documents each driver uploads in the driver app, and a scheduled job tracks expiry. The demo approves documents automatically every five minutes, so switch that off in production and a person makes the decision. You, or a screening provider you pick, run the background checks; the platform stores the result and does not perform the check. Launch, code & Miracuves*12 questions* 13**How much does a white label ride bidding app cost?** One payment of [$3,099](#pricing) covers it, deployed on your own server in 6 days and branded as yours. Store approval runs outside those 6 days, since Apple and Google keep their own review timelines. Dispatcher Pro, Agent and Franchise come with that price at no extra charge, and anything custom past the base gets a fixed written quote first. 14**Do I get the full app source code?** Yes. The repository you receive, history included, contains the Laravel console with its API, the website, and the two Flutter apps. It is hosted on your own server, set up for a single operator. Nothing is metered per ride, no module is encrypted and no runtime license applies, so Miracuves takes no fee on your rides. 15**Has a real client launched a fare-bidding ride app on this base?** Yes. Wave App is a bid-and-ride platform made for Bmore On Demand Technologies, LLC. The build took 6 working days on this base, reusing 18 of the 23 platform blocks without change, and the source code was handed to the client. The work went into Wave App’s cities, zones, service types and bid rules. Read the [full case study](https://miracuves.com/portfolio/wave-bid-n-ride-bidding-app/) in our portfolio. 16**Is this the same platform as the inDrive Clone?** Yes. The inDrive Clone page and this page sell one platform: that page frames it around a well-known app, this one describes the software itself. Code, demo and price match: rider and driver apps, an admin and dispatcher console, and fare bidding alongside fixed fares. Whichever page you start from, Miracuves delivers it white-label under your brand, so choose the page whose wording fits how you talk about your business. 17**How long does it take to launch this ride bidding app?** Deployment takes 6 days. The platform goes onto your own server under your brand. App store approval on Apple and Google follows their own timelines and falls outside that window. Before the first real ride you also need your gateway accounts, a Firebase project and the go-live hardening, and a first city needs enough drivers online at peak hours for riders to get offers quickly. 18**Is a ready-made white label ride bidding app better than custom development?** For most operators, yes. Fare bidding, fixed fares, rentals, outstation trips, parcels, dispatch and both apps already run here, and the demo proves it before you pay. You launch in 6 working days at one fixed price instead of funding months of building. Anything your market needs beyond the base is scoped, priced in writing and built into the same code you own. 19**What is the business model of a fare bidding app?** The operator earns commission on every fare a rider and driver agree, and can add driver subscription plans alongside it. Fixed-fare services bring zone surge, peak zones and airport fees, while rentals, outstation trips and parcel delivery open more income lines. Paid extras, plus fleet, corporate, franchise and agent accounts, complete the mix, and each rate is set from the admin console. 20**What is the step-by-step process to launch my white label ride bidding app?** Start with the live demo of the rider app, driver app and console. Then share your brand assets, domain, hosting, Apple and Google developer accounts, payment gateway accounts and a Firebase project. We apply your branding, deploy everything to your server and prepare the app builds under your accounts, and your service goes live 6 working days after kickoff. Store review follows Apple and Google timelines. 21**Can dispatchers book rides for customers who phone in?** Yes. The dispatcher console takes phone bookings and assigns them, with God's Eye, a heat map and manual assignment to steer drivers, while the rider app handles every other booking. Rides from either channel run on fixed fares, offered fares or both, and Dispatcher Pro, Agent and Franchise consoles come in the package, so a taxi office keeps its call desk while moving online. 22**Is a white label ride bidding app a SaaS or a one-time purchase?** It is a one-time purchase, not a rented SaaS. You pay $3,099 once and the platform is deployed on a server of your choice under your brand. You receive the full source code, nothing is metered per ride, no module is encrypted and no runtime license applies, so Miracuves takes no fee on your rides. 23**Does a ride bidding app need Google Maps?** No. The maps run on Google Maps or on the OpenStreetMap stack, and you supply either map keys or the OpenStreetMap setup before the first real ride. Distance units and currency are stored per trip, so each city you add carries its own configuration without any code changes. 24**Can fleet owners and franchise partners work on a ride bidding platform?** Yes. The driver app adds a fleet-owner mode, and the Dispatcher Pro, Agent and Franchise consoles come with the $3,099 price at no extra charge. Together with the admin and dispatcher tools, they let you run your own drivers alongside fleets, agents and franchise partners under one brand. Keep Reading ## Explore this platform further Find custom development help, the ride bidding app development cost, guides for planning, and the wider industry. [Guide ### InDrive Revenue Model: How InDrive Makes Money in 2026 Read the article→](/blog/indrive-revenue-model/) [Industry ### Transport and mobility Explore the industry→](/industries/transportation-mobility/) [Guide ### InDrive App Features: What Sets It Apart Read the article→](/blog/indrive-app-features/) [Pricing$3,099One-time price ### One price, paid once See pricing→](#pricing) [Speak with an expert →](/schedule-consultation/) [Service ### Ride-hailing development Explore the service→](/service/ride-hailing-app-development/) [Guide ### How to Build Indrive Clone App: A Complete Guide for Developers Read the article→](/blog/how-to-build-indrive-clone-app-complete-developer-guide/) Disclaimer Miracuves is an independent software development company. We are not affiliated with, connected to, sponsored by, or endorsed by **inDrive**. [Read our full Legal Notice & Disclaimer →](/disclaimer/)**Reason behind this name** “White label ride bidding app” describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for. **Creator of this page** The entire design and codebase is built by our own team. The product contains no code, design, graphics, or content originating from the **inDrive** website or applications. **Trademarks** inDrive and all other third-party names and marks are the property of their respective owners, referenced here solely to describe the category of software offered.