Identity for the events industry

One sign-in for everyone at your event

Exhibitors, their staff and your visitors sign in once with EventID. Every supplier system and event app you connect knows who they are, which company they're with and which event they're at.

  • Hosted in Sydney
  • Passkeys and email codes
  • Standard OpenID Connect

The problem

Every event rebuilds the same guest list, in every system

An exhibitor's team needs logins for the stand builder, the catering portal, the lead scanner and the exhibitor manual. Each supplier keeps its own copy of who works where, and nobody removes the person who left last month. Visitors juggle yet another account for the event app.

Today

  • A separate account per supplier, per event
  • Spreadsheets of exhibitor staff emailed between systems
  • Access lingers after people change jobs
  • Suppliers can't tell which company or stand someone belongs to

With EventID

  • One reusable identity across every connected system
  • The organiser vouches for exhibitors; companies invite their own staff
  • Remove someone once and their access ends everywhere
  • Every sign-in carries the right company, event and role

How it works

Live in three steps

  1. 01

    Import your event

    Upload exhibitors and registrations by CSV. EventID creates the event, the companies and their stand allocations. EventsAir import is next on our roadmap.

  2. 02

    Exhibitors bring their teams

    Each exhibitor's admin claims their company and invites colleagues. Visitors link their ticket from their confirmation email.

  3. 03

    Suppliers recognise them

    Connected supplier systems and event apps add "Sign in with EventID" and receive the person, their company and their event, with consent.

Security and privacy

Identity infrastructure you can put in front of exhibitors

EventID is the data controller for the identities it holds, and is designed around the Australian Privacy Principles from day one.

How we handle data →
  • Data residency

    Everything is stored in AWS Sydney. Backups stay in Australia.

  • Strong sign-in

    Passkeys, email one-time codes and authenticator-app MFA. Breached passwords are refused.

  • Consent per app

    People approve each service and can revoke it. Each app gets its own identifier, so apps can't link people across services.

  • Audit trail

    Sign-ins, membership changes and data access go to a tamper-evident, append-only log.

For developers

It's just OpenID Connect

If your platform supports "Sign in with" an OIDC provider, it supports EventID. Authorization code with PKCE and standard discovery, then one API call tells you the person's company, event and what they may do in your app.

Developer overview
GET /v1/me/entitlements
{
  "subject": "rp_7f3k…",
  "organisations": [{
    "legal_name": "Acme Displays Pty Ltd",
    "role": "admin",
    "events": [{
      "name": "Melbourne Build Expo 2027",
      "participation": "exhibitor",
      "stands": ["C12"],
      "permissions": ["supplier:order"]
    }]
  }]
}

Running an event next season?

We're onboarding a small number of organisers and suppliers for our pilot. Tell us about your event and the systems your exhibitors use.