Is Waslni a Grab clone?
No. Grab is a market reference, not a behaviour specification. Waslni provides its own configurable App Experience, one rider-and-driver app, permission-aware mobile admin tools, and a full web dashboard.
Waslni is not a Grab 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.
Grab is a useful reference when considering how several services can share one customer experience, but its launch history and operating choices should not be treated as a specification for another market.
A “Grab clone” label does not prove service quality or operational readiness. Review the live app, administration surfaces, service controls, payment scope, and the responsibilities attached to every module.
Waslni App Experience is configurable: the operator can present rides first, delivery and shops first, or both. The rollout sequence and timing depend on tenant scope, store review, provider approvals, and operational readiness.
One branded iOS and Android app serves rider and driver modes. App Experience can prioritise rides, delivery and shops, or show both.
Couriers work through driver mode while customers browse restaurants and grocery from their own mode in the same branded mobile app.
Groceries, pharmacies, retail. Per-tenant shops module with banner control, homepage layout, vendor management.
The wallet can be enabled when it fits the operating model. Provider integration, settlement rules, and any financial approvals remain separate operator responsibilities.
App Experience can present rides, delivery and shops, or both. Admins configure supported service types and fare rules without assuming a launch time or copying Grab’s market behaviour.
Provider availability depends on the tenant and market. A supported provider is connected only after the operator obtains an approved merchant account.
Service types, fares, peak windows, document checklists, content, banners — your admins drive it from the panel, no code deploy required.
Handle selected urgent tasks inside the mobile app according to permissions, and use the full web dashboard for configuration, reporting, shops, and roles.
Apply the brand, select rides, delivery and shops, or both, and define the initial service areas.
Configure supported fare, commission, and peak-period settings by service type.
Connect a supported provider after merchant approval, compose registration fields, and test the chosen payment flows.
Complete store submission and operating tests, then open the service to a limited audience before expanding.
No. Grab is a market reference, not a behaviour specification. Waslni provides its own configurable App Experience, one rider-and-driver app, permission-aware mobile admin tools, and a full web dashboard.
Yes. Motorcycle is a built-in service type with its own seat-count (1) and fare formula. Use it for markets where two-wheel ride-hailing is the dominant flow (think GrabBike).
No. Ride-hailing is the always-on core. Delivery, shops, and wallet are independent admin modules that turn on when you are ready. Sequential rollout reduces operational load and risk.
The platform has an in-app rider and driver wallet for trip credit, referrals, and bonuses. Standing up a full digital-wallet license is a separate regulatory exercise; Waslni provides the wallet infrastructure, not the financial-services license.
When cash is enabled, the operator defines collection, recording, commission, reconciliation, and exception procedures. Waslni does not promise a particular settlement method or schedule.
Review the unified app, mobile administration, web panel, App Experience, and required integrations in a live walkthrough.