← All work
BUSINESS & VERTICAL SAASLIVEDoormanTickets and the door, offline too
Business & vertical SaaSLivedoorman.inkress.com ↗

Doorman

Event ticketing that sells the tickets and runs the door, and keeps checking guests in even when the venue has no signal.

17
architecture decision records written before the build
49
database tables behind sales, door and team
Ed25519
signatures on every ticket, checkable offline

The problem

Three things go wrong at an event door: more tickets get sold than there are places, one ticket (or a screenshot of it) gets used twice, and the phone at the gate loses signal and the line stops. Small organisers usually cover this with a spreadsheet and hope.

What it does

An organiser creates an event, sets ticket types and prices, and shares a link. Guests pay by card through Inkress, receive their ticket by email, and can pass it to someone else.

On the night, any staff phone becomes a scanner. Each scan gives a large, clear verdict, such as let in, already in, wrong gate or not valid, and the phone keeps the event's ticket list so a dead signal doesn't stop the line. Scans made offline are merged back once the phone reconnects.

Behind that sit a guest list with import and export, promo codes, a waitlist, team roles, an after-event recap and a feed of suspicious-activity flags. Doorman runs on its own address or inside the Inkress merchant dashboard.

Key features

  • No overselling

    Places are held while a buyer pays, so the last ticket can't be sold twice during a rush.

  • Tickets that verify offline

    Every ticket is cryptographically signed, so a scanner can check it without any internet connection.

  • One entry per ticket

    A ticket can only be used once, and if two offline phones both scan it, the earliest scan wins once they reconnect.

  • Screenshot-resistant codes

    Higher-value tickets can show a code that changes every 30 seconds, so a shared screenshot stops working.

  • Safe transfers

    Passing a ticket on cancels the old one, so the original holder can't still use it at the door.

  • Any phone is a scanner

    Staff phones are set up per event with a short code and a role, with a live view of who's in.

Where it stands

Live and early. Refunds through Inkress are built but switched off for now, and duplicate entry between two phones that are both offline is detected afterwards rather than prevented.

Under the hood: for the technically-minded

How it's built

Doorman is one server-rendered TypeScript app with PostgreSQL as the single source of truth and no in-memory locks, so any server can handle any request. The rules for money and admission live in plain domain modules kept apart from screens and API routes, so the web app, the service API and the scanner all follow the same rules.

Decisions were written down before they were built: 17 architecture decision records cover signed tickets, holds, redemption, offline sync, revocation, transfer and wallet passes. Payment and sign-in come from Inkress, while tickets, capacity and the door belong to Doorman's own data.

The interface is ink on white with a single typeface. Colour comes only from each event's own accent and from status, so every event looks like its organiser's, not like Doorman's.

The hard problems

  • Never oversell under a rush

    Capacity is claimed with a guarded database update that only succeeds while sold plus held plus requested fits, expired holds are reclaimed at the same moment, and row locks stop a place from being both reclaimed and sold.

  • Trusting a ticket with no network

    Each event has its own signing key pair, and scanners hold only the public half, so a stolen phone can't create tickets. Tickets are re-created from their serial rather than stored, so cancelling or transferring one just changes what that serial points to.

  • Two offline phones, one ticket

    Offline scans are replayed earliest first with a fixed tie-break, so the server and every gate agree on who got in. The short window where both phones are offline is detected and flagged rather than claimed to be prevented.

Built with

  • TypeScript
  • React Router 7
  • PostgreSQL (Drizzle)
  • Ed25519 signed tickets
  • Offline-first scanning

Building something in this space?

Work with us →