Platform

On-demand transit platform

The shared product layer behind microtransit, demand responsive transport, shuttles and accessible services. One tenant, several service products if you need them.

ISO 27001 ISO 9001 ISO 14001 TISAX Level 2 ISO/IEC 27017 ISO/IEC 27018
Headset, laptop map and smartphone connected by green lines to a small van icon
ISO 27001 operations
White-label passenger and driver apps
Live assignment and pooling
European software vendor
Overview

How the platform is used

On-demand transit is the practical term many agencies use when they do not want a vendor-specific product name. It covers app-booked vans, telephone dial-a-ride, deviation from a corridor and first-mile links to rail.

The platform is the common stack: identity, stops, vehicles, tariffs, assignment, driver tools, passenger notices and exports. Service products such as microtransit or hotel shuttles are configurations of that stack.

Operators keep their own carrier contracts. maas.maker does not take a ride marketplace cut from the passenger.

On-demand transit platform

The shared product layer behind microtransit, demand responsive transport, shuttles and accessible services. One tenant, several service products if you need them.

Multiple service products

A tenant can run a public zone, an eligibility-based product and a closed shuttle with separate rules and branding.

Feeds and APIs

GTFS for published information and REST for partners sit beside the operational system, not instead of it.

Headset, laptop map and smartphone connected by green lines to a small van icon

Call-centre continuity

Telephone booking remains a first-class channel for older riders and for services that never go fully app-only.

White-label presence

Passenger-facing surfaces carry the operator brand. The vendor name stays in the contract, not on the stop pole.

Headset, laptop map and smartphone connected by green lines to a small van icon
Operations

How the platform is used

On-demand transit is the practical term many agencies use when they do not want a vendor-specific product name. It covers app-booked vans, telephone dial-a-ride, deviation from a corridor and first-mile links to rail.

The platform is the common stack: identity, stops, vehicles, tariffs, assignment, driver tools, passenger notices and exports. Service products such as microtransit or hotel shuttles are configurations of that stack.

Request a demo
Implementation

How a tenant goes live

Scope

We walk through service type, fleet, booking channels and the reports you already have to file.

Configure

Branding, stops, hours, vehicle classes and assignment rules land in one tenant.

Train

Dispatchers, drivers and coordinators practise on the live board before opening hours.

Go live

The first operating weeks are coached. Exceptions, not the happy path, are the real product.

What you actually buy

Modules you can combine. One tenant.

Start with booking, dispatch and the driver app. Add passenger apps, pooling rules, feeds and exports when the service needs them.

Explore the modules
See the platform in a working demo

A configured walkthrough, not a marketing video only. We look at your service type and fleet.

Questions teams ask

White-label software for booking, dispatching and reporting demand-responsive transport. It is not a consumer ride-hail brand.

No. Customers run the service with their own fleet or contracted carriers.

USD is the list-price base. You can switch the calculator to Australian dollars, New Zealand dollars or euro. Final contract currency is confirmed in a proposal.

Yes. Book a conversation and we walk through a configured tenant for your service type.

Contact

Plan a working demo

Share fleet size, service type and the outcome you need. We reply with a working demo path, not a generic brochure.

+43 50 556

maasmaker@anexia.com

Monday to Friday, 09:00–17:00 CET

Request a demo