Type: custom iGaming web platform (crash + mini-games)
1. Work format
• All development only on our server
• Access provided (SSH / DB / repo)
• All code and architecture belong to the client
• No Firebase, no-code, client-side logic
2. Goal
To build a server-side gaming platform that can handle traffic, with:
• controlled mathematics (RTP / House Edge)
• a full admin panel
• scalability and white-label options
3. MVP: games (10 pcs)
Crash (1 engine, different UIs):
1. Aviator-style
2. Speed Crash
3. Chicken Road Crash
4. Space Monkey Crash
Mini-games:
5. Plinko
6. Dice
7. CoinFlip
8. Mines
9. Tower Rush
10. Wheel (mini-roulette)
4. Key architectural requirements
• All mathematics and RNG only on the server
• Client — only visual
• All games — separate modules
• Crash via WebSocket
• Scalability for 5,000+ online
Stack:
• Backend (Node / Go / Python — not critical)
• PostgreSQL + Redis
• Queues / async processing
• Docker / proper deployment
5. Finances
• Ledger approach (balance = sum of transactions)
• Types of operations: deposit / bet / win / bonus / withdraw
• Balance is never stored as a single number
6. Gaming mathematics
• RTP: 80.00 – 99.99%, adjustable in the admin panel
• House Edge is calculated automatically
• Volatility: low / mid / high
• Payout tables — JSON, editable
Crash:
• crash-point is generated in advance
• cashout is recorded by the server
• limits: max bet / max payout / period cap
7. Admin panel
• Dashboard (users, deposits, profit, pending)
• Game management:
• RTP slider
• volatility
• payout JSON
• Users
• Finances
• Promo codes
• Withdrawals (manual approve/reject)
8. Security
• Cryptographically secure RNG (not Math.random)
• server seed + nonce
• Anti-exploit:
• win limits
• protection against replay / race / packet abuse
• Log of each round (for disputes)
9. Bonuses (MVP)
• First deposit bonus
• Reload bonus
• Cashback / rakeback
• Separate bonus balance
• Wagering, limits, logging
• Management through the admin panel
10. White Label
• One engine → multiple brands
• Brand = domain + design + settings
• UI separated from logic
• Architecture ready for cloning
11. What the client provides
• Design / UI
• Content
• Server
12. What the developer must deliver
• Source code
• Documentation
• Docker / instructions
• Database structure
13. Acceptance criteria
• All 10 games work
• RTP actually affects the mathematics
• Balances match according to the ledger
• Admin panel manages everything
• Nothing crashes under load