← All insights
Air Mobility·Jul 12, 2026·10 min

Digital Vertiports: Why Physical Air Infrastructure Fails Without Centralized Digital Real Estate

Concrete pads and charging rigs are the easy part of Advanced Air Mobility. The hard part is the unified digital namespace that handles routing, ticketing and data handoffs across operators, airports and cities.

Every Advanced Air Mobility roadmap published in the last three years contains the same blind spot. There is enormous detail on aircraft certification, vertiport siting, energy provisioning and airspace integration — and almost nothing on how a passenger finds, books, pays for, and connects an aerial leg to the rest of a journey.

That missing layer is not a feature. It is the commercial interface of the entire industry, and it is being left to whoever claims it first.

The handoff problem nobody owns

A single eVTOL trip crosses more institutional boundaries than a long-haul flight. Consider a Heathrow-to-Canary Wharf hop:

• The airline owns the inbound passenger record.

• The vertiport operator owns the slot and ground handling.

• The aircraft operator owns the aircraft, crew and dispatch.

• The air navigation service provider owns the corridor authorisation.

• A ground mobility provider owns the final two kilometres.

Five parties, five systems, one passenger who simply wants a seat at 14:40. Absent a neutral layer, each pair of parties builds a bespoke integration, and the passenger experience degrades to whichever partner has the worst API.

What a digital vertiport layer must handle

• Identity and passenger record continuity across airline, operator and ground legs.

• Slot-aware inventory: aerial capacity is time-boxed and weather-sensitive, so inventory is closer to airline yield management than ride-hail matching.

• Ticketing and settlement: a single payment instrument that splits across multiple operators, with clean reconciliation.

• Disruption logic: weather cancellation must fall back to ground transport automatically, or trust collapses on the first bad day.

• Regulatory data handoffs: manifest, weight and balance, and corridor telemetry moving between parties without manual re-entry.

Why namespace, not just software

Neutral layers only work if all parties accept them as neutral. An operator-owned booking platform will not be adopted by competing operators. A city-owned one moves at municipal speed. The credible position is an independent layer with a name that is obviously about the category rather than about any single participant.

This is why we hold evtol.sydney, evtol.london and evtol.osaka as a coordinated set. Each is the exact-match category namespace for a metro that has committed real public and private capital to AAM. The same architecture, localised per market, with the search intent already pointed at the front door.

The asset case

For an airline, a vertiport consortium, or a municipal infrastructure group, acquiring the category namespace in a target city is a defensive move as much as an offensive one. There is exactly one evtol.london. Whoever holds it either becomes the front door or forces everyone else to buy their way past it.

We are building the booking and routing framework behind these names now. Acquisition and partnership conversations are open — andrew.mc@nousdomains.com.

Sources & references

Primary material, official filings, and operator publications referenced while researching this article.

Strategic Asset

robotaxi.tokyo is open for acquisition or seed partnership.

The canonical URL for Tokyo's autonomous mobility layer. Talk to us before a competitor does.

Initiate inquiry →