About
Running one game is a timer and a bit of arithmetic. Running a league is a season of them, and the work is in what happens between the nights.
Most home leagues run on four things at once: a timer app on somebody’s phone, a spreadsheet nobody else can edit, a group chat where the schedule lives, and one person’s memory of who won in March. Each of those works. Together they leak. The standings are a week out of date, the seat draw is on a napkin, and the person who keeps it all is also trying to play.
PokerLeagueOS exists because those four things are one thing. The clock, the seating, the buy-ins, the payouts and the standings are all views of the same tournament, so recording a knockout at the table is what moves the season table. Nothing gets re-keyed afterwards, because there is no afterwards.
The second thing it assumes is that the players want in. A league is a social object, and the standings are the reason people show up in week nine. So every player gets the same live view the host has: their seat, the clock, where they stand tonight, and where they stand in the season. They scan a code on the TV. There is nothing to install and no account to make.
The third assumption is newer. The host should be able to play. Every action in the product is an HTTP endpoint with a specification an assistant can read, so the clock and the paperwork can be handed off to software while you sit down at the table. That is not a bolt-on: the web app is one client of that API, not a layer above it.
It is built and run by one person, which shows up in the parts you would want it to. There is no third-party analytics and no error-reporting service, because adding one would mean shipping your league’s data to a company you did not choose. Diagnostics stay in the same database as everything else and are deleted on a rolling basis.
If something is wrong or missing, support@pokerleagueos.com reaches a person.