openfrontRideshare

Open source
alternative to
Uber

Driver-owned ride discovery, quotes, booking, scheduling, trip management, payments, safety records, and marketplace interoperability.

Early alpha for evaluation, not a licensed live transport service. Trip, payment, safety, insurance, and provider requirements must be verified before serving real riders.

Workflows

Built around rideshare work

Openfront Rideshare is being built as a source-owned platform for independent drivers and fleets. The planned product connects rider discovery, quotes, immediate and scheduled bookings, trip management, payment records, support, and safety workflows while each operator retains control of its platform, customer relationships, operating data, pricing, and provider choices.

Planned rider experience, one view

Openfront Rideshare is being built as a source-owned platform for independent drivers and fleets. The planned product connects rider discovery, quotes, immediate and scheduled bookings, trip management, payment records, support, and safety workflows while each operator retains control of its platform, customer relationships, operating data, pricing, and provider choices.

Planned driver operations

Driver, fleet, vehicle, document, availability, pricing, booking, and trip workbenches

Acceptance, dispatch, trip-state transitions, incidents, refunds, payouts, and auditable event records

Openfront Marketplace registry and discovery tooling with explicit driver-owned booking handoff

Planned driver operations, one platform

Independent drivers, cooperatives, and fleets that want to operate a direct ride-booking service without surrendering their rider relationships and operational control to a centralized marketplace.

US
EU
AP

Run it wherever you operate

Run the application and database in infrastructure the driver or fleet chooses, own rider and operational records, and participate in interoperable discovery without transferring transaction control to a central marketplace. Production operation still requires applicable licensing, insurance, safety processes, legal review, and approved mapping, identity, payment, and communications providers.

Workflow Planned interoperability
Current workflows and operating signals
1
Openfront Marketplace registry and discovery tooling with explicit driver-owned booking handoff
2
Provider-neutral adapters for maps, location, identity, payments, messaging, and other operator-selected services
3
Driver and service discovery, service areas, availability, quotes, and immediate or scheduled ride requests
Openfront Marketplace registry and discovery tooling with explicit driver-owned booking handoff
Provider-neutral adapters for maps, location, identity, payments, messaging, and other operator-selected services

Planned interoperability

Driver-owned ride discovery, quotes, booking, scheduling, trip management, payments, safety records, and marketplace interoperability.

Audience

For the teams operating this workflow

Independent drivers, cooperatives, and fleets that want to operate a direct ride-booking service without surrendering their rider relationships and operational control to a centralized marketplace.

Ownership

Run it on infrastructure you choose

Run the application and database in infrastructure the driver or fleet chooses, own rider and operational records, and participate in interoperable discovery without transferring transaction control to a central marketplace. Production operation still requires applicable licensing, insurance, safety processes, legal review, and approved mapping, identity, payment, and communications providers.