Build a transport or delivery service for your city, brand, language, payment setup, and driver model. Waslni provides the shared product and per-tenant controls; the exact launch plan depends on configuration, local approvals, testing, and store review.
Uber has become shorthand for an on-demand transport product. If you want to compete in your city, the important question is not whether the home screen looks familiar; it is whether booking, driver work, pricing, support, payments, and administration operate together under your rules.
Waslni is a white-label platform: software presented under the operator’s identity rather than the vendor’s. It provides a maintained shared product while letting each tenant configure its brand, service types, fares, registration flow, roles, payments, content, and App Experience.
Each tenant has its own app identity, operating settings, registration flow, and supported payment configuration on the shared product. A new market still requires local payment, licensing, privacy, and operational review.
One branded mobile app adapts to riders, drivers, shop owners, and authorized staff. Quick operations are available in-app, and the full administration workspace lives on the web.
The branded mobile app gives riders phone sign-in, address search, fare estimates, trip requests, chat, safety tools, ratings, configured payment methods, referrals, promo codes, and an Arabic-first interface.
Online/offline controls, incoming request handling, navigation, earnings and wallet views, plus a document and registration flow reviewed by the operator. Registration sections, fields, and requirements are configured by the admin for each tenant and service type.
Authorized staff can reach quick operational tools inside the app. The full web panel handles requests, reports, roles and permissions, service types, registration forms, payment settings, content, and the broader business configuration.
Waslni is designed around Arabic RTL, regional operating needs, tenant-specific configuration, and supported payment integrations that are activated per merchant account.
The mobile app bundles eight interface languages, including right-to-left Arabic and Hebrew. Each tenant exposes only the languages configured for its market; English and Arabic are the normal baseline.
The current integrations include Lahza for Palestine and Fawry, Kashier, and Paymob for Egypt. Activation depends on the tenant’s merchant account and setup; any additional country or gateway requires a separate review.
Your colour palette, logo, app name, bundle ID, store listing, deep-link host, and splash screen are tenant-specific variables. This lets each operator publish a distinct identity while using the maintained shared product.
Service types, pricing rules, peak-hour windows, driver document lists, registration form fields, even the content of the policy pages — your admins edit them from the dashboard. You do not file a ticket every time you want to change a fare.
A one-time code handover and a maintained hosted platform create different ownership, staffing, update, and operating responsibilities. Confirm each responsibility in writing before choosing either model.
Send us your logo, brand colours, store metadata, and the country you are launching in. We provision your tenant, set up your subdomain, and configure currency, language defaults, App Experience, and the supported payment integrations approved for your merchant account.
Your team configures the operational side from the admin panel: service types (sedan, SUV, van, motorcycle), pricing per kilometre and per minute, peak-hour multipliers, driver registration documents, and the cities you are launching in.
Payment gateways connect through your merchant accounts. Your team configures the driver registration form and document requirements, then reviews submissions from the admin panel. The operator remains responsible for local licensing, data protection, and legal review.
We prepare the single branded app for submission under your developer accounts. The same build covers rider and driver modes, reducing store, release, support, and onboarding overhead.
It means the service appears under your name and visual identity. Waslni provides one branded mobile app with rider and driver modes, permission-aware operational tools inside the app, and the full admin workspace on the web. Your team controls service types, prices, registration fields, permissions, and the App Experience.
The schedule depends on brand assets, developer accounts, gateway approval, local licences, configuration, testing, and store review. We confirm a scoped launch plan once those dependencies are known.
No. Waslni is hosted, multi-tenant SaaS. You get one branded mobile app, tenant-specific configuration, and administration tools. Data ownership and export terms should be stated in the customer agreement.
The current integrations include Lahza for Palestine and Fawry, Kashier, and Paymob for Egypt. Activation depends on the tenant’s merchant account and setup. A new country or gateway requires a separate review of technical, commercial, and local requirements.
A lot. Service types and fares, peak-hour multipliers, driver document requirements, registration form fields, permissions and roles, branding (logo + colours), policy + terms + rules pages, banners, OTP providers — all of it edits live from the admin panel. Code deploys are reserved for genuine product evolution, not routine business changes.
Pricing depends on the selected scope, operating model, and required integrations. Payment-processing fees are set by the operator’s gateway. Request a proposal based on the modules and market you plan to launch.
A deeper look at what white-label actually means when you ship a real product in 2026.
How a Careem-style super app maps onto Waslni — and where MENA operators usually want it different.
Regulation, payments, language, fleet, and the on-the-ground realities in the Saudi market.
Explore the unified rider-and-driver app, its in-app operational tools, and the full web admin panel on the demo environment.