Drivers and vehicles
Every driver, every car, every document in one record — licences, insurance, inspections, with expiry dates that warn you before they lapse instead of after.
IN PRIVATE TESTING
Flipo
Fleet operations software for Uber fleet partners. Drivers, vehicles, earnings, payouts and weekly reporting in one place — in German, English and Arabic.
THE PROBLEM
A fleet runs on spreadsheets until it cannot.
Run five cars and a spreadsheet is fine. Run thirty and the same week repeats forever: download the platform statement, work out what each driver earned, subtract the rental and the fuel, notice that one licence expired on Tuesday, write the invoices, answer the driver who thinks the figure is wrong — and you cannot prove otherwise, because the calculation only ever existed in a cell.
Flipo keeps the records, does the arithmetic from the source data, and can show where every number came from.
WHAT IT DOES
The weekly routine, without the week.
Earnings, matched automatically
Weekly platform statements are read in and matched to the right driver and the right car. No copying figures between a download and a spreadsheet.
Payouts and invoices
What each driver is owed, calculated from the same data, with the deductions applied and the document generated. Billing runs through Stripe.
Performance in one view
Trips, acceptance, cancellations and earnings per driver and per week, so a problem shows up as a trend rather than as a surprise.
Paperwork that generates itself
Contracts, notices and the recurring HR documents produced from the records you already keep, in the language the driver reads.
German, English and Arabic
Including a proper right-to-left layout for Arabic — not a translated interface with the buttons in the wrong place.
HOW IT IS BUILT
Built to survive a bad Monday.
Fleet software is only useful if it is up when the week turns over and everybody is paid at once. That constraint shaped the architecture more than any feature did.
This is also the honest answer to “have you done this before?” when a client asks us about SaaS work. Flipo is the reference.
- A Node.js service layer split into small workers, so one slow job never blocks the rest
- PostgreSQL for the records, Redis streams for the work queue
- Stripe for subscriptions, invoices and tax handling
- Two order-processing servers, one active and one on hot standby, with automatic failover
- Every import and every generated document logged, so a wrong figure can be traced to its source
Where Flipo stands today
Flipo is in private testing with a small number of fleets and is not generally available. It has not launched, we are not taking sign-ups, and the feature set above is what is being tested rather than a finished product. When that changes, it will say so here.
Run a fleet, or want something like this built?
If you operate a fleet and the week above sounds familiar, write to us — the testing group is small but it is not closed. If you want a platform of your own, that is the other half of what we do.