How we work
Process.
Slot games fail in review for the same reasons every time: unverified math, missing edge cases, a single restricted word. Our pipeline is built to catch each one before it ships.
Phase 01
Brief
Theme, math target (RTP / volatility / max-win), feature set, deadline, budget. Discord intro, written summary, contract.
Artifacts
- → Scope doc
- → Theme moodboard
- → Math target sheet
Phase 02
Math
RTP modeling, paytable shape, feature math, simulated books (millions of spins). Verified by Python probes before any pixel is drawn.
Artifacts
- → math/base.csv
- → math/bonus.csv
- → Simulation dossier (PDF)
Phase 03
Design
Symbol set, UI direction, win presentation, motion language. Layout sketched in slotsite (our in-house animator) before code begins.
Artifacts
- → Symbol sheet
- → UI mockups
- → Motion reference reel
Phase 04
Build
Next.js 15 static-export project, Pixi v8 canvas, GSAP timelines, full RGS client. Built to match Backstreets — the most review-tested reference in the studio.
Artifacts
- → out/ build
- → Replay panel
- → Mobile portrait layout
Phase 05
QA
Pre-submission gate: restricted-word audit, RGS edge cases (zero-win, insufficient balance, active-round recovery), bet-level coverage, replay integrity.
Artifacts
- → QA checklist
- → Replay sample set
- → Audit log
Phase 06
Submit & iterate
Stake Engine submission, reviewer feedback in the portal, fix passes, ship. You can watch every iteration in the client portal — math, art, animation, to-do.
Artifacts
- → Reviewer log
- → Iteration tracker
- → Release tag