PPPokerBot — Operator Reference

A handbook for operators, club agents, and integrators working inside the PPPoker club ecosystem. Written like a manual, not a sales page.

PPPoker is the longest-running of the Asian-origin clubby poker apps (live since 2017, audience concentrated across China, Indonesia, Vietnam, the CIS, and parts of Latin America). Its product model — club agents act as cashiers, owners set rake and rakeback, and the platform takes a license fee per chip movement — is fundamentally different from a regulated public site like PokerStars or GGPoker.

That difference is the entire context for any conversation about bots, automation, or detection in this ecosystem. A bot inside a PPPoker club is not a market-level abuse problem the platform is incentivised to chase; it is an internal trust problem between the agent, the owner, and the regulars. This reference documents what is actually verifiable from the outside about how clubs are structured, what detection signals are real versus folklore, and which automation patterns survive the current rule set.

Scope. This site is operator-facing. We do not publish bot binaries, exploit recipes, or anything that would be illegal in the jurisdiction the reader is most likely in. We document mechanics that anyone running a club already knows about and outsiders frequently get wrong.

What is in this reference

1. Club architecture

Where the money sits, who has the rake-setting permission, how chips move between unions and clubs, and why the «no cash-out» line that PPPoker uses in every regulatory filing has a very specific legal meaning that is unrelated to player experience.

2. Bot detection layers

What signals PPPoker collects on the client, what gets escalated to a human review, and which detection claims you see on poker forums are real versus marketing noise from competing room operators. Order is roughly: device fingerprint → behaviour timing → opponent-history graph → human review.

What this reference is not

Not a directory of clubs, club codes, or union IDs. Those rotate constantly and any list is wrong within a week.
Not a tutorial on bypassing detection. The detection model is documented because operators need to know what their counterparties already see, not so a hobbyist can sidestep it on a Tuesday afternoon.
Not the official PPPoker Help Center. Refer to the platform for support, KYC, or commercial questions.

Who we are

A small operations team that has built, run, and audited automation across the major clubby apps since 2016. We work on the operator side: liquidity bots inside private clubs, detection consulting for room owners, and a custom-engineering practice for clubs whose volume justifies it. The public side is this reference and a Telegram contact channel.

If you are running a club and the topic of this site is part of your week, talk to us directly. We do not publish a price list, because the work is never the same twice.

Reading order. Start with Club architecture — most arguments about PPPoker bots collapse once you see how chips actually settle. Then Bot detection layers.