For South African taxi and e-hailing operators

Taxi App Development & White-Label Booking Software for South Africa

Launch your own branded taxi booking software and dispatch platform: a passenger app, a driver app and a dispatch console you control. Built around your fleet and cities, then configured, branded and supported remotely by the RuteAppz team in Coimbatore, India.

  • Passenger app
  • Driver app
  • Dispatch console
  • Admin panel
Taxi Platform admin panel showing booking management (demo data)
Taxi Platform passenger app booking home screen (demo data)
Admin panel: booking managementPassenger app: booking homeDemo environment with sample data

Taxi software for operators who want to own their platform

This page is for businesses that want to run their own taxi, e-hailing, private-hire or airport-transfer service on their own branded software, instead of depending on someone else's app. You are buying software and its delivery, not rides. RuteAppz does not operate a taxi fleet and does not have an office in South Africa: the platform is configured, branded and handed over to you by a remote team, and what it can do for your operation is confirmed in a scoping conversation first.

  • Your brand on the passenger and driver apps
  • A dispatch console and admin panel you operate
  • Fares, zones and vehicle types configured for your cities
  • Payments and rand pricing scoped to your requirements before anything is promised

Evaluating taxi software for South Africa?

Book a remote demo of the Taxi Platform

See the passenger app, driver app and dispatch console, and tell us about your fleet, cities and payment needs. We will say plainly what is available now and what needs scoping.

Taxi booking and dispatch software: what the platform includes

The RuteAppz Taxi Platform is four parts working from the same live data, so a booking made in the passenger app is visible to dispatch, followed by the driver and reflected in reports. This is the same product described on our Taxi Platform page; your deployment may enable a subset.

  1. Passenger app

    Passengers book trips, see a fare estimate, follow the trip live and rate it afterwards.

  2. Driver app

    Drivers go online, receive trip offers, navigate, complete trips and track earnings.

  3. Dispatch console

    Dispatchers see the live fleet, assign or reassign trips and respond to exceptions.

  4. Admin and business operations

    Admins configure fares, zones and roles, manage drivers and vehicles, handle safety and support, and run reports.

Passenger application

What your riders get in the branded passenger app.

  • Booking with stops

    Request a trip with pickup, drop-off and optional stops.

  • Ride options

    Choose from the vehicle and service types you configure, such as local, rental or outstation.

  • Fare and arrival estimates

    See an estimated fare and driver arrival before confirming.

  • Scheduled trips

    Book a trip for a later date and time.

  • Live trip tracking

    Follow the driver and trip status in real time. Tracking depends on location data from the driver's phone.

  • Promo codes and safety access

    Apply promotions you configure, and reach SOS and support from the app.

Driver application

What your drivers use day to day.

  • Availability

    Go online or offline, choose the active vehicle and share live location.

  • Trip offers

    Receive trip offers and details, and accept the ones you want.

  • Trip workflow

    Navigate to pickup, verify the passenger, start and complete the trip.

  • Cash collection records

    Confirm cash collected on a trip so it is recorded against the driver.

  • Earnings and statements

    See earnings built from final fares and your commission rules.

  • Notifications and safety

    Alerts for new and changed trips, and a route to safety and support.

Taxi dispatch software: admin and dispatch management

The control room for your operation.

  • Live operational view

    A real-time board of trips and the drivers handling them.

  • Assignment

    Match bookings to available drivers, with manual reassignment from the dispatch board.

  • Active trip monitoring

    Follow trips from pickup to drop-off and see exceptions that need attention.

  • Roles and access

    Separate permissions for admins, dispatchers and finance users.

  • Safety and support tools

    SOS alerts, incident tracking and support tickets. Your policies and response procedures remain your own.

  • Reports

    Trip, revenue and driver performance reporting.

Fleet management and fare configuration

Set the platform up around how you charge and how your fleet is organised.

  • Fare rules

    Configurable base fare, distance, time and surge rules, which you can set per service.

  • Service zones

    Define service areas and zone-specific rules for each city or branch.

  • Vehicle and service types

    Configure the vehicle categories and service types your fleet offers.

  • Driver and vehicle records

    Onboard drivers and keep vehicle details alongside trips and availability.

  • Commission rules

    Commission by percentage, fixed amount or slab for driver earnings.

  • Promotions

    Fixed or percentage promo codes with dates, limits and targeting.

Business models and operator use cases

The platform is a base you shape around how you operate. Fit and scope are confirmed in discovery.

  • Dispatch

    Taxi companies moving off phone and WhatsApp dispatch

    Bring bookings, drivers and trips into one system in stages, rather than switching everything at once.

    Read the migration guide
  • On-demand

    E-hailing, ride-hailing and private-hire operators

    On-demand and pre-booked trips under your own brand, with your own fares and driver commission rules.

  • Pre-booked

    Airport transfer and shuttle businesses

    Pre-booked pickups and drop-offs with airport, terminal and flight details, handled by dedicated workflows.

  • Business accounts

    Corporate and chauffeur transport

    Managed accounts for business travel, with vehicles and drivers under your branding.

  • Scale

    Multi-city and multi-branch operators

    Zones, fares and driver pools per branch with central reporting.

  • New venture

    Founders launching a regional ride service

    A ready base to launch from, customised to your market instead of built from a blank page.

Planning for South Africa

Planning a taxi platform for South Africa: what to settle first

