Real-time dispatch
Multi-mode by design — taxi, minibus, moto and cargo. Reservations, shared capacity and freight all dispatch from the same engine. M01
Operation plane · M09
The Node. The system you deploy on your own infrastructure.
Everything operational — dispatch, fleet, pricing, white-label apps, payments and tracking — runs inside your node, under your brand. It connects to the network through a single secure component: the Node Gateway.
M09 · runs on your infrastructureTrip data stays local
Operator console · sample data
Operations
NODE sf-yellow · last sync 12s ago · sample data
Active trips
1,284
+6.2% vs avg
Online drivers
312
flat
Settled today
$84,210
+3.1%
Median ETA
4.2 min
+0.4 min
Fleet · multi-type, multi-company
| Driver | Vehicle | Mode | Company | Status | Trips |
|---|---|---|---|---|---|
| A. Morales | 7RJ 204 | Taxi | City Cabs | En route | 9 |
| K. Idris | MN-118 | Minibus | Línea Verde | Pickup | 12 |
| P. Okoye | MT-902 | Moto | City Cabs | En route | 7 |
| L. Chen | CR-440 | Cargo | HaulCo | Reserved | 4 |
| D. Farah | 8KL 071 | Taxi | Línea Verde | Offline | 0 |
Sample screen. This console is an illustrative product still with honest placeholder data — not a live connection. Dispatch, fleet, pricing, apps, payments and tracking run on the node today; the network plane the Gateway links into (registry, ledger, roaming) is on the roadmap.
Inside the node
Everything operational, in one deployment.
The node runs the whole operation end to end. Each surface in the sidebar above is a real module — and every one of them runs on the infrastructure you choose.
Fleet management
Multi-type and multi-company. One node can run several brands and vehicle classes side by side, each with its own rules. M03
Pricing engine
Local and regulated pricing — your fares, your zones, the local authority's caps. Configured per company, per mode. M06
White-label apps & panels
Passenger and driver apps, plus operator and authority panels — all carrying your brand. See white-label apps → M13
Payments & accounts
Local payments and corporate accounts — vouchers, invoicing and balances run inside the node. M14
Real-time GPS tracking
Live positions for every vehicle on the map — for operators, passengers and the local authority. M15
One more module sits at the edge. The Node Gateway (M16) is the single secure component that connects your node to the network — enrollment, heartbeat, authorization and ledger writes. Everything else stays inside.
The edge · M16
One secure component talks to the network. Nothing else does.
The Node Gateway is the only part of your deployment that reaches out. It enrolls the node, sends a heartbeat, carries an authorization token, and writes minimal events to the ledger. Your operation never connects to the registry directly.
Enrollment. The node registers once with a signed identity; the registry knows the node exists, not what it does.
Heartbeat. A periodic health signal — up, in-sync, reachable. No trip or passenger data rides along.
Authorization. A rotating token authenticates every Gateway call. Revoke it and the node drops off the network without losing local operation.
Ledger writes. Only minimal reputation and payment events — hashes, no personal data — are written outward. network plane · roadmap
Node Gateway · status (sample)
Heartbeat
Last beat12s ago
Interval30s
StateLinked
Authorization
Node IDnode_sf-yellow
Tokengw_live_7c1a…9f02
Rotatesin 18h
Egress: health + hashed events only. registry · roadmap
// Gateway status shown with sample values. Enrollment, heartbeat and authorization are the node's edge contract; the registry and ledger it links into are network-plane — roadmap, not a live service.
Sovereignty principle
Trip and passenger data never leave the node.
The registry never sees your operation. It receives only minimal reputation and payment events — hashes, no personal data — and health signals. Your brand, your fares and your rules are yours.
Stays in the node
Trip details & routes
Passenger identity & contact
Driver & vehicle records
Fares, zones & pricing rules
Corporate accounts & invoices
Your brand, logo & legal text
Leaves via the Gateway
Health signals (heartbeat)
Reputation events (hashes)
Payment events (hashes)
No trip data
No passenger data
No personal data
// The reputation and payment ledger the Gateway writes to is the target network plane — roadmap, not a live settlement service. The sovereignty boundary itself ships with the node.
Deployment
Run it where your rules require.
A node deploys two ways: TechnoRides-managed cloud, or your own infrastructure. Either way the sovereignty boundary is the same — only the Gateway reaches the network.
TechnoRides-managed cloud
We host and operate the node for you. Fastest to go live, with the same data boundary — your trip and passenger data stay isolated to your node.
Your own infrastructure
On-prem or sovereign cloud, under your control and your jurisdiction. The node runs where your regulator and your policy require it to.
// Deployment shapes and the operational stack ship today. Forms on a published node app must connect to your CRM before go-live. The network plane the Gateway links into is on the roadmap.
In the platform
The node is the engine. The network makes it matter.
M09 is the operation plane you deploy and own. The Gateway is the one thread to the network plane — registry, ledger and protocol — which is on the roadmap.
M13 · operation plane
White-label apps
The passenger, driver, operator and authority surfaces the node drives — all under your brand.
See white-label apps →M10 · network plane · roadmap
Network Registry
Where the Gateway enrolls. The registry knows nodes exist; it never sees the operation inside them.
See the registry →M17 · network plane · roadmap
Protocol
The shared language nodes will speak to roam trips and settle across the network.
See the protocol →Get started
Deploy a node that's yours.
Dispatch, fleet, pricing, apps, payments and tracking — on your infrastructure, under your brand, with one secure Gateway to the network. We'll walk you through deployment and a live demo.