01 /
How is Waslni different from a generic ride-hailing clone?
Waslni is a configurable platform rather than a fixed clone: each deployment has its own identity, data, service rules, App Experience settings, and supported integrations.
Ride-hailing platform
A ride-hailing
platform
built for MENA.
Waslni combines one role-aware rider-and-driver app, quick in-app operations, a full web admin panel, and configurable rides and delivery under your brand.
1
Role-aware mobile app
2
Admin surfaces
3
App Experience modes
48
Languages you can ship
Why operators choose Waslni
A platform shaped by
real ride-hailing
operators.
Most ride-hailing software is built once and resold everywhere. Waslni was rebuilt by the operators who use it every day — for MENA, with the constraints that actually matter on the ground.
01 /
Branded as you, not as us
Your app name, your icon, your splash, your URL. iOS and Android binaries published from your developer accounts. Riders and drivers never see Waslni.
02 /
Payments configured for the deployment
The platform supports cash and regional gateway integrations including Paymob, Kashier, Fawry, and Lahza. A gateway is enabled only when it is supported for the market and configured with the operator's approved merchant account.
03 /
Arabic-first and bilingual
Right-to-left layouts, Arabic notifications, Arabic admin panel. Switch to English without a redeploy. Translators not required to keep the app readable.
04 /
Configured from a dashboard
Pricing, service types, fare formulas, surge windows, driver documents, content pages — all live-editable. No engineering team needed to change a rule, a copy, or a price.
Inside the platform
One mobile app.
Two admin surfaces.
One platform.
Riders and drivers use one branded mobile app, with the tools changing to match the signed-in role. Permission-aware controls inside the app cover quick operational work, while the full web admin panel handles configuration and oversight.
iOS + Android
Unified rider and driver app
Riders book trips and marketplace orders; drivers switch to their work tools to accept requests, navigate, manage documents, and review earnings. One download keeps both roles in one branded experience.
Inside the mobile app
Quick operational admin
Authorized team members can access permission-aware operational tools without leaving the app. It is designed for fast day-to-day actions, not as a replacement for the full configuration panel.
Web
Full admin dashboard
Manage the app experience, service types, pricing, drivers, shops, orders, payments, roles, content, reports, and audit history from the browser.
Operations
Run the business
from one panel.
01 /
Dispatch
Live map and override
See every driver and every trip in real time. Reassign rides manually when you have to. Cancel, refund, and credit, all with an audit trail.
02 /
Pricing
Service types and fare formulas
Per-service pricing — taxi, car, van, motorcycle, delivery — each with its own base, per-km, per-min, minimum, and surge curve. Edit live.
03 /
Payments
Multi-gateway, multi-method
Paymob, Kashier, Fawry, Lahza. Cash, card, wallet. Method tracked per trip. Refunds and partial refunds from the dashboard.
04 /
Payouts
Driver settlement
Track earnings per driver. Approve weekly or on-demand payouts. Export reconciliation reports. Hold a payout if a dispute is open.
05 /
Content
Pages and policies, editable
Privacy, terms, rules, FAQ, banners — all editable from the admin panel without a code deploy. Two-language rollouts in one click.
06 /
Permissions
Roles you can compose
SuperAdmin, Admin, Manager, Customer Service — each scoped to the screens and actions you choose. Add or remove a permission key from any role without a restart.
Built for MENA
Local before global,
by design.
Every part of the platform was built with one question first: would a real operator in Cairo, Ramallah, Amman, or Riyadh actually use this? If the answer was no, the feature was reshaped until it was yes.
01 /
Arabic-first
Arabic is the design baseline, not a translation layer. RTL layouts, Arabic dates and numerals, Arabic push notifications. English is the alternate, not the default.
02 /
Regional payment integrations
Supported integrations include Paymob, Kashier, Fawry, and Lahza. Availability and activation depend on the country, the deployment configuration, and the operator's merchant approval.
03 /
Local maps and routing
Google Maps and Mapbox supported. Configure your map vendor per tenant. Address autocomplete tuned for Arabic place names.
04 /
Operating hours that match yours
Support, deploys, and incident response run on MENA business hours, not San Francisco hours. A pull request opened in the morning gets a reply the same day.
Launch path
From signup
to live business —
step by step.
The platform is already built, but every rollout is scoped around the operator's brand, services, approvals, store accounts, and operational readiness.
- 01
Try a sandbox
Start a free 14-day demo with pre-seeded drivers, riders, and trips. Same platform as production — isolated, time-boxed, zero risk.
- 02
Configure your brand and experience
Set the app identity, service types, operating areas, pricing, roles, and App Experience mode for rides, delivery, or both.
- 03
Prepare store and payment approvals
Use your App Store and Play Console accounts, complete the required listing assets, and configure only the gateways approved for your merchant account.
- 04
Run a controlled pilot
Train the operating team, onboard an initial driver group, validate real workflows, and expand only after the service is ready.
Frequently asked
The questions
operators ask first.
02 /
Can I really run this without a developer?
Yes. Once your tenant is configured, day-to-day changes — pricing, service types, content pages, fare formulas, driver document lists, banners, permissions — happen inside the admin dashboard. A developer is only needed if you want to extend the platform itself.
03 /
Which countries does Waslni work in?
A deployment can be configured for a country's currency, languages, maps, service types, and brand. Payment gateways and regulatory requirements must be reviewed for each market before launch, and the local operator remains responsible for the licences its service requires.
04 /
How are payments and driver payouts handled?
Cash can be configured, and supported gateways such as Paymob, Kashier, Fawry, or Lahza can be connected when available for the market and approved merchant account. The admin tools track trip methods, driver earnings, and payout workflows.
05 /
How long is a typical launch?
There is no fixed launch promise. Timing depends on configuration scope, branding assets, payment and merchant approvals, app-store review, local requirements, and the operator's readiness for a controlled pilot.
06 /
How is my data isolated from other tenants?
Every tenant runs on its own database. Trips, riders, drivers, and payments never touch another operator's data. Cross-tenant access by platform staff is logged in an audit trail.
What's next
Your company.
Your brand.
Your customers.
WASLNI / PLATFORM
14
Open your sandbox - 14 days free
Launching in 30 days - or less.
-> Palestine · Egypt · you next
Launch a working ride-hailing or delivery business — drivers, dispatch, payments, payouts, and admin included. Start a free 14-day sandbox: no credit card, no engineering, and no sales call to get in.
WASLNI / PLATFORM
Launching in 30 days - or less.
-> Palestine · Egypt · you next