Ledger-based accounting, two-layer audit automation, screenshot capture, float management, drawdown analytics, action swaps. Or, for stables that already manage operations elsewhere, just the clean monthly report. Built from the inside, by an ex-stable CFO who knows what breaks. New to the topic? How poker staking actually works →
Pick the parts that fit. The full suite runs the stable end-to-end; the lighter version is just clean monthly reporting on a roster you already manage somewhere else.
Every transaction, chop, expense, deposit, cashout, and markup adjustment lives in an append-only ledger. Per-player balances reconcile from the ledger, not from a spreadsheet that drifts. Open balance, profit chop, deposit record, makeup — all tracked as discrete entry types with their own audit rules.
Sensitive entries (transfers, personal expenses, loan issues, profit chops) require two distinct non-creator signatures before they hit balances. Open requests → Layer 1 audit → Layer 2 finalisation → settled. The audit queue is the daily operating loop for the stable manager. Zero manual reconciliation; every balance change has two independent signatures behind it.
Bankroll screenshots, bank statements, on-chain transactions, SharkScope CSVs — uploaded against any audit request as third-party source-of-truth proof. Tied to the ledger entry that needs them, retained, soft-deletable. Built specifically because stables get burned when player-reported balances drift from reality.
Capital allocation across the roster, per-player makeup tracking, dynamic markup on deals, swap-pool participation. Models the stable as a portfolio: who has float, who needs more, who is in makeup, who is closest to a profit chop.
Per-player drawdown curves, aggregate stable drawdown, tail-risk distributions on the current roster. Built on the same Monte Carlo engine the individual MOTA tier uses, but at portfolio level — so you see correlated drawdowns, not isolated player risk.
Pooled action across the roster with provably-fair settlement (Shapley-value math: every contributor gets paid in proportion to the realised outcome they actually shaped). Swap percentages can be dynamic per-event, pool composition can change as players join or leave, and partial bullets, re-entries, and chops settle in closed form.
For stables that just want the report and don't need the operational layer: monthly P&L attribution per player, stable-wide ROI, capital efficiency, and an audit trail that holds up in front of an investor or a tax authority. Same data, lighter touch.
Sensitive ledger entries — transfers, personal expenses, loan issues, profit chops — never post to a balance on the creator's signature alone. They sit in an audit queue, visible to the whole stable management group, until two distinct non-creator signatures clear them. Source-truth uploads (bankroll screenshots, bank statements, on-chain tx hashes, SharkScope CSVs) attach to the entry as evidence. The full settlement history is replayable from the ledger; nothing is ever silently mutated.
Layer-2 verification is on the roadmap as an automated check — for now it's manual, which is fine for stables with a small management group, and explicit, which is the point.
Player or manager files an entry: deposit, cashout, transfer, profit chop, expense. Source-truth uploads attached.
First non-creator manager reviews and signs. The entry moves to "to finalise"; balances haven't changed yet.
Second non-creator manager signs. Balances post. Audit log records both signatures, both timestamps, and the source-truth attachments forever.
The Stable tier is priced against the actual roster size, ledger volume, and the parts of the stack you want active. Some stables run the whole operational layer; some just want the monthly group report. We talk through it on a first call and quote against the real scope, not a pre-set tier.
Risikohinweis: Poker ist Glücksspiel. Vergangene Ergebnisse sind keine Garantie für zukünftige Gewinne.