Pre-launch

A layover is inventory that expires unsold.

Hundreds of millions of hours a year are spent in transit halls by people who had somewhere they could have been. The hours are not missing — they are unpriced. We compute how many of them are genuinely usable, and when the traveller has to be walking back.

What we will not do

Three rules the rest of this rests on.

No commission on a ticket

We take nothing from an airline ticket, and it is a rule rather than a stage we intend to grow out of. It is what makes the recommendation worth having: the answer cannot move with where somebody books.

The pass is never for sale

Status is earned by travelling and never bought, and the credential is funded by the operator.

An unmeasured number says so

Every figure carries which era it belongs to and how well it is known. A total missing one of its inputs is not a smaller total — it renders as absent, with the reason attached, rather than as a confident zero.

For airports, airlines and venues

Four people stand around the same layover.

Hours for the passenger. A filled stopover. Landside dwell. A provable redemption. One computation.

Layover GDP mark

Airport operator

Layover GDP

Dwell that leaves safely beats dwell that paces the gate.

  • Funnel by hub
  • Sourced figures
  • Tenant scoped
Verified Hub Program mark

Standard

Verified Hub Program

What a hub certifies, and where it stands.

  • Engine-enforced tiers
  • Assessment, not brochure
  • Atlanta first
StayShare mark

Venue and merchant

StayShare

Settles what actually happened at your counter.

  • One-tap redemption
  • Exportable statements
  • Designed dispute path
Roll Pass ops and the API mark

Airline and developer

Roll Pass ops and the API

Fund the credential, or read it from the endpoints.

  • Carrier funded
  • Eligibility endpoints
  • Attribution on handoff

No live redemptions yet. Traffic starts with Atlanta. The consoles open with it.

Apply to partner

How we vet

No stage advances because a week passed.

An application starts at applied. Every stage after it is reached by filing evidence, and by nothing else — not by time, not by a status anybody sets, not by chasing us. The table is the one in our own code, so what it says we will ask for is what the pipeline will actually ask for.

What each kind of partner files, at each stage, before it is reached
Who you areverifiedsignedprovisionedlive
A venueA cafe, bar, restaurant or shop that can serve a passenger on a layover.
  • Business registration
  • Site visit
  • Agreement signed
  • Venue linked
  • Staff invited
  • First redemption tested
A hotelDay rooms and short stays for passengers between flights.
  • Business registration
  • Room inventory
  • Agreement signed
  • Venue linked
  • Rate plan loaded
  • First redemption tested
A city or tourism boardFunding visits and promoting what a layover can reach.
  • Authority confirmation
  • Agreement signed
  • Hub linked
  • Campaign live
An airlineFunding passes for your own passengers at a hub you operate.
  • Authority confirmation
  • Programme terms
  • Agreement signed
  • Hub linked
  • Eligibility configured
  • First pass issued
A platform or developerIntegrating the API rather than trading through us.
  • Contact verified
  • Terms accepted
  • Api key issued
  • First call made

Signing runs against an in-product redline today; the countersignature vendor is not chosen yet, so that rung is the one we move by hand. Everything either side of it is evidence-driven and append-only — nothing on an application is ever edited, and who filed what is taken from their session rather than typed.