Poker Chips

Oct 2026

A self-hosted web app that replaces physical poker chips for in-person Texas Hold'em, tracking stacks, bets, and pots from players' phones over a shared room code.

Why it exists

This came out of being the one person at the table who ends up doing chip math at 1am. One player hosts a room on their own machine, sets the blinds and stacks, and everyone else joins off their phones on the same network with a 6-digit code. From there the app takes over the parts that are tedious to do by hand: dealer button and blind rotation, turn order, side pots when more than one person is all-in, rebuys between hands. It stays out of everything else. It never sees a card, and at showdown someone just says who won, the same as at a real table. I didn't want to build a poker engine, I wanted to stop doing arithmetic.

How it's put together

Frontend's Vite/React, backend's a Python FastAPI service, and all room state just lives in memory on the host's process, with no database. You start it with ./run.sh, it comes up on port 8000, and everyone else joins over LAN, optionally behind a passphrase (defaults to "pokernight" if you forget to set one, which I usually do). The in-memory part isn't something I plan to fix. A restart wiping every game is fine for something that's supposed to disappear at the end of a game night, not outlive it.

What was actually hard

Not the UI: the pot math. Side pots when people bust at different depths, blind progression surviving a rebuy, making sure the server decides what's a legal action and the client can't just lie about it. That's what most of the test suite is actually aimed at, plus some rate limiting on the room endpoints I added after thinking about what a bored guest could do to a room code. The betting engine is done and tested at this point; what's left is licensing and some odds and ends I keep meaning to get to.

Open the app · Source and setup on GitHub