These are the questions we work through with South African operators during scoping. Treat these as planning questions rather than product claims: none of them promises that a South Africa-specific feature already exists.

  • Operating licences and compliance

    Licensing and permit rules for taxi, e-hailing and private-hire services are set by South African transport authorities and can change. Confirm current requirements with the relevant authority before launch. RuteAppz provides software, not licensing or legal advice.

  • Rand pricing and tax

    Rand display, fare rounding and tax handling for your pricing are confirmed during scoping, before they are promised.

  • Cities, zones and airports

    Set up zones and fare rules per city, and decide where airport or long-distance pricing differs from in-city trips.

  • Vehicle types in your fleet

    The platform lets you configure vehicle and service types. Specialised vehicle classes beyond the configured model, for example shuttle vans, are scoped as customisation.

  • Safety and trust

    Decide how SOS alerts, incidents and driver or passenger blocks will be handled by your team, and train dispatchers on the admin tools.

  • Languages and connectivity

    Languages other than English are scoped per project. Live tracking and trip offers depend on mobile data and location on drivers' phones, so plan for patchy coverage in your service areas.

Compare

Payment integration requirements: what is documented and what is scoped

Payments are the area where South African operators most often have specific requirements. This table separates what the product documentation states from what needs project scoping, so nothing is promised that has not been confirmed.

 Status
Online card paymentsDocumented: through a configured payment provider (Stripe is named). Availability in South Africa is checked in scoping.
Cash tripsDocumented: cash collected is recorded against the driver.
In-app wallet and corporate or pay-later accountsDocumented in the product overview.
Local payment providers (for example PayFast)Not a pre-built integration. Can be evaluated in scoping, depending on the provider's API.
Pricing in rand (ZAR)To be confirmed during scoping.
Driver payoutsRecorded manually; automated payout providers are not assumed.

Customisation

Customisation and white-label branding

White-label branding is a deployment option and its scope is agreed per project. Not every option below is included by default.

  • Branding

    Your name, logo, colours and domain across the passenger and driver apps.

  • Pricing and zones

    Fare rules, service areas and zone-specific rules for your cities.

  • Service types

    Local, rental, outstation, airport, corporate and other services you want to offer.

  • Payments and integrations

    Payment methods and provider integrations, plus connections to your own systems, scoped to your requirements.

  • Notifications

    SMS and push trip alerts, and the wording of customer messages.

  • Android and iOS publishing

    App-store accounts and publishing are agreed per project.

Deployment options

Hosting and deployment options

Deployment options described on our Taxi Platform page. The right one for you is agreed during scoping.

  • Managed cloud

    Managed hosting with regular updates.

  • Dedicated environment

    A dedicated environment for your operation.

  • Client-owned server

    Deployed on infrastructure you control.

  • White-label setup

    Your branding across passenger and driver apps.

Working with a remote team

Development and onboarding approach

RuteAppz is based in Coimbatore, India, and delivers projects remotely. South Africa is about three and a half hours behind India, so calls, demos and WhatsApp conversations fit within a normal working day on both sides. Timing varies by scope, integrations and customisation.

  1. 1

    Discovery call

    Your fleet, cities, service types, payment needs and launch priorities.

  2. 2

    Scope and configuration

    Agree modules, fares, zones and what needs customisation, including payments and rand pricing.

  3. 3

    Branding and customisation

    Apply your brand and build the agreed changes.

  4. 4

    Integrations and testing

    Set up agreed integrations and test the booking, dispatch and payment flows end to end.

  5. 5

    Demo and handover

    Walk your dispatchers and admins through the console before launch.

  6. 6

    Launch and support

    Go live, with ongoing support agreed in your project.

Pricing factors

What affects the cost of a taxi app project

Every taxi project is scoped individually, so we do not publish fixed prices. These factors decide the quote, which helps when you compare vendors.

  • Apps and modules

    Which of the passenger app, driver app, dispatch console and extra modules you need.

  • Customisation depth

    How far your workflows, fares and screens differ from the standard platform.

  • Integrations

    Payment providers, maps, SMS and links to your own systems.

  • Hosting model

    Managed cloud, dedicated environment or your own server.

  • Branding and publishing

    App-store accounts, branding assets and Android and iOS release work.

  • Support and maintenance

    How much ongoing support and how many updates you want after launch.

Screenshots

See the platform (demo environment with sample data)

Mobile

Passenger app: booking home screen

Demo environment with sample data. Local, rental and outstation booking from the passenger app.

Mobile

Passenger app: choosing a ride option

Demo environment with sample data. Ride options with a fare estimate.

Web

Admin panel: booking management

Demo environment with sample data. Search, filter and manage bookings.

FAQ

Taxi app development for South Africa: common questions

Yes, as a software project: you get a branded passenger app, driver app and dispatch console that you operate. Whether your business may run a taxi or e-hailing service, and under which licence, is decided by South African transport authorities, not by the software. Confirm the licensing requirements that apply to you before launch.

Prefer to talk on WhatsApp? Message the RuteAppz sales team about your South Africa project.

Chat on WhatsApp (opens in a new tab)

Evaluating taxi software?

Talk to us about your South African taxi platform

Tell us about your fleet, cities and payment needs. Walk through the platform with us on a remote demo, and we will tell you plainly what exists today and what would need scoping.

Got an App Idea? Let's Turn It Into Reality, Faster!