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.
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.
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.
Explore how organisations use Playmoove to power real-world mobility services, adapting a flexible and configurable platform to different business models, operational requirements and market needs.
A Mobility as a Service platform connects different transport and mobility services through a common digital infrastructure. Playmoove provides a modular, multi-tenant architecture that helps organizations integrate operators, fleets, booking models and operational policies while maintaining control over individual services.
Yes. Playmoove uses a federated architecture that allows multiple operators or programs to share platform infrastructure while maintaining separate fleets, service areas, pricing rules, users and operational configurations.
Yes. Playmoove offers versioned REST APIs designed to support integrations with external mobility applications and aggregators. Available interfaces include access to vehicle availability and operational data, with integration requirements defined according to the connected systems.
Yes. Playmoove supports multiple operational models, including shared mobility, automated rental, corporate mobility and ride-hailing. These services can be configured within a common platform architecture, allowing organizations to develop mobility ecosystems without relying on separate software infrastructures for each model.
Yes. Playmoove allows federated operators to maintain separate branding, pricing structures, geographic zones and operating policies. This makes the platform suitable for multi-city and multi-operator environments where centralized infrastructure must coexist with independent service management.