Slotty Labs is the RGS behind its own five original titles — NIST-standard RNG, server-authoritative outcomes, four selectable RTP models per game, and a round log that reconstructs any bet on demand. Integrated with one TypeScript SDK.
A remote gaming server is the component that owns game logic. The client in the player's browser is presentation: reels, animation, sound. Every decision that touches money happens on the server — the random number is drawn there, the paytable is applied there, the win is calculated there, and the round is written to durable storage there.
That separation is not an architectural preference. It is the precondition for certification. A testing lab cannot certify a game whose outcome is computed in a client it does not control, and a regulator cannot adjudicate a player dispute against a round that was never persisted.
Slotty Labs operates as the RGS for its own catalog. There is no third-party studio behind the games and no aggregator between the operator and the engine.
Certification review concentrates on a small number of questions. The engine is built so each one has a document, a dataset, or a reproducible run behind it.
NIST SP 800-90A Rev. 1 HMAC-DRBG (SHA-512, 256-bit security strength), seeded from multiple entropy sources, with continuous statistical self-tests modelled on NIST SP 800-22. Process-isolated with internal RPC access only.
Every RTP variant is a separately calculated model, then verified with 10,000,000 fixed-seed Monte Carlo rounds — landing within ±0.5% of the theoretical figure. The written model and the simulation output ship together.
SHA-256 commit-reveal on every real-money round: the seed is committed before the bet and revealed after, so a player can verify the outcome independently on a public verification page.
Hash-chained audit logs with WORM storage and Merkle anchoring, plus a complete seven-dossier package built to GLI-19 (Interactive Gaming Systems) standards for accredited labs.
The same game ships at 92%, 94%, 96% or 97% — each one an independently calculated and independently simulated math model, not a multiplier applied to a single base model.
| Title | Genre | Volatility | Max win | RTP variants |
|---|---|---|---|---|
| Slotty Slots | Online video slot | Medium | 500× bet | 92 / 94 / 96 / 97% |
| Safe Smash | Mines-style instant game | High | 250× bet | 92 / 94 / 96 / 97% |
| Bit Key Rush | Tower / ladder instant game | High | 500× bet | 92 / 94 / 96 / 97% |
| Fox'n Flock | Crash-style cash-out game | Medium | 200× bet | 92 / 94 / 96 / 97% |
| Katapuuult | Arcade instant game | High | 300× bet | 92 / 94 / 96 / 97% |
Integration is a TypeScript SDK with zero runtime dependencies on Node 18+. The core path — single sign-on plus game embedding — is roughly twenty lines. Players are created automatically on first launch, keyed to the operator's own player IDs, so there is no user-migration project and no second identity system to reconcile.
Game launches are authorised with single-use RS256 tokens that expire in thirty seconds. Round outcomes, wallet movements and lifecycle events arrive as HMAC-SHA256-signed webhooks with retries and a dead-letter queue, so a brief outage on the operator side does not lose events.
A sandbox with forced outcomes lets QA drive specific results — a max win, a bust, a mid-round disconnect — without waiting for probability to cooperate.
A remote gaming server is the system that actually runs casino game logic. The player's browser only renders the game; the RGS holds the RNG, resolves every bet server-side, applies the configured RTP model, writes the round to a persistent log, and reports the result back to the operator's wallet. Because outcomes are decided server-side, an RGS is what makes a game auditable and certifiable.
An RGS runs the games. An aggregator resells access to other studios' RGS platforms and takes a share of revenue for the routing. Slotty Labs is the RGS for its own five original titles, so operators integrate the source rather than a reseller layer on top of it.
Yes. Games are delivered as HTML5 clients embedded through a single-use, 30-second RS256 launch token, and the operator controls branding, lobby placement, and the surrounding experience.
Through a seamless-wallet model: the RGS calls the operator's balance, debit and credit endpoints — or uses the Slotty Labs double-entry wallet directly, if the operator would rather not run money infrastructure at all.
Yes. Rounds are event-sourced and deterministically replayable from their event log, and each round is tied to the exact game version that produced it — which is what dispute resolution and lab review both require.
Book a technical demo — RNG architecture, Monte Carlo evidence, round replay and the certification dossier, walked through live.