The Operating System for Physical Space

A futuristic, minimalist room with a large circular doorway and bright light shining through, with white tiled walls and floor.

Starting with tourism. Built for cities.

LoopPass is a cross-border visitor identity and interoperability protocol that lets one profile authenticate across hotels, mobility, destinations, and city services - without replacing existing systems.

A minimalist wall light fixture with four white 3D icons connected to a central glowing sphere: a rectangle, a bus, a house, and a ring, all mounted on a gray wall.

Physical Space Has No OS

Every physical environment runs on its own closed system

  • hotels operate isolated PMS and loyalty identities

  • mobility providers use separate ticketing and access

  • destinations issue their own passes and platforms

  • buildings rely on proprietary access control

  • smart-city pilots rarely interoperate

Digital space has iOS.

Cloud has AWS.

EVs have Tesla OS.

Physical space still has nothing.

A 3D rendering of a geometric pattern made of white square tiles arranged in a staggered, layered pattern.

LoopPass

One Identity, Many Systems

LoopPass is the identity and interoperability protocol for the real world.

A visitor creates a single profile that can be recognized across hotels, mobility, destinations, venues, and - over time - city services.

Three core layers

  • Reusable visitor profile recognized by

    • hotels & resorts

    • tourism boards & DMOs

    • mobility and transit

    • event venues and attractions

    • buildings & access systems

  • Privacy-first framework aligned with Swiss + EU norms

    • granular consent

    • data minimization

    • auditable flows

  • Connects existing systems without replacements

    • PMS

    • ticketing & pass platforms

    • mobility systems

    • access control & loyalty

    LoopPass is not another app, marketplace, or booking platform.

    It is the OS layer beneath everything.

Why This Layer Is Needed Now

Global shifts converging

Intermodal travel requires shared identity

Smart cities fail due to lack of coordination

Cross-border identity is missing in Europe

Operators want sovereignty - not Big Tech platforms

LoopPass is the missing backbone

A neutral identity + consent layer across regions and providers.

A Multi-Billion Infrastructure Opportunity

We are not claiming the value of tourism, mobility, real estate, or smart cities.

We focus on the identity + interoperability layer:

  • infrastructure licensing for destinations & cities

  • SaaS fees for operators (hotels, mobility, venues)

  • optional transaction fees on coordinated services

If LoopPass becomes a de-facto protocol in select destinations and cities,

the realistic revenue range is €1–10B annually.

Operators connect. Visitors reuse.

Hotels, DMOs, and mobility providers integrate via connectors

Visitors

create one profile

authenticate across systems

Operators

reduce onboarding friction

access consent-aware data

partner without heavy integrations

Destinations

gain coordinated insight without centralizing systems

Roadmap

Validated in Sequence, Deployed in Parallel

2025–2026 — Switzerland (Technical Validation)

Innosuisse-backed feasibility with HSLU

Identity + consent framework

Pilot scoping with tourism & mobility operators

2026–2027 — France (Cross-Border Validation, in Parallel)

France entity

Riviera pass + regional data partnerships

One identity across the Alps ↔ Riviera corridor

2027–2028 — Smart Destinations (EU + Middle East)

EU smart-destination deployment

Gulf smart-city partner

Expansion into buildings, events, mobility hubs

2029+ — City-Scale OS

LoopPass adopted as default interoperability layer

Protocol formalized as open standard

We validate in sequence.

We deploy in parallel.

 Why Big Tech Won’t Own This Layer

  • LoopPass sits at the institutional layer.

    Big Tech sits at the consumer layer.

  • Cities and tourism boards do NOT want identity data on U.S. clouds.

  • LoopPass is a protocol anyone can join.

  • Governments and operators don’t buy after-the-fact tech.

    They co-create the rules they adopt.

We are in the early-stage infrastructure phase, co-developing LoopPass with real institutions.

Architecture

Identity + consent framework with HSLU

Interoperability model for existing systems

Development (High-Level Only)

Core API concepts defined

Connector design patterns mapped for key system categories

Pilots

Switzerland - feasibility into pilot

France - corridor exploration with regional actors

Why SWIXS Is Positioned to Build This

Institutional co-development

We build with public and regional partners from day one - not as a vendor, but as a backbone.

Swiss neutrality

A trusted position for identity infrastructure across Europe and the Middle East.

Origin in real-world coordination

We come from solving complex multi-stakeholder coordination challenges - not from a slide deck.

From Airports to Destinations to Cities

SWIXS emerged from work in one of Europe’s most complex physical environments: a major international airport. Coordinating multiple ecosystem actors revealed a deeper insight.

Physical systems fail at coordination because they lack a shared identity and interoperability layer.

That insight now drives LoopPass across

  • tourism

  • mobility

  • buildings

  • smart destinations

Public partners reduce technical risk.

Private capital scales deployment.

  • Swiss federal innovation (Innosuisse)

  • Research institutions (HSLU, BFH)

  • Regional tourism & mobility agencies

Partner with LoopPass

We welcome structured discussions with

  • destinations & tourism boards

  • mobility operators

  • smart-city teams

  • government innovation bodies

  • infrastructure-aligned investors