ARRIVEOS

ArriveOS is an autonomous travel operating system. Its fundamental object is not a ticket or a route but an arrival objective: who is traveling, where they need to be, by when, and what the system is authorized to do about it. The engine continuously asks what sequence of actions maximizes the probability that the traveler arrives on time — and continuously acts on the answer.

The system protects an outcome — the arrival — not a route. Launch geography is the European Union, with EUR pricing and GDPR-native data handling. The project is in active development and is not publicly released.

Travel tools protect routes, not arrivals. A planner produces an itinerary and stops there; when a leg fails, detecting the failure and repairing it — rebooking, rerouting, notifying whoever is waiting — becomes the traveler's problem.

The real product is the outcome: being there at the agreed time. That is a continuous process of monitoring and intervention, not a search result.

Model the objective, not the itinerary. An arrival objective carries the deadline, the budget, the acceptable modes of transport, and the actions the system is authorized to take on the traveler's behalf.

Repair in the open. When a leg degrades, the engine detects, decides, and repairs — rerouting, rebooking, notifying stakeholders — and every intervention is visible in the live itinerary.

A Next.js application with a service-oriented backend. Live EU rail and coach data arrives via GTFS and GTFS-RT feeds, with per-source circuit breakers, response caching, and in-flight request coalescing; flights come from a real fare API when credentials are configured and are never synthesized when they are not. Persistence runs on PostgreSQL, and GDPR obligations — full data export and erasure — are first-party features rather than afterthoughts.