Where your tickets live, and how to send one to a friend

The normal way people manage tickets is a search through their email at the door, with one bar of signal, while a queue builds behind them. It works until it does not.

One place, everything in it

Every ticket you hold sits in your account: upcoming first, past events kept as a record. Each one carries its live QR code, the venue, door times, and the organiser's terms for that specific event.

Transfer is a real operation

Send a ticket to someone and it moves. It becomes invalid in your account and valid in theirs, with their name against it. Nobody is holding a screenshot hoping it still works, and there is no ambiguity at the door about which of you is coming.

The ticket’s rotating secret is replaced as part of the same operation, so every code your phone can still compute stops working within thirty seconds. That is the part that makes a transfer real rather than a change of name: two working copies of one seat would be worse than no transfer at all.

It works without signal

The code your phone shows is computed on the phone, from a secret the ticket already holds — it is not fetched from a server at the moment the queue is longest and the network is worst. A ticket that needs connectivity to display is a ticket that fails in exactly the place it is needed: a basement venue with eight hundred phones competing for one cell. Apple and Google Wallet passes are not built; this is the ticket in your browser, installed as an app if you want it.

The messages that matter arrive

Confirmation, reminders, changes of time or venue, and cancellations are delivered rather than optional. Marketing you can turn off; a message telling you the venue has changed is not marketing, and it will reach you.