Online Poker Software Providers
Compare poker software providers by engine ownership, network and liquidity model, delivery route, licensing, player data, integrations and exit terms.
6 providers compared · Content updated · Provider eligibility reviewed . Commercial relationships do not affect editorial conclusions.
Online poker software is not one interchangeable product. A supplier may own the game engine and clients, operate a shared-liquidity network, connect an independent network to its software, or resell another provider's poker product inside a wider platform. This comparison records those roles separately. A reseller does not become the engine owner, and a software supplier does not become the licensed operator merely because its product is certified or its group holds a B2B license.
A provider qualifies only with a current poker product, a real company or clearly bounded brand, and a defined ownership, delivery, certification, regulated-use, or deployment boundary. Traffic totals, network rankings, project counts, launch times, prices, revenue shares, and performance outcomes are excluded unless the population, date, scope, and method are clear. Descriptions such as large or global are not comparable liquidity measurements.
The contract matters more than the label. Before choosing a standalone license, API, turnkey package, white label, or network skin, confirm the contracting entity, operator license, permitted markets, player-account and wallet owner, merchant of record, data-controller and processor roles, network admission rules, ring-fenced liquidity, fund reconciliation, fraud decisions, game and RNG certification, source-code rights, hosting, service levels, incident duties, and exit plan. None of those boundaries should be inferred from a feature list.
Select the poker engine and liquidity route together
Online poker depends on game integrity, player matching, cash and tournament controls, fraud operations, client software, and sufficient liquidity. The engine owner and network operator may not be the same contracting party.
Use when: The product needs a poker engine, client, tournaments, game integrity, and liquidity access.
Keep explicit: Engine ownership does not establish network control, player funds, licensing, or portable liquidity.
Use when: Compared with Online poker software, use this route when player accounts, wallet, bonuses, content connections, and casino operations must work as one stack.
Keep explicit: Keep this distinction from Online poker software: a casino platform is wider than content distribution but may still depend on a separate PAM.
Use when: Compared with Online poker software, use this route when one wallet and catalog integration should connect content from several studios.
Keep explicit: Keep this distinction from Online poker software: aggregation distributes games without becoming their owner or a complete casino platform.
Use when: Compared with Online poker software, use this route when the organization is mapping suppliers across several different regulatory control functions.
Keep explicit: Keep this distinction from Online poker software: identity, monitoring, player protection, testing, and advisory work are not interchangeable.
What this comparison covers
- • Current poker engines, clients, tournament systems, back offices, APIs, shared-liquidity networks, skins, and hosted or white-label poker products through the exact qualifying module
- • Owned, operated, connected, and resold poker products when the platform, network, game, license, player contract, wallet, and distribution roles remain explicit
- • Cash games, tournaments, and other poker formats only within the current product, build, network, and market scope
- • A consumer poker room or operator brand with no identifiable B2B software, network, hosting, or resale route
- • A broad casino platform, game aggregator, development company, or payment service that merely mentions poker without a current contractable poker module
- • Historical networks, discontinued products, affiliate poker tools, generic card games, or planned features with no current delivery or identifiable owner
What operators should compare
These are procurement dimensions, not assumptions that every field is known. A blank or unknown detail is not treated as a negative score.
Platform, network, and skin boundary
Engine and client owner, network operator, liquidity provider, skin or reseller, host, contracting entity, software and operating licensees, and current product status.
Games, tournaments, and liquidity
Formats, stakes, tables, schedules, tournament and prize rules, shared and ring-fenced pools, admission, segregation, fill and cancellation behavior, and operator concentration.
Accounts, wallets, and funds
Player contracting party, PAM, wallet and ledger, merchant of record, deposits and withdrawals, buy-ins, prizes, fees, reconciliation, customer-funds protection, and chargebacks.
Integrity and player protection
Identity and location checks, collusion and bot controls, fraud decisions, device and behavioral data, responsible-play tools, limits, exclusions, investigations, appeals, and incident escalation.
Build, integration, and data
Game and RNG version, certification, target markets, API or client delivery, SSO, wallet messages, hand and tournament history, reporting, controller roles, retention, monitoring, and recovery.
Network change and exit
Liquidity or network withdrawal, table and tournament closure, open play, balances and prizes, data exports, domain and client changes, transition support, credential revocation, and post-termination records.
Market snapshot
This snapshot summarizes the products that qualify each listing. Provider and role totals count companies; product type, ownership, availability, and delivery-model totals count the relevant products or recorded variants. One product can have several delivery models, so those counts can exceed the provider total. It does not count every product sold by a company and is not a market-share measure or ranking.
- Poker
- 6
- Technology owner
- 4
- Reseller
- 1
- Service provider
- 1
- First party
- 4
- Resold
- 1
- Undisclosed
- 1
- Standalone and bundled
- 5
- Bundle only
- 1
- Managed service
- 3
- Software license
- 3
- Turnkey
- 3
- API
- 2
- iFrame
- 1
- White label
- 1
Comparison at a glance
This table uses the qualifying product scope for this hub. Unknown means the field remains unresolved; it does not mean the provider lacks that option.
| Provider | Qualifying vertical product | Ownership | Availability | Delivery |
|---|---|---|---|---|
| BetConstruct |
| Resold | Bundle only | Unknown |
| Connective Games |
| First party | Standalone and bundled | Software license |
| Cubeia |
| First party | Standalone and bundled | Software license, iFrame, Managed service |
| EvenBet Gaming |
| First party | Standalone and bundled | Software license, API, Turnkey, Managed service |
| Playtech |
| First party | Standalone and bundled | Managed service, Turnkey |
| Stretch Network |
| Undisclosed | Standalone and bundled | White label, Turnkey, API |
Providers
RFP shortlist: 0 of 5
Select two to five providers to open a named proposal comparison. This is separate from the editorial pick.
BetConstruct
ResellerBetConstruct offers Poker inside its wider product and back-office environment, with Stretch Network as the upstream poker product. BetConstruct is a distribution and integration route rather than the owner of a separate poker engine or liquidity network.
Why listed here: BetConstruct currently distributes and integrates Stretch Network poker. BetConstruct is the reseller and integration route, not the poker engine or liquidity owner.
Relevant product
Stretch Network Poker via BetConstruct
- Type: Poker
- Ownership: Resold
- Availability: Bundle only
Connective Games
Technology ownerConnective Games develops its poker clients and game product in-house and can combine them with a wider operator platform covering accounts, responsible-gambling controls, CRM, promotions, payments, CMS, reporting, and third-party content connections.
Why listed here: Connective supplies first-party poker software and a separate operator platform, with a long-running Aconcagua deployment. Comparable current liquidity data is unavailable.
Relevant product
Connective Games Poker
- Type: Poker
- Ownership: First party
- Availability: Standalone and bundled
Cubeia
Technology ownerCubeia licenses a first-party real-money poker system with a game server, responsive HTML5 client, back office, bonus and engagement tools, single-wallet integration, iframe delivery, game history, and collusion and multi-accounting controls. The product can stand alone or sit inside the broader Cubeia Nano platform.
Why listed here: Cubeia supplies a first-party poker engine, client, back office, and wallet integration. Hybrid Poker Network is a separate shared-liquidity organization.
Relevant product
Cubeia Poker
- Type: Poker
- Ownership: First party
- Availability: Standalone and bundled
EvenBet Gaming
Technology ownerEvenBet supplies its own poker engine, game and tournament layer, browser and native clients, operator back office, account and engagement tools, reporting, anti-fraud functions, and integration interfaces. The current offer supports a standalone room, a broader turnkey stack, and poker added to an existing operator product.
Why listed here: EvenBet owns the poker product and holds a Malta B2B license covering peer-to-peer poker. Optional network operation is delivered by third parties; Enterra is brand history, not a separate provider.
Relevant product
EvenBet Poker Platform
- Type: Poker
- Ownership: First party
- Availability: Standalone and bundled
Playtech
Technology ownerPlaytech owns and operates iPoker as a B2B poker technology and network product. The current offer includes web, desktop, and mobile clients, cash games and tournaments, direct game launch, network management, operator promotion tools, player segmentation, and BI-connected engagement functions.
Why listed here: Playtech has a first-party poker network, an active Great Britain software license under the iPoker trading name, and a named regulated turnkey deployment that included poker.
Relevant product
Playtech iPoker
- Type: Poker
- Ownership: First party
- Availability: Standalone and bundled
Stretch Network
Stretch Network offers poker through white-label, turnkey, and API routes and operates a shared-liquidity product with tournaments and operator tools. Stretch is the upstream poker product used in the BetConstruct platform route.
Why listed here: Stretch has a current poker product, three delivery routes, and an active upstream integration with BetConstruct. Its legal company and IP owner remain unresolved.
Relevant product
Stretch Network Poker
- Type: Poker
- Ownership: Undisclosed
- Availability: Standalone and bundled
Providers are listed alphabetically; this page is not a ranking.
A company can appear in several comparisons when the same product fits more than one buying need. Distinct products are assessed separately.
Poker liquidity and integrity map
Map the network, funds, game-state, and integrity controls behind each poker offer.
Poker layer
Network and seating
Decision boundary
Name network owner, skins, shared liquidity, player pools, regions, table access, and migration rules.
Evidence to test
Production configuration shows which players can meet and under which operator terms.
Poker layer
Buy-in, pot, and rake
Decision boundary
Assign wallet transfer, table balance, pot calculation, side pots, rake, fees, and cashout.
Evidence to test
Hand history, table ledger, wallet postings, and operator reports reconcile by hand ID.
Poker layer
Integrity and player action
Decision boundary
Define bot, collusion, multi-account, device, seating, investigation, restriction, and appeal controls.
Evidence to test
A case retains signals, hands, analyst reasoning, decisions, confiscation, and communication.
Poker layer
Disconnect and exit
Decision boundary
Set reconnection, timeout, tournament interruption, balances, open games, history, and network departure.
Evidence to test
Failure and migration tests preserve funds, entries, results, and downloadable hand records.
Procurement checks
- • Map the engine, client, network, skin, host, licensed entities, player contract, PAM, wallet, funds, fraud, data, support, and incident responsibility chain.
- • Require dated, market-specific liquidity data by format, stake, room, and observation window, including shared and ring-fenced pools, fill and cancellation behavior, and operator concentration.
- • Test seating, buy-ins, gameplay, disconnect and resume, duplicate messages, cash tables, tournament registration and cancellation, prizes, wallet rollback, collusion and bot escalation, reporting, and recovery.
- • Contract for network and product withdrawal, final tables and tournaments, open games, balances and prizes, hand and audit exports, player notices, disputes, parallel migration, and post-termination access.
Limits of this comparison
- • Included providers have a current poker platform, network, hosted product, API, or resale module. Inclusion does not imply network liquidity, ranking, player totals, operator licensing, every game or market, integrity outcomes, performance, price, revenue share, launch timing, or continued availability.
Load this category's comparison fields, contract controls, and acceptance tests into a working decision record. You can also shortlist two to five providers above and carry their names into a side-by-side proposal evaluation.
Build the Online Poker Software Providers RFP