The Node
Each client — city, country, or company — deploys a node on its infrastructure. The node runs everything operational: dispatch engine, fleet, pricing, white-label apps, local payments, tracking.
See the NodePlatform overview
One platform, two planes.
TechnoRides is an operation plane — the nodes, where everything happens — and a network plane — the registry, which connects and certifies. On top, an open protocol that agents and merchants enter through.
Operation plane
The Node — dispatch, fleet, pricing, apps, payments, tracking
Network plane · roadmap
The Registry — routing, identity, ledger, settlement, governance
Build status. The network plane — registry, immutable ledger, cross-network roaming and the open protocol — is on the roadmap and shown as a target architecture, not a live service. The operation plane (node, apps, dispatch, payments, tracking) is what ships today.
How it fits together
The operation plane runs the work. The network plane makes it matter.
Each client deploys a node on its own infrastructure. TechnoRides operates the multi-region registry that connects every node into one network.
The Registry
Operated by TechnoRides, multi-region. It routes orders across networks — roaming, agents, merchants — and certifies driver reputation and payments in an immutable ledger, plus identity/KYC, settlement, governance, and monitoring.
See the RegistryThe Protocol
The common interface nodes, agents, and merchants speak. Versioned, with SDKs and a conformance suite. It's what turns a set of apps into a network.
Read the protocolSovereign by design
Trip and passenger data never leave the node. The registry only receives minimal reputation and payment events — hashes, no personal data — and health signals. Your brand, your fares, and your rules are yours.
Operation plane
Everything the node runs.
The system the client deploys on its own infrastructure. It runs everything operational and connects to the registry through a single secure component — the Node Gateway.
The Node
The sovereign deployment. Real-time dispatch, multi-type fleet, regulated pricing, white-label apps and panels, local payments, GPS tracking, and the Node Gateway — enrollment, heartbeat, authorization, ledger writes.
Self-hosted or managedData stays in node
Explore White-label apps
Passenger and driver apps, operator and authority panels — with the client's brand, logo, palette, and legal text. Publishable in your own App Store and Google Play accounts. One multi-company app or one app per company.
Passenger & driverOperator panels
Explore Dispatch
The operational heart. Turns orders into driver assignments in real time — proximity, vehicle type, reputation and local rules — with ~1-second automatic dispatch extended to every mode, reservations, shared capacity, and freight.
~1s auto-dispatchAuthorization check
Explore Payments
Local multi-method charging — cash with reconciliation, tokenized card, local wallets — plus multi-currency, corporate accounts with anti-fraud vouchers and e-invoicing, and driver settlement. Every payment certified in the ledger.
Tokenized cardCorporate accounts
Explore Tracking
Real-time fleet telemetry. High-frequency GPS ingestion, an in-memory geospatial index for the dispatch hot query, live streams to apps and panels, and trip traces that feed final pricing and reports. Traces never leave the node.
In-memory geo indexLocal geofences
Explore M09
Node Gateway
The single secure component that connects the node to the registry — enrollment, heartbeat, authorization, and signed ledger writes. The registry never sees your operation: only minimal reputation and payment events and health signals.
In build · roadmap
Explore Network plane · roadmap
The registry that connects and certifies.
Operated by TechnoRides, multi-region. It routes orders across networks and certifies reputation and payments in an immutable ledger — the equivalent of being online with the card network, for a bank.
M01
Network Registry
The directory and control plane of the network. Registers every network — city, country, company — maintains its identity and state, and issues the dispatch authorization a node renews while it complies. Without a valid authorization, a node can't process orders.
Dispatch authorizationIn build · roadmap
Explore M03
Reputation & payments ledger
An immutable, verifiable record of driver reputation and network payments — append-only, cryptographically signed, validated by the network's own nodes. Reputation belongs to the driver and travels across networks. Stores only hashes and minimal amounts.
ImmutableInclusion proofsIn build · roadmap
Explore Identity, settlement & governance
The registry also handles identity/KYC, settlement, governance, and monitoring. It validates the ledger through a permissioned chain with consensus among the networks themselves — proof-of-authority. No mining, no disproportionate energy cost: integrity without waste.
Proof-of-authorityIn build · roadmap
See governance Build status. The network layer — registry, ledger, roaming, protocol — is on the roadmap and shown as a target architecture, not a live service. It is not billed today.
The interface · M06 · roadmap
The common language of the network.
The specification nodes, agents, and merchants speak: message contracts, authentication, versioning, and public routing rules. It's what turns a set of apps into a network.
- Orders and status events for every mode — moto, car, luxury, van, shuttle, bus, freight
- Cross-network routing with public, neutral rules
- Signed ledger events — reputation, payments
- Heartbeat and authorization of the node lifecycle
- Mutual authentication (mTLS) and per-message signatures
Open & versioned
Semantic versioning with migration windows and dual active versions on major changes. A mandatory conformance suite for nodes, and SDKs for nodes, agents, and merchants.
Semantic versioningConformance suiteIn build · roadmap
Extensible: an extension point is reserved for future interoperability with external platforms — reserved, not required.
Interfaces
Enter the network programmatically.
Agents and merchants reach the whole network through one integration — the protocol is open, but admission still requires verification. No KYC bypass.
M16
Agent API
Request, offer, and orchestrate drivers programmatically — the mobility protocol for AI agents, over the whole network. Request creates orders of any mode and the registry routes; offer publishes driver availability; orchestrate quotes and coordinates multi-order by zone.
POST /agent/ordersGET /agent/orders/{id}POST /agent/quotesPOST /agent/supply/offersPOST /agent/webhooksNo KYC bypassIn build · roadmap
Read the referenceM17
Merchant API
Dispatch last-mile orders with the network's capacity — the right vehicle for each shipment, no fleet of your own. Create a dispatch with pickup, drop, and parcel data; the registry routes to the city node; your customer tracks live from a public link, no app. Proof of delivery: photo, signature, or PIN.
POST /merchant/dispatchesCash on deliveryBatch importIn build · roadmap
Read the referencePrivacy by design. Card data is tokenized at the gateway and parcel contents are never recorded — only class, size, and weight. The ledger stores only hashes, amounts, and the method class.
Get started
Your node is yours. The network makes it matter.
Deploy a sovereign node to run your operation, and connect to the registry that turns a set of apps into a network of networks. A node disconnected from the network isn't a transport network — it's a database.