Aurelis exists to demonstrate what a serious charter platform looks like
This is a template. The brand, the fleet, the destinations, the clients and every figure on every screen are invented. What is not invented is the product architecture underneath: a typed dataset, derived state, business rules that refuse impossible actions, and three workspaces that are genuinely one product.
Where Aurelis came from
Aurelis was written as the flagship demonstration of a private aviation platform: the public brand experience, the charter builder, the illustrative quote engine, the client portal and the operations workspace, all sharing one dataset and one set of business rules.
The premise is a small charter house in London that treats the schedule as the product. Twelve aircraft, fifteen cities, one desk. The interface is built the way a serious operator would want it: dense where it needs to be precise, quiet where the client should feel unhurried.
Everything is deliberately fictional. There is no operating certificate, no availability feed, no payment provider and no customer data. What remains is the thing worth demonstrating — how the pieces of an operation fit together, and what happens on every screen when one of them changes.
The demonstration dataset
- Aircraft
- 12
- Destinations
- 15
- Workspaces
- 3
- Real bookings
- 0
Across six cabin classes
Five regions, plotted by coordinate
Public, client and operations
Nothing is ever reserved
Three rules the product is built on
Derive, never duplicate
A trip has one status, and it comes from the operational record. A proposal has one total, and it comes from its line items. If two screens can disagree, one of them is a bug.
Refuse the impossible
An aircraft in maintenance cannot be quoted. A trip cannot skip a stage. An expired proposal cannot be approved. The interface should make the wrong action unavailable rather than apologise for it afterwards.
Say what is fictional
Every price, availability, aircraft and client in this product is invented. Where that matters — and it always matters — the interface says so plainly rather than in a footnote.
A fictional team
These people do not exist. They are here to show how the roles in a charter operation relate to one another — and to the roles you can sign into in the demonstration portal.
Marguerite Ellory
Founder & Managing Director
Twenty years in executive travel before deciding the schedule mattered more than the cabin.
Idris Kalu
Director of Operations
Runs the desk. Believes an itinerary that cannot survive a two-hour delay was never planned properly.
Béatrice Nyland
Head of Concierge
Holds the preferences, the dietary notes and the standing arrangements for every account.
Rafael Oduya
Fleet & Availability
Decides which airframe answers which sector, and says no when the answer is none of them.
Hanne Vestergaard
Client Relationships
The first voice on a new account and the last check before a proposal leaves the building.
Tomás Ferrer
Standards & Review
The second pair of eyes on every itinerary. Reads the trip brief before the crew does.
The demonstration atlas
See how it actually works.
Fictional company · Fictional team · No real aviation operation is described