Run your own live tables
elite is a live-video game platform. Operators that already have tables, a studio and dealers can bring their own tables to elite: dealers deal as usual, round results reach the platform from the dealer tablet (or another result source), and the studio pushes its video to elite. The platform provides the game screens (desktop and mobile), betting and bet limits, settlement, the wallet, bet records and reports.
Who this section is for
Operations managers and studio technical staff (cameras, network, streaming). Engineers integrating the games into their own site should start with the Quick start; engineers building a round data source should read Data source interface (GFI).
How it works
Camera → streaming PC or encoder ──WHIP (desktop and mobile feeds)──→ elite ──WebRTC──→ players
Dealer tablet (+ card-reading shoe) ──rounds, cards, results──────→ elite ──→ bets, settlement, bet records- Video and round results travel separately: the platform never reads cards from the video; results always come from the result source.
- Besides the dealer tablet, the result source can be EWIN AI VISION, RoadMapServer or your own results system pushing over GFI; see Result sources.
- Whatever the result source, you push the video of your own tables yourself; see Pushing video.
Equipment
| Item | Used for | Notes |
|---|---|---|
| Camera | Filming the table and the dealer | Connected to the streaming PC or encoder |
| Streaming PC or hardware encoder | Pushing the picture to elite over WHIP | For example OBS Studio 30 or later (built-in WHIP output), or any hardware encoder that supports WHIP; each table has a desktop feed and a mobile feed |
| Tablet | Runs the dealer tablet app: starting rounds, next-card prompts, confirming results, voids and corrections | A web app you can install to the home screen; Android tablets, iPad, or Chrome/Edge on a computer. A 10-inch or larger screen, in landscape and on power, is recommended |
| Card-reading shoe (optional) | The reader at the shoe's exit sends each card as it is drawn | Keyboard mode (HID, USB or Bluetooth), or a serial reader on a computer; without a reader the dealer can enter each card on the tablet |
| Network | Streaming and tablet connections | A stable wired network or Wi‑Fi, with enough upload bandwidth for both feeds at once |
- In Texas Hold'em every card of every hand must be recorded, so a card-reading shoe is recommended; the tablet's Pick card is a fallback for when the reader fails.
- Voids and corrections need a supervisor PIN entered on the tablet (4–8 digits, set in the Console).
- With EWIN AI VISION, set up the cameras and recognition equipment as AI VISION instructs.
From table to live
- Create the table: in the Console go to Table → Table management → My tables → Add table, choose the game (baccarat, dragon tiger, Niu Niu or Texas Hold'em) and enter the table ID and names. The new table gets a desktop and a mobile stream name automatically, starts in Maintenance and is enabled in your lobby (subject to your plan's table limit).
- Choose the result source: pick one under Results source in the same form. For dealer-tablet tables, use the table's Tablet button to pair a tablet and PIN to set the supervisor PIN. See Result sources.
- Push the video: the table's Streaming button shows both push URLs and the push key; configure WHIP in OBS or your encoder. See Pushing video.
- Rehearse: while the table is in maintenance the dealer tablet can start, deal and confirm rounds as usual; the platform records the results and the roadmap but takes no bets. Check cards and results in Table → Round results or the Table workbench.
- Open the table: set bet-limit profiles and the betting time, then set the status to Open. See Going live and costs.
- Billing: on the paid plan every table offered to players has a table fee, plus a streaming fee for the video your players watch, both taken daily from your prepaid credit. See Costs.
Result sources by game
| Result source | Baccarat | Dragon tiger | Niu Niu | Texas Hold'em | Notes |
|---|---|---|---|---|---|
| Dealer tablet (card-reading shoe or manual entry) | ✓ | ✓ | ✓ | ✓ | Nothing to apply for; the only source for Texas Hold'em |
| EWIN AI VISION | ✓ | ✓ | — | — | Uses your own AI VISION account and API key |
| RoadMapServer | ✓ | — | — | — | Advanced feature; uses your own RoadMapServer merchant API key |
| elite API push (GFI) | ✓ | ✓ | ✓ | — | For studios with their own results system, pushing signed GFI events |
A table is linked to one result source at a time; you can change it later with Edit.
Who does what
| elite | You |
|---|---|
| Game screens (desktop and mobile), betting and bet limits, checking results against the cards, settlement | Tables, dealers, cameras and streaming |
| Delivering the video to players (WebRTC) and metering it | Running the result source (tablet, card reader) and the studio network |
| Transfer wallet, bet records, reports, tenant API and webhooks | Handling incidents at the table: voids and corrections (supervisor PIN) |
| Stopping bets when a result source goes down; voiding and refunding rounds that never get a result | Abnormal rounds on your own tables (the Console has buttons for them, and they close automatically if left alone; see abnormal rounds) |
Limits
- Up to 50 tables of your own per merchant.
- A table ID has 2–12 characters (letters, digits,
_and-, converted to upper case) and cannot be changed after creation; the ID of a removed table cannot be reused. - The full table ID is "company code-table ID", for example
ACME-B01; it is what game launch, bet records and the API use. - Your own tables are visible only to your players by default; you can also share them with other merchants, see Tables shared by other merchants.
Next
- Result sources: installing and pairing the dealer tablet, card readers, the supervisor PIN, voids and corrections; EWIN AI VISION, RoadMapServer and GFI pushes.
- Pushing video (WHIP / OBS): push URLs and the push key, OBS settings, suggested encoder settings, checking that the stream is live.
- Going live and costs: opening a table to players, table settings, maintenance, and worked examples for table and streaming fees.