A Bolt-style ride-hailing service is more about pricing discipline and operator economics than about a flashy rider app. Waslni gives you both: lean apps that riders learn in 30 seconds, and the admin controls your team needs to keep commission, peak hours, and payouts in line.
Bolt won not because the rider app looked nicer — it usually did not — but because the operator economics were better. Lower commission to drivers, sharper pricing controls, smaller country teams. The product served the business model, not the other way around.
That is hard to replicate with a clone script, because the clone gives you a rider app and a driver app and considers itself done. The actual leverage sits in the admin panel: how fast you can change commission per service type per city, how granular your peak-hour windows are, how cleanly you can run a payout calendar that drivers actually trust. Most clones do not have those tools at all.
Waslni does. Commission is per service type per city. Peak windows have multiple targets per day, configurable by weekday. Payout cycles are admin-set. The product behaviour your riders and drivers see matches Bolt; the operator controls behind it match what Bolt's country managers were actually using.
The deliberate trade-off Bolt got right: rider and driver apps stay minimal, operator tooling does the heavy lifting.
Bolt-style minimal flow: address autocomplete, fare quote, book. Saved payment methods, scheduled rides, ride history, ratings. Bilingual EN/AR.
Closest available driver with the right service type, weighted by rating and recent load. Decline thresholds. Auto-reassign on timeout. Tunable per service type.
Per-trip commission visible, weekly payout calendar, wallet view with cash + card breakdown. Drivers see every fee before they accept a trip.
Live map, manual reassignment, phone booking, finance reports, role-based permissions. A small ops team runs a 500-driver fleet from one screen.
Per-km, per-min, base fare, minimum fare, peak multipliers per day-of-week per time-of-day. Admin-editable, no engineering required.
Document workflow with admin approval, expiry tracking, auto-offline on expired license. Built for the transport-authority audit, not against it.
Brand kit applied. Tenant provisioned. Service types your fleet runs (sedan, SUV, motorcycle, custom) and their commission structures configured.
City geofences drawn. Per-km, per-min, base fare set. Peak multipliers configured per day-of-week and time-of-day. The product matches your pricing card by Friday.
Gateway integrations live. Driver document checklist configured. 50-driver pilot onboarded and approved through the admin panel.
iOS + Android builds in the stores. Marketing campaign runs. Operations team handles the first call-in bookings through the console.
No. Waslni is the white-label platform you build a Bolt-style service on top of. Branded rider and driver apps in your stores, an operator console for your team, an admin panel for your ops lead. The product behaviour matches Bolt; the cost structure and the maintenance model do not.
Yes. Driver commission is configurable per service type and per city from the admin panel. You can run a 10% commission model in one market and a 20% model in another on the same Waslni tenant.
Yes. EV-specific service types with their own fare formulas and dedicated driver pool are a configuration exercise. Charging-station partner promotions go through the same banner and promo-code engine as everything else.
Default is a weekly payout calendar, but admins can configure daily, weekly, or monthly. Earlier cash-out tiers (tip-led drivers in particular) typically settle through the same gateway as inbound payments.
Clone script = you take the source code and become the maintainer. Waslni = hosted SaaS, branded apps in your stores under your developer accounts, quarterly feature releases that ship to every tenant, infrastructure run by us.
14 days free. Real apps. Real admin. No card required.