Your shared rides app, your brand, your routes
Cabgo gives you the full shared-rides app — rider, driver and dashboard — so you define routes with stops, your drivers publish departures and riders book seats by segment. Pay in person or prepaid; you enable it from the dashboard, no coding required.
Shared rides bring the BlaBlaCar model into your own operation: instead of an on-demand trip, the flow revolves around routes, departures and seats. From your dashboard you create routes with their stops (Downtown → Terminal → Airport), your drivers publish departures with date, time and vehicle, and the rider books seats for the exact segment they need. Inventory is per segment: the same seat can be sold on the Downtown→Terminal leg to one rider and on the Terminal→Airport leg to another, squeezing every seat. The price is set by the dashboard within a band and the driver can adjust it without leaving that band; payment is configurable and defaults to cash paid in person to the driver. All under your brand, on your domain, coexisting with your other services in a single app.
Use cases
Who shared rides is for and how they use it in practice.
Intercity & long-distance routes
Recurring trips between cities or towns with fixed stops, where each rider gets on and off at the leg that suits them.
Rural transport
Communities with little public transport coverage: a daily departure connects the village with the city center and its services.
Airport & event transfers
Scheduled departures to the airport, concerts or fairs, with seats by segment to fill the van at every stop.
How it looks in the app
Scroll to discover the full flow — with your brand and colors.
Browse routes and upcoming departures
The admin creates routes with their stops; drivers publish departures with schedules. The rider opens your app and sees 'Downtown → Airport' with its upcoming departures.
Features
Routes with stops from the dashboard
The admin creates routes and defines their stops in order (Downtown → Terminal → Airport). That stop map is the base for departures and per-segment inventory.
Driver-published departures
On a route, the driver publishes a departure with date, time, vehicle and available seats. Riders see it listed with its schedule.
Seat by segment (per-segment inventory)
A seat isn't sold for the whole departure but by segment: freed the moment a rider gets off, it becomes available again for whoever boards at the next stop.
Admin price with driver override
The dashboard sets the per-segment price within a band (min–max). The driver can tune their departure without leaving that band — you control the range, they fine-tune it.
Pay in person or prepaid, configurable
By default the rider pays the driver in cash on boarding. If you prefer, you enable prepay by card/wallet to lock the seat before departure.
Live departure tracking
The rider sees where the vehicle is relative to their boarding stop and gets alerts at each stage of the departure up to their segment.
How it works
The admin creates the routes
From the dashboard you define each route and its ordered stops, along with the per-segment price band. No code required.
Drivers publish departures
Each driver picks a route and publishes their departure with date, time, vehicle and seats, tuning the price within the band.
The rider picks a segment and books
They pick boarding and drop-off stops, see the seats and price for that segment, choose how many seats and book.
Why Cabgo?
Launch your transport app without building it from scratch — without losing your brand.
Your brand, not ours
White-label app on iOS and Android with your name, colors and domain. Your riders never see 'Cabgo'.
One more vertical, not another system
Shared rides reuse your fleet, drivers, payments and dashboard. Collective transport is just one more service inside your operation, not a separate product.
Rates within your band
You set the per-segment price range and commission; the driver only fine-tunes within it. You control the business without micromanaging each departure.
Ready today, no development
You enable it and configure routes from the dashboard in minutes, instead of paying months of custom development.
Frequently asked questions
How is this different from a normal taxi trip?
Instead of requesting an exclusive on-demand trip, shared rides revolve around routes and departures: the admin creates the route with stops, the driver publishes a departure and several riders share the same vehicle, each paying only for their segment. It's the BlaBlaCar model inside your app.
Is the seat booked by segment?
Yes. Inventory is per route segment, not for the whole departure. If a rider only travels from Downtown to Terminal, their seat is freed there and becomes available for whoever boards from Terminal onward. That way the same seat can be sold across several legs of the same departure.
How is payment collected?
It's configurable. By default the rider pays the driver in cash on boarding, just like a traditional shared ride. If you prefer, you enable prepay by card or wallet so the seat is locked before departure.
Who sets the price, the dashboard or the driver?
Both, within limits. The admin sets a per-segment price and a band (minimum and maximum) from the dashboard. The driver can adjust their departure's price, but always within that band — you control the range, they fine-tune it.
Who publishes the departures?
The drivers. The admin creates the routes and their stops; on top of those routes each driver publishes their departures with date, time, vehicle and available seats. The rider just sees the listed departures and books the segment they need.