04Technology · How the network is built
The architecture underneath the journey.
Orange Rides Network is a transportation platform built on one principle: if it matters, it is a structured record — and records with the right permissions are what everything else stands on.
01Journey infrastructure
One record per journey, from draft to arrival.
Every ride on the network is a structured journey record: a route, its checkpoints, the passengers on board, and the journey stage as it changes. Journeys move through defined states — from draft, to planned, to analysed — so every system that touches a journey sees the same shape of truth.
Route planning is deterministic: ride owners plan routes with professional mapping and routing data, and the same inputs produce the same plan. Reproducibility is a feature, not a compromise.
02PWA architecture
One installable app. Every role.
Orange Rides Network ships as a progressive web app — the same application serves passengers, ride owners and platform staff, with the interface and permissions shaped by role. Passengers join a journey by scanning the QR code their ride owner shares; no app store is required.
Installable
Runs in the browser, installs like an app
Role-shaped
Passengers, ride owners and staff each get their own surface
QR-first joining
A scan is all a passenger needs to board the right journey
03ORION intelligence architecture
An intelligence layer with guardrails designed in.
ORION serves passengers, ride owners and staff through a single conversation system. Capabilities are gated — by role and by subscription — and the architecture is built so that consequential operations cannot run themselves.
Conversation
One chat system, three surfaces — passenger, owner dashboard, staff operations. Answers are grounded in the journey data behind the question.
Capability gating
What ORION may do depends on who is asking — and their plan. Consequential operations resolve to “requires human approval” and are never executed automatically.
Structured outputs
Risk assessments carry level, rationale and contributing factors, persisted with the journey. Suggestions enter a two-stage human approval path; reports are prepared for ride owners.
04Journey monitoring & checkpoints
Watched while it moves. Remembered after it arrives.
Journey status is recorded as it changes, and the people with a stake see it: passengers follow their journey, ride owners see their operation, and platform staff can see activity across the network and act on it while journeys are still moving.
Checkpoints give a journey a planned shape — defined points between pickup and destination that stay part of the record the whole way.
Pickup
Passengers check in with the journey QR.
Checkpoints
Defined points, part of the record.
En route
Status recorded as it changes.
Arrival
A complete journey record remains.
05Data infrastructure
A database that enforces the rules itself.
The network runs on managed PostgreSQL. Authorization is enforced at the database level with row-level security: every table defines who may read and write each row, and role checks — staff, ride owner, passenger — live in the data layer, not just the interface. A client cannot ask its way past the database.
06Security architecture
Bounded by design.
Security on Orange Rides Network is about boundaries: who can reach what, and what any single actor — human or machine — can do without someone else knowing.
Server-side gates
Private surfaces verify identity and role on the server before anything renders
Fail-closed operations
When ORION touches something consequential, the answer is “wait for a person” — never silent execution
Clear public/private line
This website exposes the story — never dashboards, journey data or internal systems
Architecture is a promise kept quietly.
The intelligence layer is where the architecture becomes visible. See what ORION does today — and where it is going.