DEV3 Kerbora – Ride Hailing Laravel Script with Live Matching, Surge Fares & Driver Earnings (Flutter Apps)

Kerbora is a ride hailing platform that you host yourself, built by DEV3 Technologies on Laravel 12 and Filament 4, with two Flutter apps: one for passengers and one for drivers. A passenger asks for a ride, the matching engine offers it to nearby drivers ranked by true pickup time, and the trip runs from pickup to payment and rating. Staff work in an admin panel and a dispatch panel with a live map. The demo business operates in the fictional river city of Solvanna.

No live demo: 112 grouped screenshots and a desktop video tour show the 3D marketing site, the public pages, the admin and dispatch panels and both apps. Install it with the demo data to try every role on your own server.

Passengers

• Sign in with a phone number and a six-digit code, pin a pickup and drop-off, and see four ride classes with the full fare up front, the seat count and the pickup time.
• A live ride from matching to driver assigned, arrived (with the plate and a PIN and a waiting timer), in-trip and complete, with trip sharing, an SOS button that alerts dispatch with the trip and live position, and a destination change.
• A cancel preview that shows the exact fee and the reason before you confirm, and a free-cancel window.
• Cards, Kerbora credit or cash, a wallet, tips, receipts with every fare part, ratings, promos and a clear way to pay an outstanding balance.

Drivers

• A driver app with an earnings dial, a slide to go online, an offer card with a draining countdown, route to pickup, an arrived button that checks the distance, PIN start, tolls added at completion and a cash-collect step.
• Earnings by day, incentives with progress rings, a cooldown after repeated cancellations and cash-out.
• Driver applications, document review and fleets (operators with a commission share) are managed in the admin panel.

Matching, fares and surge

• A deterministic matching engine: offers last 15 seconds and go out in up to five rounds, ranked by pickup time, with an acceptance rule that an accept at the exact expiry second still wins.
• A fare engine in integer minor units: base, distance, time, surge, promo, tip and fees, with a fare preview you can try in the admin panel. Pure fare, match and cancel maths share test vectors with the Dart code in the apps.
• Surge pricing per area cell with a cap, step and a manual override with an expiry that is audited.
• Pre-booked rides, with a dispatcher alert before they are due, and booking on behalf of a caller.

Admin and dispatch

• An admin panel with trips in tabs (active, scheduled, completed, cancelled, no driver, flagged), a replay map of the driver's path, complaints, driver applications, fleets, fare preview, surge override, reports (gross bookings, take rate, acceptance, unfulfilled rate and cancellation causes), driver lookup, settings, audit and roles.
• A dispatch panel with a live map in light and dark themes, booking on behalf of a caller and manual assignment.

What is included

• The Laravel application with Composer packages and compiled assets inside (no Node.js or Composer on the server), both Flutter projects in apps/, the shared DEV3 Flutter package, a web installer and HTML documentation.
• Demo data for the fictional city: about 42,000 trips over six months, 220 drivers and live traffic, with a base currency of US dollars.

Good to know

• Stored-card charging is simulated only. Card payments work on the simulated gateway. Charging a saved card with Stripe, Razorpay or PayPal is not built, so a developer has to add it, and there is no pre-authorisation. Real push and payment gateways were never called.
• The driver app has no GPS plugin. Positions come from a built-in trip simulator. For real driving you need to add a location plugin to the driver app (the app reads positions through one provider you can replace) and connect a map provider.
• Masked calling is a stub. The call button exists but does not connect a real masked number: add your telephony provider.
• The driver home screen scrolls slightly on small phones. On a 390 by 844 phone the dials and rows fit above the tab bar, but on shorter screens the home screen scrolls a little.
• A driver cancelling in the last matching round ends the search. A driver cancel on round 5 goes straight to no driver found, and every driver who was already offered stays excluded. This was left as an open product decision.
• Languages: the marketing site and the passenger app include a right-to-left Arabic layout. The admin and dispatch panels were not translated.
• The apps were not tested on physical devices. They build as debug Android packages and run on the iOS simulator.
• Use MySQL or MariaDB on a live site. The concurrency checks run on MySQL 8.
• Name: Kerbora is a working name checked by a web search only, not a trademark clearance. Check it before you launch under it.
• No hosted demo. The city, drivers and passengers in the screenshots are fictional.

Quality checks

Kerbora 1.0.0 passed the seven release gates of the DEV3 Laravel suite on the final code: static analysis (Larastan level 6, 0 errors), 157 Pest tests with 1,840 assertions, a front-end size budget, migrations and seeding on MySQL 8 and SQLite, a headless-browser pass over 121 pages and 15 happy paths with parallel-request race checks on MySQL, an installer test from the zip, and a secret scan. The passenger app passed analysis and 161 tests, and the driver app 202 tests, with debug Android and iOS simulator builds. A review of the matching and trip engine fixed nine defects before the apps were built. Lighthouse scores were not measured.