Skip to content
Meridian

Passenger portal demo

From connection to discovery, and to interaction if the passenger chooses.

This interactive prototype demonstrates route-resolved content, discovery, configuration and explicit consent. Flight context and performance data are seeded. Live flight-plan ingestion, campaign operations, persistence and partner routing remain to be validated in a pilot.

Interactive prototype · seeded data
01

Presence

A brand introduced because it belongs in the environment. Nothing to click, nothing asked.

02

Discovery

A collection, a story, a product to explore, made relevant by where the aircraft is going.

03

Interaction

Configure, view, reserve, access, read or arrange, when the passenger chooses.

04

Request

Where it adds value, a request sent with explicit consent. In a live deployment, an approved partner would receive it.

TEB→PBI
In flight0:38ETA 18:40
Automotive partner

The motor car, specified before you land

Have concierge arrange

Meridian

The Destination, In Reach.

You are flying TEB to PBI.

Connect for internet access and a short, curated view of Palm Beach.

No account, no email, no passenger details. Your details are shared only if you ask for something.

Operated by Your operatorPalm Beach · PBI

TEB → PBI · 2:38 · Starlink Aviation

Demo lane

Changing the lane re-resolves everything downstream — the destination editorial, the categories, the experience list, the featured brand and the arrival market. Nothing here is hardcoded to one route.

Screen

Flight context

Resolved pre-departure

Block

2:38

Aircraft

Ultra-long-range

Gulfstream G650ER

Passengers

4

Representative leg

Bundle

PB-WNTR-04

Palm Beach winter season

Showing Welcome aboard. Flight card, route, connectivity — and the lane selector.

What is real here

Real interaction, seeded data, one screen.

Every screen, transition and interaction works as specified. What is simulated is the flight context. In a live deployment it would come from the filed flight plan, assigned to the tail before departure.

Real

Screen flow, the presence and discovery screens, configurator state, consent gating, route-resolved content, the curation desk, offline-capable rendering.

Seeded

Flight context, aircraft assignment, engagement figures, lead counts and revenue. Four corridors instead of a live fleet.

Pilot will validate

Live flight-plan ingestion, campaign operations, persistence, and request routing to approved partners. Nothing in this prototype reaches a partner.

Small enough to control. Real enough to learn.

The prototype is the pitch. It runs offline, on a laptop, in a room, which is how these conversations actually happen. A pilot puts it on a defined aircraft group and measures what passengers do with it.