Features
Six things have to work for a poker league to run itself: the clock, the room, the money, the season, the players and the plumbing. Here is what each one does.
The clock
The clock is the part of the night everyone is watching, so it is the part that cannot be approximately right.
Remaining time is computed from a single stamp on the server. A phone that slept through a level catches up the moment it wakes, instead of running its own count.
Open the display on a TV, a laptop or a tablet. Share the link and every player has the same clock in their pocket.
Scheduled breaks pause the timer. Hand-for-hand near the bubble freezes it on every screen at once, and unfreezes them together.
Level changes, the last minute of a level and the end of a break are announced out loud, so the room hears it over the table talk.
The room
Multi-table tools appear when the tournament is actually multi-table, and stay out of the way when it is one table of eight.
Seats are drawn at check-in. Late registrations take an open seat rather than a queue position.
When tables drift apart, the suggested move names the player and the seat. Accept it and the affected phones update.
When a table gets short, break it and the remaining players are redistributed to open seats.
A check-in screen built for the person at the door: search a name, take the buy-in, hand out the seat.
The money
Three different shapes of payout structure, and the deal maths that follows from whichever one you used.
Pay a ladder of percentages, promise fixed dollars regardless of turnout, or use a schedule that resolves by however many people actually paid.
Recorded as they happen, by the host or by the player from their own phone. The prize pool follows.
When the last players want a deal, both numbers come from the same prize list, with the places already won taken out.
Payout sheet and seating chart print on paper, for rooms that still want paper.
The season
Points, schedule and history are what separate a league from a series of unrelated nights.
Pick a points chart or write your own. Best-of-N drops a player's worst nights so missing one game does not end their season.
Standings move on every bust while the tournament is running. They are provisional by design and never written down until a result is saved.
Publish the calendar once. Players opt in or out from their phone and you see the count before you set the tables.
Finishes, ROI, in-the-money rate, head to head, and which venue a player does best at.
The players
Players scan the code on the TV. Nothing to download, nothing to sign up for.
Table and seat, updated through every rebalance and table break.
A 4-digit PIN lets a player report their own rebuy or add-on. PINs are casual identification and are documented as such, not a security mechanism.
Place in the tournament, chips against the average, and their live position in the season.
Every finish they have had in your league, and how they compare with the people they play against.
The plumbing
The parts that stop game night being a data-entry exercise.
Blind schedules, chip sets, payout schedules and point charts are saved once and referenced by every tournament that uses them.
Send another host a short code and they can import your structure into their own league.
Every organizer action is an HTTP endpoint, described by an OpenAPI 3.1 document, with API keys that are org-scoped and role-bounded.
Export at any time. Deleting an organization removes every row that belongs to it.