The Customer. An operator wanting an invite-only, club-based mobile poker experience on iOS and Android — private clubs, an agent hierarchy, and chip settlement between agents and players. The product needs to feel private and controlled, with membership rules the operator can enforce.
The Challenge. Club poker isn't just "poker with friends." It needs a membership and permission model, an agent and sub-agent hierarchy, and a settlement layer that tracks chips up and down that hierarchy correctly. Most teams would build this from scratch and rediscover every edge case River has already solved.
The invite-only model adds complexity: membership approval flows, club codes, access control at the game level. The agent hierarchy introduces a permission structure that has to compose cleanly with the existing admin system. And chip settlement across that hierarchy requires the same audit-grade ledger already running in production — not a new one.
The Solution. River extends the architecture already in production — the same server-authoritative engine and audited chip ledger — adding club membership, agent hierarchy, and settlement on top, rather than starting at zero. When you build with River, you're not betting on new, unaudited code. You're extending a proven system.
Under the Hood.
Results. Because the engine, shuffle, and ledger are already in production, the club layer is an extension rather than a rebuild. Architecture is in place, deliverable in weeks rather than quarters. When you build this with River, you launch on a proven foundation instead of betting on new, unaudited code.
"A direct extension of the architecture in production today — clubs, agents, and settlement on the engine that's already live."— River capability (club path)
River can deliver your club-based poker platform on a proven engine. Let's scope the build together.
Book a call →