Getting started
The walkthrough below reflects the actual submission pipeline — from organization setup through automated checks and reviewer play-testing to a listed, verified game.
Create or claim your publisher organization
If your provider application was approved, your organization already exists and you were made its owner. If you need another organization (e.g. a second studio slug), visit /admin and use "Create a publisher" — enter your Stake Engine provider slug so catalog games matched to that slug show up in your console immediately.
Open adminAdd your game
From the publisher console, start a new submission for a game not yet in the Stake Engine catalog, or open an existing catalog game already matched to your organization.
Submit new gameProvide a demo URL and a play URL
The demo URL is used by automated probes — it should include a live RGS session so the probe can drive real rounds. The play URL is a stable, non-expiring link (e.g. a hosted static build) that reviewers use to actually play the game; unlike the demo URL it has no expiring session ID, so it stays playable indefinitely.
Upload math books per mode
Upload the lookup/paytable book for each declared mode (Base, Bonus Buy, Super Buy, etc). StakeBench analyzes each upload for RTP, hit frequency, max multiplier, and row count so you and reviewers can sanity-check the math before anyone plays.
Complete the submission checklist
Work through the publisher checklist items for your submission — assets, disclaimers, declared modes, and any jurisdiction findings that need acknowledgment. Checked items unlock the next stage of review.
Publisher consoleAutomated probes run
Once submitted, automated checks hit your demo URL, capture screenshots and network activity, and record findings with citations (screenshots, rounds, RTP, endpoints). These land in your submission as automatedFindings — pass, fail, or warn per checklist item.
Reviewer play-testing happens
Real reviewers — people who play on Stake — spin each of your declared modes, read your published rules, and answer a task-based rubric with server-timed results. Their decisions (pass / fail / waived) are recorded per checklist item alongside their notes.
Iterate on feedback via the dashboard
Your publisher console shows submission status, reviewer activity, and any fail findings as they come in. Address the feedback and resubmit — there is no limit on iterations.
View submissionsApproval and listing
Once the checklist, automated findings, and reviewer decisions are all satisfied, an admin marks the submission approved and your game is listed with its verified fairness data.
Questions about a specific submission? Check its status and reviewer notes from the publisher console.