L3
Service experience layer
Rider, driver, operator, and partner surfaces are tailored to each mobility service line.
Screens differ by service, but booking, dispatch, payment and control run on the same operating engine, and driver verification, sealing and cross-checking run on the same trust layer.
Service experience layer
Rider, driver, operator, and partner surfaces are tailored to each mobility service line.
Operating engine
Shared modules coordinate dispatch, fleet, payment, charging, and control workflows.
Trust layer
Driver verification, trip-record collection, blockchain sealing and third-party cross-checking come built in, so whoever receives a record can check it directly.
User touchpoints, shared operating modules and the trust layer are kept separate, so new services and regions reuse the same structure.
L3
Rider, driver, operator, and partner surfaces are tailored to each mobility service line.
L2
Shared modules coordinate dispatch, fleet, payment, charging, and control workflows.
L1
Driver verification, trip-record collection, blockchain sealing and third-party cross-checking come built in, so whoever receives a record can check it directly.
Shared modules connect dispatch, fleet, payment, charging, and control work so each service flow can be configured quickly.
AI-based demand-responsive dispatch algorithm. Using real-time route optimization and cost function design, it chooses a dispatch that fits the situation and records why it was chosen.
From vehicle registration to driver management and real-time tracking. Provides all vehicle management functions necessary for operations.
One-stop from reservation to payment and settlement. Supports global PG integration and mileage systems.
OCPP 2.0.1 based charger management system. Integrated management from charger onboarding to remote control and promotions.
Operational status at a glance. Ensures service quality with real-time monitoring, incident management, and SLA dashboards.
Turns records produced by the operating engine into evidence the receiving party can check.
Verifies drivers with the government mobile driver's licence and decentralised-identity (DID) credentials, and attributes each record to that driver.
Collects trip data from in-vehicle devices (OBD, DTG) in a standard format.
Seals scores, trip summaries and calculation basis on a blockchain.
Insurers, operators and contracting agencies cross-check and verify the same record themselves.
Map the initial service scope, roles, and integrations, then define the operating foundation your launch needs.