Who we are
PokerNet was founded in 2024 by a team with 5+ years of combined experience in private-club operations and infrastructure engineering. Our operators came from inside the ecosystem — running clubs across PPPoker, PokerBros, Suprema, ClubGG, X-Poker and HHPoker environments — before we rebuilt the internal tooling as a managed service and opened it publicly in 2026.
We work as a distributed team. The combined background is club operations on one side (agent management, off-peak coverage, manager workflows, retention design) and infrastructure engineering on the other (uptime, telemetry, ecosystem-neutral configuration, platform-specific deployment playbooks). The two halves are deliberately separated: operations decisions belong to the club owner, infrastructure execution belongs to us.
Why we don't publish full names
Anonymity is the norm in private-club infrastructure, and it's a deliberate choice — not a hedge. Operators who work inside this ecosystem don't put their faces on landing pages, and the reasons are practical: platform policies, agent relationships, jurisdictional considerations. We've chosen to operate the same way our partners do. What we publish instead is operator-grade work: technical playbooks, operational comparisons, case studies. A reader who has run a club knows which articles on this site could only have been written from inside the system.
That's also why our articles are bylined under a stable operator name rather than a full legal one. The work on this site is written and reviewed by a real operator we credit as Andrew M. — the pseudonym keeps the identity protected for the reasons above, while still attaching each piece to a single accountable person rather than a faceless brand.
About the author — Andrew M.
How we think about the work
Ecosystem-neutral by default
Aggressive bot deployment kills clubs. Default configurations are calibrated to be ecosystem-neutral or slightly negative — meaning the AI segment loses small amounts to the player pool over long stretches. The economic model is rake recovery and retention, not edge extraction. Owners who run aggressive configurations see strong Q1 numbers and Q2-Q3 collapse. We don't run those configurations.
Operations is the hard part, not the technology
The technology of managed bots is well-understood. The hard part is the operations layer: when do tables get reinforced, when do they not, how do bot profiles match real player density, how does the schedule adapt when a regular goes off the rails or a union changes rake caps. That layer is where we earn revenue share — and where DIY scripts and unmanaged tools fail at scale.
Revenue share, no upfront cost
We charge revenue share, calibrated per club, with no upfront license fees and no per-bot pricing. The model exists because we believe the deployment should pay for itself or it shouldn't run. If a club generates rake lift that exceeds our cut with room to spare, the math works. If it doesn't, we both need to know that within the pilot window — and the model gives both sides honest feedback fast.
Platforms we work with
We deploy on the platform your club already runs — there's no migration step. The infrastructure is vendor-neutral, but operational playbooks are platform-specific: PPPoker, PokerBros, ClubGG, Suprema, X-Poker, and HHPoker all have separate deployment configurations, separate detection-avoidance considerations, and separate format-traffic patterns we calibrate against.
Where to next
If you're a club owner or partner operator weighing this against DIY scripts, read the operational comparison: Managed poker bots vs DIY scripts. If you're evaluating which platform fits your member base, see PPPoker vs PokerBros vs ClubGG operational tradeoffs. If you want to talk specifics about your club, the form is on the home page or you can message us on Telegram.