JollyDrivers Sign in
JollyDrivers

Closed beta · Australia

Rideshare, the right way up.

For too long the app has sat in the driver's seat. JollyDrivers hands the wheel back to the people who make this industry work — the drivers and the riders — with operators keeping everyone safe, legal and accountable.

Booking and back-office software for hands-off rideshare, chauffeur and transfer operators in Australia and the drivers who work for them.

Sign in See what changes
  • No surge
  • No auto-dispatch
  • No star ratings
  • Your own Xero
  • Works with your AI

The story

Somewhere along the way, rideshare got turned upside down

The app set the price. The app handed out the work. The app kept the customer. The people actually doing the driving were the last to have a say. Here is what the right way up looks like.

01 · How it has been

The app took the wheel

Prices that climb with demand. Work handed out by an algorithm that treats drivers as interchangeable. A star average standing between a driver and tomorrow's income. And the customer? They belonged to the app, not to the driver they trusted.

02 · The flip

So we built it the other way up

In JollyDrivers the driver runs the job. The rider keeps the driver they trust. The operator holds the authorisation and keeps everyone safe and legal. And the software gets out of the way — it prices nothing for itself and hands out no work on its own.

03 · Drivers

Take the driver's seat

Keep your own fare book for your own customers — only you can see or change those prices. Nothing auto-assigns work to you. One calendar across every operator you drive for, with a warning when two jobs clash. Your hours logged from the trips themselves. Your share of every fare, visible without asking anyone.

04 · Riders

Keep your driver

Book by saying what you need, not by filling in forms. Follow the trip live and message your driver. Keep a list of the drivers you trust and book them again — you decide who has your details, and you can stop sharing at any time. And no surge. The fare comes from a fare book, not from how busy it is.

05 · Operators

Keep it safe, legal and on the record

You hold the authorisation, so you set the standard. Compliance documents with expiry tracking, driver hours and fatigue warnings, training records, safety management plans you can prove were in force on the day, and an audit-ready export when someone asks. Invoices land in your own Xero. You step in when something needs you — not for every trip.

06 · Your AI

Bring your own AI

Connect Claude, ChatGPT, Gemini or any assistant that speaks MCP. Ask it what's next, who's free, what's still owed. It proposes; you approve. It works under your own sign-in, and you can disconnect it at any time.

What changes

Same industry. Opposite way up.

Each card starts the way rideshare has worked, then flips to the way JollyDrivers works. Tap one to flip it back and forth.

The life of a booking

From a chat to an invoice in the operator's Xero

Every step is an event in the booking's history, and the rider's, driver's and operator's screens update live from that record.

  1. BookedBy AI chat, the operator's public booking page, or the operator. One shared set of checks.
  2. ConfirmedJollyDrivers emails the customer a confirmation in the operator's name.
  3. DrivenEn route, arrived, on board, completed. The rider sees each step live.
  4. PaidRecorded as cash, card or invoice. The invoice is raised in the operator's own Xero.
  5. On the recordThe history feeds the driver's hours, the operator's reports and the compliance pack.

Connect your AI

Bring your own AI. Talk to your bookings.

JollyDrivers speaks MCP — the open standard AI assistants use to plug into other software. Connect Claude, ChatGPT, Gemini or any assistant that supports it, and ask about your work the way you'd ask a colleague. No new app to learn: the assistant you already use becomes the way in.

Anyone, before they have an account

What is JollyDrivers, and how is it different from a rideshare app?

about_jd compare_to

It's booking and back-office software for small rideshare, chauffeur and transfer operators and their drivers. Where a rideshare app owns the rider and prices by demand, the operator sets their own fares with no surge, riders keep booking drivers they trust, and JollyDrivers works out no share of a fare for itself.

Drivers, signed in to their own account

What does tomorrow look like?

my_schedule

Three jobs across two operators: a 6:40 am airport pickup, an 11:00 run to the hospital, and a 3:30 pm return to the airport.

I'm at the terminal. Mark me arrived.

propose_trip_stage

Ready to record you as arrived for the 6:40 pickup — your rider will see it straight away. Go ahead?

Yes.

