The Uber-clone-script market has been selling the same recycled codebase since 2017. Waslni is not in it. We are the hosted, MENA-first white-label ride-hailing platform that ships a real product in four weeks — and keeps shipping new features every quarter, to every tenant.
Most people searching for an "Uber clone" are not actually looking for an Uber clone. They are looking for a way to start a ride-hailing business without writing the platform from scratch. The clone-script market showed up to answer that question with a $4,999 license to a recycled codebase. It mostly does not work.
The reason it does not work is not that clones are evil. It is that ride-hailing is a real marketplace product, not a static app. A working ride-hailing service has to do live driver-to-rider assignment under contention, handle SOS calls, settle to four different payment gateways, file VAT, keep up with iOS privacy rules every September, and survive a sudden Friday-evening surge in Cairo. None of that is in the clone codebase, and all of it is your problem the day after you take delivery.
Waslni took a different approach. Build the platform once. Run it as a hosted SaaS. Let operators configure it per tenant down to the level of driver registration form fields and peak-hour pricing windows. Ship new features quarterly to every tenant. The clone-script question disappears because the right answer is not "buy a clone". It is "rent a real platform".
isCash.None of that is hypothetical. We have rescued three projects that started with one of these scripts. The pattern is identical every time: the rider app works for the demo video, the driver app limps along, the dispatch panel never gets used, and by month nine the founding team is asking for a hosted platform to migrate to.
Every behaviour a rider would experience in Uber or Careem, shipped under your brand.
Address autocomplete with Google + Mapbox. Fare quote before booking, with surge multiplier and promo applied. Multiple saved payment methods, scheduled rides up to two weeks out, repeat-favourite addresses.
In-app SOS calls the local emergency number and notifies your operations team. Share-ride sends a live tracking link by SMS or WhatsApp. Riders see the driver photo, rating, plate number, and ID before pickup.
Saved cards through Lahza, Fawry, Paymob, Kashier. Cash with automatic wallet reconciliation. Top-up wallet for prepaid customers. Promo codes and referral credits stack naturally.
Built-in referral codes with admin-defined rewards. Promo codes per city, per service type, per first-N-rides. Bonuses settle to rider wallet or as a fare discount.
Smart assignment, transparent earnings, a heatmap that helps them earn more, and a compliance flow that does not feel hostile.
Driver flips online, accepts or declines incoming requests based on radius + rating + load score, navigates with the embedded turn-by-turn map, completes the trip, and is auto-assigned the next nearest pickup.
Real-time earnings counter. Daily, weekly, and lifetime totals. Cash trips deducted, card trips added, commission visible per trip. Weekly payout calendar with bank-transfer or wallet withdrawal.
Live demand heatmap updates every minute. Drivers see where to position themselves before peak. Reduces empty kilometres, increases utilisation.
Drivers upload national ID, license, vehicle license, insurance, inspection — through the registration flow your admins compose. Expiring documents trigger automatic offline-mode and SMS reminders.
Dispatch, finance, drivers, riders, content, branding — one panel, with permissions so you can scale the team without scaling chaos.
Operators see every active driver and every active order in real time. Phone-booking shortcut for call-in customers. Manual reassignment for the awkward 1% of cases. Trip-history filter for follow-up.
Super Admin, Admin, Manager, Customer Service — each with a permission registry. Lock down who can edit fares, who can refund a rider, who can suspend a driver. Audit log records every change.
Sedan, taxi, van, motorcycle, custom. Per-type pricing formula (per-km + per-min + base fare + minimum fare). Per-type peak-hour multipliers. Seat counts. All editable from the admin panel.
Daily, weekly, monthly revenue breakdown by service type, city, payment method. Driver commission report. Settlement runs export to CSV or trigger bank transfers via the gateway. VAT-ready receipts.
Privacy, terms, rules, FAQ pages are editable from the admin panel. Multi-language. No deploy required to update copy.
Logo, brand colour palette, splash colour, push-notification sound, deep-link host, app name. Set once per tenant; applies across rider app, driver app, operator console, and admin panel.
A clone-script rider app looks pretty in a screenshot. A production ride-hailing service has to survive Friday 8pm in Cairo. These are the parts that matter.
Per-tenant database, per-tenant Redis namespace, per-tenant Cloudflare R2 path, per-tenant signing keys. Cross-tenant data access is structurally impossible — it is enforced at the connection-pool proxy layer.
JWT tokens carry tenant + role claims. Every backend endpoint verifies both. Admin endpoints additionally check a permission-registry key. There is no "trust the client" path anywhere.
Backend error rates, MQTT message latency, gateway failure rates, and driver online ratio are tracked per tenant. Alerts page the operations team before customers notice.
The honest comparison, with the trade-offs called out plainly.
Not in the sense the clone-script market uses the term. A clone is a one-time-licensed lookalike codebase that becomes your maintenance problem on day one. Waslni is a hosted multi-tenant ride-hailing platform: branded rider and driver apps in your stores, an operator console for dispatchers, an admin panel for your operations team — and we run the backend. The product behaviour matches Uber; the cost structure and the maintenance burden do not.
Three reasons. First, the typical clone uses an outdated React Native or Flutter version that breaks the next time Apple changes a privacy rule. Second, the backend is rarely production-grade — single-process, no MQTT broker, no real driver assignment logic, breaks at 50 concurrent rides. Third, you carry the maintenance forever: SDK upgrades, gateway changes, App Store policy churn, security patches. Most clones are abandoned by month nine.
Monthly platform fee plus a small per-completed-trip fee. The per-trip fee covers backend infrastructure, OTA updates, Apple/Google account costs, and platform engineering. Payment processing fees are passed through from your gateway. A 14-day free demo lets you drive it before committing.
Yes. Service types and fares, peak windows, driver documents, registration form fields, role permissions, banners, homepage layout for shops, policy pages — all editable from the admin panel. For deeper customisation (a new service type with unique behaviour, a regulator-specific receipt format), we run it through a quarterly platform-feature pipeline.
We document a data-export path: drivers, riders, trips, transactions, documents — all exportable to CSV or to a database dump. You keep your published apps under your developer accounts. We do not believe in vendor lock through obscurity.
The production stack runs Node.js / Fastify on the API + an MQTT broker (aedes) on the same process, with MySQL primary + Redis for cache and pub-sub, hosted in a regional cloud. The two production tenants today carry low-thousands of daily trips with headroom; the architecture scales to tens of thousands without redesign by adding read replicas and horizontal API workers.
Free demo for 14 days. Real rider + driver apps install on your phone. Real admin panel opens in your browser. No card required.