Waslni combines an Arabic-first mobile experience, 8 bundled interface languages with tenant-visible languages controlled by configuration, tenant settings, implemented regional payment providers, and a launch plan scoped to the market.
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.
A ride-hailing product must support far more than a visual re-skin: live driver workflows, pricing, money records, support, permissions, incidents, releases, and local operating responsibilities. The exact included capabilities still need to be demonstrated and written into the deployment scope.
Waslni is built around two product decisions. First, operators use a maintained hosted platform rather than maintaining a separate fork of the codebase. Second, tenant configuration reaches into service types, fares, peak hours, document requirements, registration fields, permissions, policy content, and App Experience so routine operating changes stay under the operator’s control.
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.
The customer and driver experiences support right-to-left Arabic alongside seven other bundled languages. Tenant-authored labels and content can be managed by language from the dashboard.
The provider catalog includes Lahza for Palestine and Fawry, Kashier, and Paymob for Egypt. Operators enable the methods available in their country and choose whether each method serves customers, drivers, or both. Cash and wallets are supported too.
One connected product stack: a unified mobile app, a quick in-app admin area, and a full web control panel, all backed by the same tenant configuration.
Customers request rides, browse shops, order delivery, use their wallet, and review history. Approved drivers switch the same account into driver mode for jobs, navigation, earnings, wallet, and document workflows. One install replaces separate rider and driver apps.
Permission-aware admins can search users, review drivers, follow orders and withdrawals, manage shops and coupons, send notifications, and open the live command center without leaving the mobile app.
The browser dashboard adds live dispatch, analytics, service and pricing editors, App Experience controls, driver-registration forms, payment methods, roles, content, marketplace layout, and audit history.
These are areas of the current Waslni product to inspect in a configured demo. Availability and integrations depend on the tenant, country, release, and signed scope.
Tenant context selects the correct database, Redis namespace, and operating configuration. In multi-tenant mode, authenticated tokens also carry a tenant claim that must match the tenant resolved for the request.
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.
The mobile bundle contains English, Arabic, Russian, Turkish, German, French, Ukrainian, and Hebrew resources. Each tenant exposes only configured languages—normally English and Arabic, with Hebrew additionally configured for the Palestine deployment.
Compose driver-registration sections and required fields by service type, including identity, licence, vehicle, insurance, image, text, select, year, colour, and vehicle-model inputs. The mobile flow follows the saved configuration.
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-only changes can use Expo EAS Update. Changes that add or modify native code still require a new binary and store review.
Use this table as a requirements prompt, not a claim about every competing SaaS product. Ask each vendor to complete it from current evidence.
The sequence is consistent, but the duration depends on brand assets, developer accounts, gateway approval, local licences, testing, and store review.
Confirm the app identity, tenant configuration, currency, default language, domain, storage, and administration access.
Configure service types, fares, peak windows, driver registration, service areas, permissions, and App Experience.
Connect supported gateways through your merchant accounts and complete local licensing, privacy, and legal review.
Test the configured flow with a controlled pilot, resolve findings, then submit the production binary through your developer accounts. Store approval remains outside the platform’s control.
It means one mobile app is published in the App Store and Google Play under your developer accounts, with your name, logo, colours, and bundle ID. That app contains rider and driver modes and can also expose shop-owner and permission-aware admin tools. The full web dashboard sits on your operating domain.
Yes. Settings → App Experience includes Ride-only, Delivery-only, Ride-first, Delivery-first, and Both presets. You can enable Transport, Marketplace, and Wallet independently, choose the opening module, and localise the module labels.
A clone script usually transfers the maintenance burden to the buyer. Waslni is hosted: the shared platform is maintained centrally, while each operator manages its own brand, configuration, data, and daily 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.
The platform integrates Lahza for Palestine and Fawry, Kashier, and Paymob for Egypt. Activation depends on the tenant’s merchant account and configuration. Any other gateway or country requires a separate technical and commercial review.
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.
Waslni is hosted SaaS, so the platform source code is not transferred. Your agreement should state the ownership and export terms for your data, brand assets, tenant configuration, accounts, and published app listings.
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.
Request access to the unified app and web admin, then test your services, roles, language configuration, registration, pricing, and integration scope.