stamp_trip_stage

Done. You're marked as arrived.

Operators, signed in to their own account

What's still owed to us?

unpaid_invoices

Four invoices are unpaid; the oldest is 19 days. Want the list?

Later. Who's free for the 2 pm airport job?

fleet_status

Sam and Priya are both available from 1:30.

Accept it and put Sam on it.

propose_accept_booking propose_assign_driver

Here's what I'll do: accept the booking and assign Sam. Approve?

Riders

Riders can't connect an assistant to their account yet. For now a rider's own AI can use the no-account endpoint to find out what JollyDrivers is, and riders book through the booking assistant on their operator's page.

Illustrations. The names, times and amounts are made up; the tool names are the real ones.

  • It proposes. You approve.Anything that changes something — accepting a job, stamping a stage, raising an invoice — comes back as a proposal to approve before it happens.
  • Your sign-in, your permissions.An assistant connects with your usual JollyDrivers login, in one role, and can do no more than you could in the app.
  • Recorded as you. Revocable by you.What it does is recorded as done by you, through your assistant. Disconnect it from your account and it stops on its very next call.
No accounthttps://jollydrivers.com.au/mcpread-only · reads no bookings and no personal data
Your accounthttps://jollydrivers.com.au/mcp/accountoperators and drivers · open to a small pilot during the closed beta

Account connections are in pilot while JollyDrivers is in closed beta, and some of these tools are still being switched on. A plain-text summary for AI assistants is at /llms.txt.

Under the bonnet

Built to take rideshare to the next level

However a booking arrives, it comes through one door, lands in one record, and every screen that shows it is drawn from that record — live.

The booking assistant An operator's booking page The operator's portal A driver, for their own customers
One doorthe same checks, every time
The booking recordevery change an event, with a name on it
The rider's live trip The driver's workspace The operator's fleet view The operator's Xero
Live, everywhereScreens update over a live connection, so nobody refreshes to find out what changed.
A history, not a rowEvery booking is a record plus an event history. The current state is fast to read; the full story can always be checked.
AI bookingThe booking assistant runs on Anthropic's Claude, asks only for what is missing, and knows about airports and flight arrivals.
Checked on the mapAddresses and routes are checked against Google Maps while the booking is still being made.
Your Xero, not oursInvoices, approvals, voids and payments go straight into the operator's own Xero organisation.
Installs like an appA progressive web app: add it to your home screen and it runs as a real app, built for phones first.
Messages that come from youConfirmations go out by email in the operator's name, and texts from a sender the driver is allowed to use.
Open to your AIAn open MCP endpoint for anyone's assistant, and account connections for your own.

The work behind it

Serious engineering, counted by the code itself

Every figure here is counted from JollyDrivers' own repository each time it is built — not typed in by hand, and never rounded up.

1,736commits
636pull requests merged
143releases to production
7,589automated tests on every change
384,397lines of source code
176days since the first line

Counted when this version was built (commit b0ec54ad), from the first commit on 1 April 2026. Lines of code are non-blank lines of C#, Razor, CSS, JavaScript, HTML and PowerShell, tests included, generated database migrations excluded. Tests are test methods — many run several cases — and every code change has to pass all of them before it can merge.

Straight answers

What JollyDrivers deliberately is not

  • Not a transport operator or booking entity. The operator holds the authorisation to take bookings and is accountable for them.
  • Not a dispatch engine. Drivers pick up their own work or are assigned by their operator.
  • Not a ratings platform. There are no public star ratings. Trust comes from riders going back to drivers they know.
  • Not a consumer brand. JollyDrivers is infrastructure for operators and drivers, not a rideshare app competing for riders.

From the blog

Notes from the driver's seat

All posts

Read more

The whole story

Drivers. Riders. Operators.

About bloody time.

Rideshare built around the people who do the driving, the people who ride with them, and the operators who keep it all safe and legal.

Get in touch Sign in

Contact

Get in touch

JollyDrivers.com.au is in closed beta. Membership is currently invitational only. Invitations can be requested for suitable applicants.

hello@jollydrivers.com.auEmail +61423759045Phone
We reply as soon as humanly possible!