Who founded TechnoRides?

Matias Baglieri founded TechnoRides in 2012 — originally as DineroTaxi in Buenos Aires — and led its 2013 pivot into the TechnoRides network.

TechnoRides is the infrastructure of driving: an open protocol, sovereign nodes, and a network registry that let cities, fleets, platforms, and AI agents run regulated, interoperable mobility.

The infrastructure of driving

One protocol for moving people and things.

One protocol. Every mode of mobility. Drivers, companies, cities, countries, agents, and merchants, connected over a network of sovereign nodes.

Your node is yours, infrastructure, data, brand, pricing. The network is what makes it matter.

Request a demo See the platform

Built for every mode

For taxis, limos, shuttles, buses, freight, cities, and countries. Multi-modal, multi-actor, sovereign by design.

TaxisLimosShuttlesBusesFreightCitiesCountries

The problem

Mobility was built as islands.

Every company, every city, and every app reinvents the same dispatch, the same payments, the same driver verification and none of them talk to each other. Closed apps keep your data, your brand, and your customer relationship.

TechnoRides flips the model: not one more app, but the network everyone operates on.

How it works

Three layers, one network.

A sovereign node you operate, a registry that connects nodes, and an open protocol everyone speaks.

M09

Sovereign nodes

Every city, country, or company deploys a node on its own infrastructure. It runs everything operational (dispatch, pricing, trips, apps) with its brand and rules. Trip data never leaves the node.

M01

Global registryIn build · roadmap

Connects the nodes: routes orders across networks, keeps driver reputation and payments in an immutable ledger, and verifies that every participant is real.

M06

Open protocolIn build · roadmap

Drivers, AI agents, and merchants speak the same protocol to request or dispatch. Hail a ride, send a parcel, or dispatch a fleet, one interface.

See the platform

Build status. The network layer (registry, ledger, roaming, 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.

Who it’s for

Six actors, one network.

Each gets the surface that fits them and the same verified, portable identity underneath.

For people behind the wheel

Drivers

A verified identity and a reputation that travels with you, portable across every node on the network, not locked to one app.

For operators

Companies

Run your fleet on infrastructure you own (dispatch, payments, tracking) with your brand and pricing, then plug into the network.

For public mobility

Cities

Operate a sovereign node for urban mobility (your rules, your data, your reputation) interoperable with neighbors through the registry.

For national infrastructure

Countries

National transport as critical infrastructure: data sovereignty, governance with due process, and cryptographically auditable payments.

For automation

AI agents

Agents speak the open protocol to request or dispatch, hail a ride, send a parcel, or coordinate a fleet through one programmatic interface.

For commerce

Merchants

Move goods over the same network that moves people, request delivery, dispatch a parcel, and settle through an auditable ledger.

Explore solutions

Why it’s different

We don’t compete for your customer. We give them back to you.

Closed ride-hailing apps and generic dispatch tools both keep something from you. TechnoRides keeps nothing.

Capability	Closed ride-hailing app	Generic dispatch software	TechnoRides
Your brand on the apps	No	Yes	Yes
You own the data & customer relationship	No	Partial	Yes
Federated network across operators	No	No	In build · roadmap
Portable driver reputation	No	No	In build · roadmap
Multi-mode (people & freight)	Partial	Partial	Yes
Open to AI agents & merchants	No	No	In build · roadmap

Roadmap, not a claim. The federated network, portable reputation, and agent/merchant access depend on the network layer (registry, ledger, protocol) which is in build. The operation plane (brand, data ownership, multi-mode operations) ships today.

Enterprise-grade

Built for institutions that can’t afford to guess.

For governments and critical operators: data sovereignty, an availability SLA, governance with due process, and cryptographically auditable payments and reputation.

See enterprise capabilities

Data sovereignty. Trip data stays inside the node; policy is set by jurisdiction.
Availability SLA. Operate transport as critical infrastructure, with committed uptime.
Governance with due process. Auditable rules, appeals, and a verifiable record.
Auditable payments & reputation. Cryptographically verifiable settlement and standing.

Proof

More than a decade building dispatch for transport operators.

~1s

Automatic dispatch time

−77%

Setup time since launch

Countries with presence

Verify before publishing. Figures reflect a decade of dispatch work across multiple countries and are indicative, confirm current numbers (dispatch latency, setup-time reduction, country count) before this page goes live.

Get started

Build on the network, not against it.

A node disconnected from the network isn’t a transport network, it’s a database. Deploy yours, keep what’s yours, and join the network.

Request a demo Talk to sales