A white-label taxi booking app for traditional fleets ready to leave radio and PBX behind. Native customer + driver apps under your name, a web operator console for dispatchers, and an admin panel that your operations lead can run without engineering help.
Most MENA taxi fleets did not skip the radio era. They still run on it. A dispatcher answers a landline, shouts an address into a handset, and a driver who happens to be three blocks away picks up the customer five minutes later. That is the system in most cities of the region, and for a long time it worked.
Then the global ride-hailing apps arrived. Customers expected fare quotes before booking, ETAs they could trust, in-app payments, and a small green car icon they could watch slide toward them on a map. The fleets that did not adapt either sold out or shrank. The fleets that tried to adapt by buying an Uber-clone script discovered that the clone shipped a beautiful rider app and forgot the rest — no admin console worth using, no phone-booking shortcut for the call-ins that still make up half their volume, no Arabic anywhere.
Waslni is the white-label taxi app for the middle path: keep the dispatchers who know your city, keep cash as a primary payment method, keep the regulatory relationships, and add modern apps on top. Customer app. Driver app. A web operator console that is faster than the radio. Built where you operate, configured by your team, hosted by us so the platform keeps moving while you focus on the cars and the customers.
A customer app, a driver app, and a web console for your operators. Integrated. Tested together. Live in your stores under your name.
iOS and Android apps in your name. Address autocomplete, fare quote before booking, scheduled bookings, multiple payment methods including cash, in-app chat, SOS button, ratings, and saved favourite places. Bilingual EN/AR.
Online/offline toggle, smart job assignment, turn-by-turn navigation, weekly earnings dashboard, document upload workflow, demand heatmap. Drivers self-register from the app and operators approve from the admin panel.
Web operator console: live map of fleet and bookings, manual reassignment, phone-booking shortcut for radio call-ins, history with filters, finance reports, settlement runs, and a service-type editor that admins use without engineers.
The product fits the way MENA fleets actually run, not the way a Silicon Valley startup imagined fleets run.
If your dispatchers still take calls on a PBX and shout addresses through a radio, the operator console gives them a phone-booking shortcut so the workflow stays familiar while the dispatch logic is automated. The transition does not require firing your dispatchers; it makes them five times faster.
Most MENA taxi fleets still settle most rides in cash. Waslni treats cash as a first-class payment method — fare is computed by the app, recorded in the wallet, settled at end of shift. Card and wallet payments process through Lahza, Fawry, Kashier or Paymob.
Multi-tenant infrastructure is designed for ride-hailing throughput. A 20-driver town fleet and a 2,000-driver national operator both run on the same platform. Pricing scales with completed trips, not fleet size.
Document upload workflow with admin approval, document expiry tracking, automatic offline-mode if license expires, vehicle inspection logs. The compliance audit your transport authority is going to do, your dashboard already passes.
No-one wants to give up the radio and rediscover their job through a SaaS product. The operator console is designed to be faster than the radio from day one.
A dispatcher takes a call, types the address and phone number, and assigns the closest available driver in two clicks. Faster than the radio.
Define your service area. Drivers cannot accept rides outside it, riders cannot book outside it. Per-city pricing rules apply automatically.
Weekly or daily settlement runs. Driver commission, platform commission, cash collected, card processed, net payable — calculated and exported.
Configure surge multipliers per day-of-week, per time-of-day, per service type. Friday-evening Cairo is not the same as Tuesday-morning Ramallah.
Riders top up; drivers cash out. Wallet transactions are reconciled with the gateway statement. Manual adjustments are audit-logged.
The admin panel runs in Arabic RTL when your team picks it. Receipts, SMS, push notifications, emails — all bilingual.
The honest comparison.
The same playbook Palestine and Egypt followed.
You send brand kit and the cities you want to launch in. We provision the tenant, the subdomain, the admin account, and the city geofences. Your service area is on the map by day five.
Your operations lead configures the service types your fleet runs, the per-kilometre and per-minute fares, the driver commission, and the peak-hour multipliers. The product matches your existing pricing card by Friday.
Existing drivers get an SMS invite. They sign in, upload documents, and your operations team approves from the admin panel. A 50-driver pilot is in the field by end of week three.
Apps ship to App Store and Play Console. Marketing campaign runs. Dispatchers field call-in bookings through the new operator console. First public rides flow through the platform.
It is a taxi booking application sold under your fleet brand, not the vendor brand. Waslni ships native iOS and Android apps published under your developer accounts, plus a web operator console and admin panel on a subdomain you choose. The end customer never sees the word Waslni.
Yes, and it is one of the most common starting points. The operator console has a phone-booking shortcut: dispatcher types name + phone + pickup address, the system finds the nearest driver, the ride starts. Your dispatchers transition from radio to console without retraining.
Yes. Cash is a first-class payment method. The app calculates the fare; the driver collects cash; the platform records it in the driver wallet; at end-of-shift or end-of-week the settlement run reconciles cash collected against platform commission owed. Cards and wallets process through your gateway in parallel.
Four weeks to a public launch in most cases. The longest poles are usually waiting for the developer accounts to be ready, signing the payment gateway agreement, and Apple/Google review at the very end.
Lahza, Fawry, Kashier, and Paymob are in production today. For Saudi Arabia we wire HyperPay or PayTabs against mada and STC Pay. For the UAE we use Network International or Telr. For other countries, a gateway integration is a configuration task on top of the existing payment abstraction.
The product is built to pass a standard transport-authority audit. Driver document tracking, vehicle inspection logs, fare receipts, anonymised trip data export for regulator queries — all built in. We support your team with the compliance review, but Waslni is not a legal advisor.
14 days free. Real apps. Real admin panel. Drive it for a week before you decide.