Waslni is the white-label ride-hailing platform built where Arabic-first UX, regional payments, admin-configurable product behaviour, and a four-week launch are the starting point, not a roadmap promise.
White-label is one of the most abused words in B2B software. It usually means a re-skin — same product, different colour, same vendor name buried in the footer of a receipt PDF.
That definition was good enough when the product was a salon booking calendar. It is not good enough when the product is a ride-hailing service that has to settle thousands of payments per day, dispatch drivers in real time across a city, file VAT in two currencies, and absorb the unique fact that one of your drivers just had their car towed. A real white-label ride-hailing platform has to do the boring parts of being a marketplace operator out of the box.
Waslni was built on two stubborn opinions. First, the platform should run as a hosted multi-tenant SaaS, because the alternative — every operator owning a fork of an ageing codebase — is how most clones die in year three. Second, configuration should reach deep enough into the product that operators can change service types, fares, peak hours, document requirements, registration form fields, role permissions, and policy copy without opening a ticket. Everything else follows from those two decisions.
Most platforms claim white-label and ship a re-skin. These are the four lines that separate a real white-label platform from one.
Logo, palette, app name, bundle ID, deep-link host, splash colour, push sound, store metadata, marketing email templates — all per-tenant variables. Two Waslni-powered apps will not look like siblings unless their operators want them to.
Service types, fares, peak windows, driver document checklist, registration form fields, role permissions, banners, terms of service, OTP providers — all editable from the dashboard. Engineering ships product, not config tickets.
Right-to-left layout is verified on every screen in every app. Receipts, push notifications, SMS bodies, admin panel — all bilingual. Translations include AR, EN, RU, TR, DE, FR, UK, and HE.
Lahza, Fawry, Kashier, Paymob in production today. Adding mada, STC Pay, MyFatoorah, HyperPay, or any regional gateway is a tenant-config exercise, not a rebuild. Cash and wallets are also wired in.
Three connected products that have to be in sync in real time. Waslni ships all three from the same codebase, integrated, tested together.
Native React Native build via Expo. Phone-OTP signup, address autocomplete, fare quote before booking, scheduled rides, in-app chat, SOS, ratings, saved payment methods, referrals, promo codes, ride history, and Arabic RTL. Published under your developer accounts.
Online toggle, smart assignment based on proximity + rating + load, turn-by-turn navigation, earnings + wallet, weekly payouts, document upload with admin review, demand heatmap, and per-tenant onboarding fields. Drivers can self-register; admins approve.
Live map of drivers and orders, manual reassignment, phone-booking shortcut for call-in customers, ride history with filters, financial reports, role-based permissions, content management for policy pages, banners and homepage layout for shops, and a service-type editor.
The features below are not on a roadmap. They are running in production for two operators in two countries today.
The same Waslni cluster can power multiple operator brands at once. Per-tenant databases, per-tenant Redis namespaces, per-tenant Cloudflare R2 paths, per-tenant signing keys. Cross-tenant access is impossible by design.
Super Admin, Admin, Manager, Customer Service out of the box, each with a granular permission registry. Build custom roles by toggling permissions. Audit log captures who changed what.
Policy, terms, rules, and onboarding copy are CMS-managed. Your team writes the text once per language; the apps render the right one from the device locale.
Configurable per-country document list. National ID, license, vehicle license, insurance certificates — define them in the admin panel and the rider/driver registration flow updates automatically.
Drivers register from the app, upload documents, and your team reviews from the admin panel. The form is admin-composable: add new fields by type (image, text, select, color, car model) without shipping code.
JavaScript-side fixes ship to users in minutes via Expo Updates. Native binaries are recut quarterly. You never ask users to update for routine improvements.
Most ride-hailing SaaS started in another region and was retrofitted to MENA. Waslni was built where the operators are.
The same playbook we used for Palestine and Egypt. No surprises.
You send us your brand kit; we provision the tenant: database, Redis namespace, R2 storage path, subdomain, admin account, currency, default language. The skeleton app is up the same week.
Your operations lead spends a couple of days in the admin panel: service types, fares, peak-hour windows, document checklist, cities, geofences. The product behaves like yours by Friday.
Payment gateway merchant accounts plug in under the keys you control. KYC for drivers is reviewed against local regulations. Privacy + terms are localized.
Builds submitted to App Store + Play Console under your developer accounts. 50-driver TestFlight pilot validates dispatch. Public launch within 24 hours of approval.
It means the rider and driver apps are published in the App Store and Google Play under your developer accounts, with your name, your logo, your colours, and your bundle ID. The admin panel sits on a subdomain you choose. No Waslni branding is visible to your users or drivers. From their perspective, the product is yours.
A clone script is a one-time code delivery. You then maintain the servers, the security patches, the iOS / Android SDK upgrades, the payment gateway API churn, and the bug fixes — forever. Waslni is a hosted platform. We run the infrastructure, ship new features quarterly to every tenant, and you focus on operating the business.
Yes. The admin panel has dedicated editors for service types (car, taxi, van, motorcycle, custom), pricing formulas per service type and per city, peak-hour multipliers with multiple windows per day, and seat-count rules. Changes take effect immediately.
Lahza is live in Palestine and Egypt. Fawry, Kashier, and Paymob are live in Egypt. For Saudi Arabia, HyperPay + mada + STC Pay are the typical stack — these are tenant-config integrations, not platform-level engineering. For the UAE, Telr / Network International / Checkout.com follow the same pattern.
Yes. Every admin screen is fully translated and rendered right-to-left when the operator picks Arabic. Email and SMS templates are bilingual. Print receipts render correctly in Arabic.
You own your data, your brand, your tenant config, your driver and rider relationships, your accounts, and your published apps. You do not own the platform source code — that is a hosted SaaS. The trade-off is that every new feature we ship lands on your tenant automatically, and you never carry the security and maintenance burden of running a ride-hailing backend.
What "app like Uber" actually means once you ship it — components, timeline, real costs.
For traditional taxi fleets and dispatch companies — same platform, different angle.
A side-by-side review of ten vendors — Waslni included, with the trade-offs called out honestly.
14 days free. Apps install on your phone. Admin panel opens in your browser. No card required.