Data sovereignty
The operation runs on your infrastructure. You audit it; we don't see your trips. Trip and citizen data never leave the node.
For cities
Your city's mobility app. Sovereign by design.
A platform with the city's brand, deployed on your infrastructure, connecting every local operator under your rules. Your city is a network — and it runs on infrastructure you control.
The model
A sovereign network.
Your city is a network. It runs on infrastructure you control, with your brand, your regulated fares, and your driver requirements. Trip and citizen data never leave the node.
The global registry only adds what makes the network strong — verified drivers, valid reputation, auditable payments — without touching your operation.
Build status. The city node, your branded app, dispatch, payments and tracking ship today on the operation plane. The global registry that adds portable verification and reputation across networks — registry, ledger and roaming — is on the roadmap and shown as a target architecture, not a live service.
What stays · what's added
01
M03
Runs on your infrastructure
You operate the node and audit it. We don't see your trips — the operation is yours end to end.
02
M09
Carries your brand
One city app — or each affiliated company with its own logo — under your fares and your driver rules.
03
M06
Plugs into the registry
Verified drivers, valid reputation and auditable payments — added without touching your operation. In build · roadmap
Why a city chooses it
Public infrastructure, not a private app.
A closed platform owns your riders, your fares and your data. A sovereign node hands all three back to the city — and lets local operators compete without surrendering their identity.
One app, every operator
Local sites and companies affiliate to your node; citizens use one city app — or each company runs with its own logo, under your rules.
Regulated fares
You set the fare ceiling; no company can exceed it. Full transparency to the passenger, before the trip begins.
Citizen safety
A panic button you can integrate with your emergency system, plus live trip sharing so a rider's journey can be followed in real time.
Modernize the taxi sector
Local companies compete with global apps without losing their identity — or handing their data to a third party.
Public-policy programs
Supports schemes like vehicle restriction, electronic payments, and real-time mobility metrics — measured on data you hold.
Regulated fares
You set the ceiling. No one exceeds it.
Every operator affiliated to the node prices under a ceiling you define. The passenger sees the full fare before the trip starts — and no company can quote above the cap the city has set.
Fare ceiling · illustrative
City capOperator A$8.40
Operator B$9.20
Operator C$7.10
City cap$9.60
// Values illustrative — your ceiling and operator pricing are configured per city.
Why it's different
The city should own its mobility layer.
A closed app extracts the rider relationship, the data and the pricing power. A sovereign node keeps all three inside the city's control.
| What the city controls | Closed ride-hailing app | TechnoRides city node |
|---|---|---|
| Trip & citizen data stays inside the city | No | Yes |
| One app for every local operator, under city rules | No | Yes |
| City-set fare ceiling no operator can exceed | No | Yes |
| Panic button wired to the city emergency system | No | Yes |
| Local taxi sector keeps its brand & identity | No | Yes |
| Verified drivers & portable reputation across networks | No | Roadmap |
Build status. Data sovereignty, the single city app, regulated fares, citizen-safety tooling and policy-program metrics ship today on the operation plane. Verified drivers and reputation that travel across the registry — registry, ledger and roaming — are on the roadmap and shown as a target, not a live service.
The city stack
A node the city runs — and a registry it plugs into.
The operation plane is what ships today: your node, your branded app, dispatch, payments and tracking, all on infrastructure you control. The network plane — verified identity and reputation across cities — is on the roadmap.
You audit the node. We never see the trips. The registry adds strength without reaching into your operation.
City deployment · operation plane + roadmap
M03
M03
The Node
The city's live network — dispatch, payments and tracking — running on infrastructure you control.
M09
M09
White-label city app
One app under the city's brand, or each affiliated company with its own logo — all under your rules.
M10
M10
Dispatch & safety
Automatic dispatch, regulated fares, the integrable panic button and live trip sharing.
M06
M06
Network Registry & Ledger
Verified drivers, valid reputation and auditable payments across networks. In build · roadmap
For public institutions
Book an institutional meeting.
Tell us about your city and the mobility outcomes you're accountable for. We'll walk through a sovereign-node deployment, data-handling, regulated fares and the safety integrations — and how it fits your procurement and policy frameworks.
Get started
Deploy a sovereign city node.
Your brand, your infrastructure, your rules — connecting every local operator, with trip and citizen data that never leaves the node.