MaaS

SOLUTIONS

← back to all Solutions

Problem statement

Mobility as a Service requires native multi-tenancy, not forced integration. Regional mobility networks, institutional multi-program deployments, and multi-stakeholder environments fail when each service requires separate infrastructure, separate APIs, and separate maintenance cycles. You end up maintaining three platforms, coordinating four deployment schedules, and explaining to the CTO why none of them talk to each other.

What Playmoove enables

Multi-tenant federation model

Single platform instance manages multiple independent programs or entities, each with isolated fleets, clients, zones, pricing structures, and branding—no cross-contamination, complete operational autonomy

All booking modes active simultaneously

Operators within one federation can mix car-sharing, rental, corporate, ride-hailing models without platform constraints or custom development

Versioned REST API with backward compatibility guarantee

MaaS aggregators integrate once, remain stable across platform upgrades, and access all operators via unified endpoint

Cross-operator client onboarding

Registration tokens pre-configure plans, credits, group assignments for partner operator enrollment; federation-level client association enables user accounts across multiple services

Real-time vehicle availability API

Location-based queries return available vehicles across all federated operators with segment-based filtering and pricing data for aggregator displays

Architecture
Overview

Federation layer sits above operator instances—each federation is a complete operational entity (fleet, clients, zones, rates, policies) sharing platform infrastructure but maintaining data isolation. Hierarchical organization (Federation → Group → Client → Driver) enables inheritance of rates and policies at each level. API versioning ensures aggregator integrations remain stable as the platform evolves. Single deployment serves multiple cities, multiple operators, multiple booking models—unified management, independent operations.

Concrete
Example

A regional mobility network deploys Playmoove for three cities: City A operates municipal car-sharing (free-floating mode), City B runs campus bike-share (station-based), City C manages corporate van pools (round-trip). Each city is a separate federation with independent branding, pricing, and policies. MaaS aggregator integrates once via REST API, exposes all three services in a unified app, handles cross-city bookings. New operator (City D ride-hailing service) onboards by creating a fourth federation—no aggregator API changes, no platform migration, operational in days not months.