Waslni is not a Jeeny clone. It is a configurable white-label platform with one mobile app for rider and driver modes, permission-aware quick admin inside the app, and a full web dashboard. App Experience can run rides, delivery and shops, or both.
Jeeny is a regional reference that some MENA operators may study. The useful lesson is not to copy screens or assume how another company behaves, but to validate language, payments, support, driver onboarding, and city operations for the market being served.
That is exactly where most clone scripts fail. They can show a rider booking flow, but the cracks appear in the local details: Arabic copy that wraps badly, driver documents that are hardcoded, payment providers that do not match the country, weak cash reconciliation, support teams sharing one admin login, and fares that require engineering every time the operator changes a city or service type.
Waslni gives the operator one branded mobile app for rider and driver modes, permission-aware quick administration inside the app, and a full web dashboard. Services, registration forms, roles, shops, and supported payment integrations are configured for the tenant.
The customer journey is only one part of the product. Waslni connects rider and driver roles in one app with mobile and web administration behind them.
The same branded app presents rider or driver tools according to the account role. Review the supported booking, communication, safety, promotion, and rating flows in the live product.
Permission-aware tools let authorised team members handle urgent approvals, support checks, and selected operating tasks without a separate admin download.
Live fleet map, active trips, manual reassignment, phone-booking flow, customer support view, driver status, order history, and finance reports. A small local team can run city operations without touching code.
Enable cash or the optional wallet, and connect a supported card or wallet provider only after the operator’s merchant account is approved.
Service types, fare formulas, commissions, peak windows, driver registration fields, document requirements, city geofences, roles, permissions, policy pages, and banners are controlled from the admin panel.
Admins compose the registration flow, review submissions, and approve documents. The operator’s local legal team determines the fields and checks required in its market.
Jeeny-style markets punish generic software. Waslni is built around the details that local operators actually change week by week.
A Jeeny-style launch depends on country fit: currency, city boundaries, phone formats, document fields, payment options, language defaults, driver supply, and support workflow. Waslni keeps those as tenant configuration, not forks.
When cash is enabled, the operator defines collection, commission, records, reconciliation, and exceptions. The platform does not promise a particular settlement workflow or schedule.
Some markets need national ID, license, car papers, profile photo, service-type approvals, or extra KYC. The registration form builder lets operators change the checklist without waiting for a release.
Customer service can see trips without finance controls. Managers can handle drivers without platform settings. SuperAdmin sees everything. Permissions are built around real local teams, not one shared admin account.
A clone script can copy the surface. A platform has to run the business after the first thousand rides.
Apply the brand to the unified app and configure currency, languages, domains, and initial services.
The operations team defines service areas, supported fare and commission rules, peak periods, and the dynamic driver-registration form.
Connect a supported provider after merchant approval, create support roles, and test the driver-registration and approval flow.
Submit the iOS and Android builds, rehearse operating scenarios, and release to a limited audience before expanding.
No. Waslni is a white-label ride-hailing platform for building a Jeeny-style local service under your brand. The rider and driver experience can feel familiar to users, but the brand, pricing, data, admin rules, payment setup, and operating model are yours.
The platform supports Arabic RTL, currencies, configurable services, and admin-composed registration. The operator must confirm local licences, required fields, store setup, and supported payment providers with its advisers before launch.
Cash can be enabled when it fits the operating model. The operator defines collection, recording, commission, reconciliation, and exception procedures; no particular settlement process is promised.
Yes. The driver registration flow is admin-composed. Operators can add sections, fields, images, selects, car details, and service-type visibility rules from the admin panel.
Timing is scoped per tenant and depends on brand assets, store accounts and review, provider approvals, data preparation, and the operating model selected for launch.
Copy the local discipline: Arabic-first flows, cash support, clear driver economics, fast support, and city-by-city operations. Avoid copying the brand surface blindly. A new operator needs a sharper local promise, not a second Jeeny logo with different colors.
Explore the unified app, mobile admin tools, web dashboard, services, registration, and required integrations in a live walkthrough.