What outlives the break.
Institutions migrate cryptography before Q-Day; vehicles become liable computers; we monetize the nearer seam first (QUANTOM waitlist) and earn Ride. The public horizon is 2029 — a hoped-for authorized corridor only after permits. Earliest 2028 only if those gates are already true. Commercial passenger service is not authorized.
A ride is a closed sequence, not a marketplace.
There is no driver to hail, rate, or tip. The passenger requests; the fleet assigns; the vehicle arrives, carries, and ends. Remote assistance exists for edge cases — it does not sit in the front seat. Integrity of the trip record is an engineering claim, not a badge.
App, not curb chaos
Origin, destination, accessibility needs, party size. The request is a structured intent — not a broadcast to gig workers. Companion apps are native (iOS SwiftUI, Android Compose) and listed separately from this site.
Fleet, not a driver pool
A vehicle already in the operational design domain is matched. Humans do not bid. Cities and depot partners are the B2B counterpart — see Fleet / Operators.
Autonomy under an ODD
The vehicle operates without a safety driver in the cabin when — and only when — regulators have authorized that mode. That authorization has not been filed. The architecture is described on Safety & Autonomy.
A receipt that can be checked
Trip receipts are shaped as Falcon-1024 inscriptions — the same signature family verified on-chain by Algorand's native falcon_verify. The reference application is TestNet 763809096. No Ride MainNet writes are live. Verify the protocol, not our word: trelyan.foundation/verify.
Driverless is a safety case, not a slogan.
TRELYAN Ride does not anthropomorphize the stack. Perception, prediction, planning, and control are engineered subsystems. Remote assistance can advise, authorize a pullover, or dispatch support — it is not a hidden chauffeur. Data collected for autonomy is listed, limited, and lawful-basis gated; it is not a surveillance product.
A trip record that survives the break.
A classical signature on a fare receipt is a deferred forgery the day a cryptographically relevant quantum computer arrives. Ride receipts are specified to the same Falcon-1024 (NIST-selected 2022; FN-DSA / FIPS 206 still in development) shape used by the Foundation inscription protocol, with QRL considered as a complementary post-quantum ledger rail — under evaluation, not a claim of live dual-writes.
What is demonstrated today lives on Algorand TestNet application 763809096, unaudited. What is not demonstrated: MainNet commercial receipts, confidentiality of the trip (Falcon is a signature scheme), or legal admissibility of an inscription as a tax invoice.
A phased register. Zero authorized markets.
Phase I is the United States — ten named cities. Phase II densifies Switzerland, then Europe country bands, the French Riviera, Monaco as its own city-state, and an eight-city Europe need-priority list. After Europe: Middle East, Japan, China. None of these is a live robotaxi market.
US, Switzerland, Europe
Ten US majors; Swiss majors plus St. Moritz and Zug; Italy / France / Netherlands / UK / Germany / Spain bands; Nice and Cannes on the Côte d’Azur; Monaco on its own line. Every gate: not filed.
City dossier →Middle East, Japan, China
Israel and the UAE, then Tokyo / Osaka / Nagoya, then Shanghai / Beijing / Shenzhen / Guangzhou / Hangzhou. Names on a register, not concessions.
City dossier →If the structure is ready, the list is open.
Request a briefing for a future trial, join the TestFlight or APK waitlist, or write as a city or depot partner. Nothing on this page books a car tonight.