Recording · IATA · May 11 CUSS 2 Business Informative Session Recorded Monday May 11, 2026 · IATA Common Use WG
Watch recording (IATA members) →
Microsoft Teams · IATA · Jun 1 CUSS 2 Technical Deep-Dive Monday June 1, 2026 · 15:00 CEST (09:00 ET)Read more →
Join Teams meeting →

CUSS 2 · THE NEW GLOBAL STANDARD

Every airline.
Every airport.The CUSS 2 migration is here.

CUSS 1.x was retired December 31, 2025. The IATA RP 1706c standard now defines how airline applications run on shared airport self-service kiosks worldwide — and every carrier still on CUSS 1, every airport vendor still on legacy platforms, has to migrate. We help both sides do it without breaking each other's timelines.

Want to hear it straight from IATA? Join the CUSS 2 Technical Deep-Dive on Monday June 1 — Teams details in the meeting card above.

See our offers → FAQ →

Why this matters now

The soft transition is here.
The cutover is coming.

IATA's CUSS 2.0 specification (RP 1706c) is now the global standard for airport self-service. We're in the soft-transition phase — vendor-by-vendor CUSS 2 mandates are already starting; full cutover and the formal sunset of CUSS 1.x come next. Every airport and every airline still on CUSS 1.x has to migrate. See the FAQ for timeline, hardware, and migration specifics.

01

Born Digital

OpenAPI and WebSockets replace CORBA/IDL. Standard web tooling, true cross-platform compatibility, no proprietary middleware.

02

Zero-Trust Security

Mandatory TLS 1.2+ encryption and OAuth 2.0 authentication baked into the protocol itself. No more perimeter-trust assumptions.

03

Rapid Deployment

Hardware decoupled from software. Web-first apps cut integration overhead ~40% and ship the same day they're written.

How we help

Four paths to CUSS 2 — without waiting on anyone.

Migration delay is almost always a lockstep problem — airlines waiting for airport platforms, airports waiting for airline apps. Each path below breaks that dependency in one direction. Two for airlines, two for airports, and all of them deliver in a fraction of the typical industry timeline.

For Airlines

BUILD WITH OUR SDKS

Build your own CUSS 2 app — and ship now.

Use our open TypeScript, Angular, and React SDKs to build a CUSS 2-native application from scratch — or convert an existing CUSS 1 app in place. The included bridge layer lets the modern app run on both CUSS 2 and CUSS 1 platforms during the transition, so you ship without waiting for every airport to certify CUSS 2.

  • Open SDKs in TypeScript, Angular, and React at cuss2.dev
  • Bridge layer for backward compatibility with CUSS 1 platforms
  • New build or in-place CUSS 1 → CUSS 2 conversion
Talk to us →

WHITE-LABEL · WE BUILD IT FOR YOU

Or have us build it — fully branded to your carrier.

We build complete CUSS 2 applications as white-label — hyper-branded to your carrier identity, with a full-service architecture underneath. Low and mid-service apps ship in weeks. Full-service experiences with every feature turned on take longer, but still well under the 9–12 months typical of DIY or competing vendor builds.

  • Fully branded as your carrier — we stay invisible
  • Low/mid-service apps: weeks. Full-service: months.
  • Months, not 9–12 months — faster than DIY or competing vendors
Talk to us →

For Airports

KEEP YOUR PLATFORM

Add CUSS 2 to your existing platform.

Deploy our bridge layer on top of your current CUSS 1 platform — regardless of which vendor it's from. CUSS 1 airlines keep running unchanged; CUSS 2 airlines now have a compliant target on the same kiosks. No platform migration, no vendor swap, no disruption to existing tenants.

  • Compatible with any RP 1706b-compliant CUSS 1 platform
  • Hardware-agnostic deployment
  • Zero disruption to existing airline tenants
Talk to us →

REPLACE YOUR PLATFORM

CUSS 2 platform on your hardware.

Our full CUSS 2 platform runs on any vendor's kiosk hardware and serves both CUSS 1 and CUSS 2 airlines side-by-side. Existing tenants don't need to migrate on your timeline — you upgrade the platform, they upgrade their apps when each is ready.

  • Runs on any vendor's kiosk hardware
  • Serves CUSS 1 and CUSS 2 airlines simultaneously
  • No platform fee for early airport partners
Join the platform waitlist →

Join the waitlist

Tell us which offer fits.

We'll be in touch within 48 hours.

01 Which offer fits?
02 Who are you?
03 Context (optional)

0 / 1000

By submitting, you agree to be contacted by Elevation AI about CUSS 2. We won't share your information. Protected by reCAPTCHA — Privacy & Terms.

Resources

Everything else worth reading.

IATA Common Use Program

Official IATA program page for Common Use Self-Service — RP 1706c specification, certified vendors, and the CUSS 2.0 transition guidance.

iata.org/programs/common-use →

ACI World Advisory

Operational guidance for airports transitioning to web-native CUSS 2.0 environments.

aci.aero →

cuss2.dev

TypeScript / Angular / React SDKs, live sandbox, and the full RP 1706c migration guide.

cuss2.dev →

Developer Discord

Real-time technical support from the Elevation team and the broader CUSS 2 developer community.

discord.gg →