天照神雷
Thunder of Amaterasu
A 6×5 tumbling slot. Eight or more matching symbols anywhere on the board pay — no lines, no adjacency. In free spins the multiplier accumulates and never resets.
Slot content & RGS provider
Verifiable math.
Money that never goes missing.
We build HTML5 slots and the remote game server behind them. Integration is seamless single-wallet — no sub-accounts to open on your side, and no code change to launch a new title.
The numbers on our current title
Read directly from the game definition file — the same one the production server runs.
- Return to player
- 96.85%
- Max win
- 5,000× bet
- Calibration sample
- 200M spins
- Round retention
- 5 years
Games
Every title ships with its full spec sheet — RTP, volatility, hit rate, paytable and trigger frequency. No need to ask.
Captured straight from the running game — real boards, real wins, real multipliers.
Why a new supplier is worth an hour of your time
We have one game, and we won't pretend otherwise. What we can put side by side is something else: what this RGS does when things go wrong.
Math that survives certification
Two independent implementations, compared cell by cell over 100,000 spins.
Alongside the production engine we maintain a second, independently written simulator. Both are fed the same RNG seed and compared spin by spin, cascade by cascade — board, clears, multipliers, wins. Not one cell may differ across 100,000 spins.
Statistical comparison cannot prove equivalence: a 0.3% RTP gap is invisible in a million-spin sample but fails this test outright.
Every RTP configuration ships with its calibration record. The current version was measured over 200 million spins, standard error 0.06%.
A wallet integration built for the worst case
When a debit's outcome is unknown, not a single symbol is dealt.
Most incidents are not “the debit failed” — they are “we don't know whether the debit happened.” Timeouts, dropped connections, 5xx, unparseable responses: we treat all of these as a third outcome, neither success nor failure.
The round stops as pending and nothing is dealt — a dealt round cannot be taken back. A reconciliation worker then re-queries your wallet with the same idempotency key until the truth is known.
There is exactly one reconciliation identity: the change in your balance equals the change in our ledger. A 100,000-round chaos test injecting timeouts, duplicates and disconnects closes it at zero.
Every round is reproducible
Replay recomputes the round. It does not play back a recording.
Rounds and ledger entries are append-only, enforced by database triggers that reject UPDATE and DELETE — not by application discipline.
Replay takes the round's original RNG seed, recomputes the entire round, and reconciles it against the log spin by spin: win amount, trigger counts, RNG draws consumed. A mismatch shows “replay failed” rather than a plausible-looking fabrication.
Rounds are retained for 5 years. Partitions past the hot window are archived to compressed files whose hashes are re-verified on a schedule.
What integration looks like
Four steps from credentials to the player's first spin.
01
Get credentials
We issue an API key, a signing secret and a sandbox. Keys rotate on demand with no downtime.
02
Exchange for a token
When a player opens the game, your backend calls launch once with the player id, currency and game code, and receives a single-use token.
03
Send the player in
Append the token to the game URL. Pure HTML5, no plugins, one build for desktop and mobile.
04
We call your wallet
Every bet and every payout hits your wallet API in real time with an idempotency key. The money never leaves your system.
Launching a new title needs no code change on your side — just a different game code at launch.