XGENIA RGS
Remote gaming server.
A remote gaming server (RGS) runs game maths, processes rounds and connects the game to your operator wallet. XGENIA RGS adds replayable results, market controls and signed lab evidence.
XGENIA RGS
Play money on every plan. Real money for crypto casinos: 5% of GGR on Indie, 2% on Team and Partner, and by contract on Enterprise. No setup fee.
How a round works. One round. Nothing lost.
- 1. The player presses spin. The game sends the bet to the RGS. A retried request returns the same round, never a second bet.
- 2. The market's rules are checked. Stake cap, round pacing and the player's limits, at bet time, before any money moves.
- 3. The casino's wallet is debited. A record is written first, then a signed call takes the stake. The RGS never holds the money.
- 4. The result is drawn. The ISAAC RNG draws from this round's seed, and the game's maths decides the win.
- 5. The win is paid. The payout is written down before it is paid, then a signed call credits the wallet.
- 6. The round is sealed. Its seed and draw count are saved, so it can be replayed. Settled rounds join a daily signed hash chain.
More players. More servers, automatically.
Each round is one short, independent call. When traffic grows, more copies of the round server run side by side. Nobody adds machines by hand.
- Scales with your traffic: Round servers start on demand and run side by side, so a busy night needs no capacity planning.
- One Postgres database: Every bet, win and record in one database, with row-level security on every table.
- Isolated maths: Studio maths runs in a separate sandbox with CPU and memory limits, never beside production keys.
- Careful releases: Only changed functions deploy, migrations are hash-checked, and tests run on a throwaway stack.
An AI-driven RGS. New protection every month.
AI runs through the server, not only the games. New AI and player-protection features ship every month.
- Ask in plain words: The built-in assistant answers from your live data: GGR, RTP health, big wins and top players.
- AI screens the build: A lab pack can include an automated AI screening of the deployed source, with its findings.
- Watches for harm: Risk scoring flags bonus abuse, bot play and money laundering, and a drift monitor watches every game's RTP.
- A person decides: AI flags and explains. Limits, exclusions, AML decisions and going live stay with your team.
Playing games
Every casino game type, demo or real money, with state that survives a dropped connection.
- Two play paths: /round for hand-written maths and classic reel games; /rgs-fn for games built in the XGENIA editor
- Every game type: Slots, crash, plinko, blackjack and table games, keno, instant win, and any editor node graph
- Demo or real launch: Anonymous, auto-funded play money, or casino server to server
- Session lifecycle: Start, heartbeat, reconnect, end and timeout; demo guests keep their state
- Feature rounds: Free spins and bonuses carry state across rounds, free to play inside the feature
- Unfinished features: Carried over to a relaunch, and played out automatically once the resume window passes
- Feature buy and special bets: Priced per game, switchable per market
- Player choices: Pick bonuses, with full handling of missing and invalid choices
- Open-round grace period: Set per market (Denmark and Sweden: 90 days)
- Win cap: Per round
- Stakes: Integer minor units, with a stake ladder per currency
- Markets per game: Limit a game to the markets where it may take real money
- Idempotent and single-round: Retries never bet twice; one open round per session
- History and replay: For the player
- Game catalogue: REST, plus JSON-RPC for aggregator integrations
- Public pages: Rules per game, UI translations, leaderboard and jackpot tickers
Money and wallets
Connect your operator platform through the seamless wallet: balance, debit, credit and rollback. The operator keeps the funds; signed calls and reconciliation account for retries and crashes.
- Seamless wallet: Balance, debit, credit and rollback, every call signed, with retries
- Six contract checks: Before a casino wallet can be enabled
- No RGS-held real money: A live operator without a checked wallet is refused
- Play-money wallets: For demo operators
- Crash safety: Write-ahead record before each debit and payout; a sweeper refunds orphaned stakes; a reconciler settles the rest
- 41 currencies: Correct minor units (JPY 0 decimals, KWD 3); never summed across currencies
- Settlement: Operator statements and reconciliation, FX rates, tax rules and jackpot seed costs
- Aggregator API: Game list, launch, balance, bet, win and rollback, with per-operator transaction ids
- Platform compatibility: Launch and balance calls in the shape common casino platforms expect
Randomness and fairness
Every round can be replayed from its seed, and crypto players can check each result.
- ISAAC RNG: Reference implementation, versioned algorithms, 256-word cryptographic seeding
- Seed per round: Seed and draw count recorded, so any round can be replayed
- Provably fair: Server seed committed before the client seed; commit, reveal, rotate and a public verify endpoint
- Your own RNG: Your URL, 5-second timeout; unreachable means the round is refused before any debit
- RNG export for labs: Raw output for NIST, Dieharder and TestU01, plus an in-house statistical battery
Responsible gambling
Limits, exclusions and market rules, checked at bet time on both play paths.
- Wager and loss limits: Raising a limit waits for the market's cooling period (Sweden: 72 hours)
- Self-exclusion: Temporary or permanent, with expiry handled automatically
- Reality checks: Per player and per market, with net position shown
- Bet-time checks: Stake cap in local currency, round pacing (Germany: 5 seconds), RTP band, autoplay, turbo, slam-stop and feature-buy rules
- 7 markets configured: Germany, Sweden, Denmark, the Netherlands, Ontario, Great Britain and Malta, plus a default
- Responsible-gambling API: Keyed by the casino's own player id
- Fair rate limiting: A throttled request doesn't use up the player's allowance
- IP allow-list: On every money endpoint
- Kill switches: Suspend play, maintenance mode, end one session, live-sessions view
Publishing from the editor
From the XGENIA editor to the RGS in one step. A republish never puts a live game at risk.
- Editor connection: Sign in once; the install key is kept in the system keychain
- Atomic deploys: Maths deploys as a component, live at once, versioned
- Safe republish: Real money stays off until the new build is verified again
- Web hosting: XGENIA hosting or your own account; no studio can overwrite another's site; file hashes recorded
- Play-money sandbox: Room for 5 games
- Maths lifecycle: Upload, activate, stress test, approve, deploy, plus versions, revert and bet range
- Checks on deploy: Compile, determinism (same seed twice), entropy, stress-test gauntlet and auto-test
- Simulation: Chunked runs for editor games, batch runs for hand-written maths
- Books export: Per bet mode, in the format crypto-casino platforms take
- Maths sandbox: Separate empty project, two lanes, Ed25519-signed jobs, CPU and memory limits, never beside production keys
Pre-certification
Everything the lab asks for, prepared and signed before you submit, to speed up approval. The lab certifies the game.
- Billion-spin RTP runs: On the server, about 240,000 spins a second, with a quick 10-million-round preview
- Signed reports: Confidence interval, coverage per feature, max win, win distribution
- Player-choice games: Verified once per strategy, at the lowest RTP
- Offline runs re-checked: Re-run on the server, shard by shard, before they count
- Go-live gate: Real money needs a signed RTP report for the exact build, with an expiry
- Verifiable anywhere: Ed25519 signatures and a published public key
- Pre-certification pack: One zip: maths source and hashes, RTP report, PAR sheet, replayable top wins, client hashes, rules, signed manifest
- Ten compliance packs: Licence, AML, KYC, responsible gambling, RNG, RTP audit, platform (GLI-19/33), ISO 27001 readiness and more
- Prefilled regulator forms: MGA-F-001 and F-016 checklists
- Game recall: Round verification, and a daily signed hash chain of settled rounds
Jackpots, tournaments and free rounds
Engagement tools that keep their own books, one currency per pool.
- Jackpots: Local or shared pools; random, scatter or must-hit-by triggers; progressive contributions
- Jackpot ledger: Owner-funded seeds on a ledger, one currency per pool, play money kept apart
- Jackpot admin: Create, update, seed, reset, close, list wins, live tickers
- Tournaments: Create, join, score, leaderboard, scheduled finalisation and prizes
- Free rounds: Grant, activate, delay, reject and cancel; voided rounds are given back
Risk
Fraud, AML and RTP drift, watched continuously, with a person making each decision.
- Fraud engine: Risk scoring and alerts for bonus abuse, bot play and money laundering
- AML: Flags and a decision step in the back office
- RTP drift monitor: CUSUM
- GDPR: Export or erase a player
Reports
For regulators and for you, every figure split by currency.
- 8 regulator reports: Compliance, GGR and tax, player activity, responsible gambling, RNG audit, RTP, AML suspicious activity, fraud
- 9 back-office reports: Big wins and wagers, player liability, jackpot funds, AML flags, RTP split, symbol tracking and more
- Reporting API: GGR, RTP, game, player, audit and health
Back office
31 pages for running games, operators and compliance.
- Daily running: Dashboard, bet history, players, sessions, financials, settlement and tax, support
- Per game: Versions, maths, tests, compliance, API docs, distribution, go-live panel, stakes and markets
- Operators: Licences per operator, internal, demo or live mode, wallet enable
- Settings in the app: Translations, FX rates and tax rules
- Team: Invitations, read-only viewers and an AI assistant
- Audit log: Every privileged action
Security and operations
Separate keys, separated tenants, row-level security on every table.
- Three credentials: Operator key, machine-only admin key and user sign-in, with admin MFA
- Tenancy: Organisations kept apart; row-level security on every table
- Alerts: Email or a signed webhook, chosen per studio
- Health: Liveness check and a deep readiness report
- Scheduled jobs: Reconcile, session timeout, alerts, RTP monitor and round anchor
- Careful releases: Only changed functions deploy; hash-checked migrations; tests on a throwaway stack
Client SDKs
Two packages for the game in the player's browser.
- @xgenia/game-sdk: Client, events, typed errors and currency formatting
- @xgenia/game-wrapper: Routes rounds to either play path, with error dialogs for 85 codes
- Player protection: Reality check, spin pacing, inactivity check, autoplay with stop reasons
- Game UI: Paytable, replay, settings, translations, promo bar, menu and operator bridge
Certification
XGENIA does not certify games or grant operator licences. The RGS signs measurements for the exact build; an accredited lab certifies the game. Configured market controls are not regulatory approval.