Poker bot software

Poker bot software is a category of computer programs that automate decision-making and execution at online poker tables. The category divides into client-side agents that operate within a player's account, server-side decision engines that produce recommendations consumed by separate execution layers, and hybrid systems that split policy and execution across processes.

Definition

Poker bot software refers to programs that select and place actions at a hand of online poker without per-decision human input. A canonical implementation combines a perception layer that reads table state, a policy layer that maps state to action distributions, and an execution layer that submits the chosen action through the host client or a network interface. The category is distinct from real-time advisors and post-session analyzers, which produce recommendations for a human operator rather than acting autonomously.

Scope and boundaries

The category covers software that closes the decision loop end-to-end at the table. Programs that stop short of execution, such as solvers, range explorers, and replay analyzers, fall outside the strict definition and are treated as adjacent tools. Auxiliary modules that ship with bot suites — bankroll routers, multi-account orchestration, and seat selectors — are considered part of the category when packaged as a single product, and as integration components when sold separately. Software that automates the game lobby but not the table itself, such as queue managers, is excluded.

Principal vendor archetypes

Vendors in the poker bot software market generally cluster into three archetypes. These archetypes are presented without attribution to specific brands; the labels describe roles rather than companies.

Procurement patterns differ across archetypes. Operator-type vendors typically charge by seat-hour or by share of profit and retain ownership of the underlying model. Platform-type vendors license the engine for a fixed fee or per-call basis and leave execution to the buyer. Integrator-type relationships are project-based and produce code and operational runbooks owned by the buyer at delivery.

Integration architectures

Integration of poker bot software into operator infrastructure typically requires three components: a seat-allocation service that decides which account plays where, a kill-switch with a sub-second response budget, and a settlement layer that reconciles the bot's chip movements with the agent network. The decision engine itself is treated as a replaceable backend so that operators can change vendors without rebuilding the agent fleet.

Two architectural patterns dominate. In the thick-client pattern, the decision engine runs on the same host as the poker client and reads state through the operating system; deployment is per-machine and the kill-switch is local. In the split-policy pattern, the engine runs on a central server and exchanges state and action messages with thin clients over an internal network; deployment scales with hardware at the center and the kill-switch is enforced at the message bus.

Operator-side considerations

Operators evaluating poker bot software typically assess four properties before procurement. Profile diversity describes the engine's ability to vary its action distributions across accounts so that play styles do not collapse to a single fingerprint. Per-opponent adjustment describes whether the engine modulates aggression against weaker and stronger seat neighbors. Stability under network loss describes the timeout and reconnection behavior, since dropped hands carry both a financial and a detection cost. Audit surface describes the engine's logging policy, since downstream reconciliation depends on a recoverable trace of decisions.

Operators procuring through an integrator also assess the handover package: source rights, deployment scripts, monitoring dashboards, and a runbook covering routine maintenance and emergency shutdown. A complete handover reduces the operator's dependence on the integrator after delivery and lowers the cost of a future vendor change.

Related categories

Adjacent software categories include game-theoretic solvers, which compute equilibrium strategies offline; table analytics overlays, which present aggregated opponent statistics to a human player; and seat-allocation services, which schedule accounts across rooms without making in-hand decisions. These categories share components with poker bot software but do not close the decision loop and are therefore treated separately in this reference.

This page is a reference overview. Vendor archetypes are presented as roles rather than named companies, and integration patterns are described at the architectural level. Implementation details vary by operator constraint and applicable jurisdiction.