Build a service under your own identity that brings transport and the marketplace into one app. Run rides only, delivery only, or both, with payment and regulatory requirements reviewed for each target market.
Careem did the work of teaching the MENA region that ride-hailing apps could be local, Arabic, and trustworthy. Then they sold to Uber. The market that Careem built is still here, but the local operator opportunity is, if anything, bigger than it was in 2019 — and most of it is being chased by founders with the wrong tools.
A clone can look complete in a sales demo while leaving important regional work unresolved: Arabic RTL across every workflow, readable receipts and messages, supported payment integrations, driver onboarding, permissions, and the operating tools used after launch.
Waslni uses one shared product with tenant-specific identity, currency, enabled gateways, driver-registration form, languages, and App Experience. A new market still requires a local review of payments, licensing, privacy, and operations before its launch scope can be confirmed.
The interface adapts to rider, driver, shop-owner, and authorized admin accounts, while the complete administration workspace remains on the web.
The unified iOS and Android app gives riders fare estimates, trip requests, configured payment methods, safety tools, chat, referrals, and trip history in an Arabic-first experience.
Drivers sign in to the same installation for online status, job requests, navigation, earnings, and the admin-composed registration and document flow.
Authorized staff get quick operational controls inside the app, while the full web panel handles roles, service types, registration forms, finance, content, and configuration.
The same super-app can include restaurants and grocery shopping. Shop owners use their own in-app workspace, and drivers handle transport and delivery work without installing another app.
Not retrofitted to MENA from a base built somewhere else.
Right-to-left layout is verified across every rider, driver, operator and admin screen. Receipts, push notifications, SMS bodies — all bilingual. Translations include AR, EN, RU, TR, DE, FR, UK, HE.
Current integrations include Lahza for Palestine and Fawry, Kashier, and Paymob for Egypt. Activation depends on the operator’s merchant account and tenant setup. Any additional country or gateway requires a separate technical and commercial review.
App Experience settings support rides-first, delivery-first, rides-only, delivery-only, or a combined experience. In combined mode, customers move between transport and the marketplace from the same app.
Configure separate tenants for different brands, currencies, languages, services, and operating rules. Each market still needs its own payments, compliance review, testing, and launch scope.
Apply the brand kit, provision the tenant, and choose rides only, delivery only, or both. Then set the default language, currency, and first screen.
Service types, fare formulas, peak windows, document checklist, city geofences configured by your operations lead from the admin panel.
Configured gateways connect through your merchant accounts. Your team defines driver registration fields and documents; local licensing, privacy, and legal review remain the operator’s responsibility.
Test real operating flows with a pilot group sized for your service area, resolve issues, and submit the branded app under your developer accounts. Public launch follows your readiness checks and store approval.
Waslni is software for launching your own branded transport and delivery service. One mobile app adapts to rider, driver, shop-owner, and authorized admin accounts, while the full administration workspace remains available on the web.
Clone scripts are usually one-time licence deals: you take the code and assume maintenance. Waslni is a maintained hosted product with a branded mobile app, permission-aware in-app operational tools, a web admin panel, and tenant-specific configuration.
The platform supports separate tenant configurations for brand, currency, language defaults, services, payments, and operational rules. Each country still needs its own scope, merchant accounts, compliance review, and launch validation.
No. App Experience lets you run rides only, delivery only, or both. You can also choose whether transport or the marketplace appears first when both are enabled.
Waslni can be configured for different markets, but no country is automatically “easy.” Payment availability, transport licensing, privacy requirements, maps, taxes, and store rules must be reviewed for the target market before scope and timing are confirmed.
Explore the unified mobile app, its role-aware experiences, and the full web admin panel in the demo environment.