Getting started as a studio building games on hiziYou are a game studio building a game on the hizi engine with your own frontend. Follow the five steps in order, from engine config to operator-ready.Start the quickstart guide
Hizi AppYou want help with the hizi app itself: building or importing games, configuring studios and partners, and publishing your setup live.Get started with the hizi app
Operator APIYou are an operator or aggregator integrating hizi.io games into your platform. It covers game launch, player management, balances, and transactions.Read the Operator API
Game Studio APIYou are building a game engine, or running your own RGS, and want it to talk to the hizi.io platform. It covers gamerounds, transactions, and certified RNG.Read the Game Studio API
Operator & Game SettingsYou want to configure operator-level settings, game permissions, payment retry strategies, or regional access controls in the backoffice.Configure settings
Hizi EngineYou want to understand how the hizi engine serves pre-computed game outcomes: entries and weights, multi-step scenarios, provably fair RNG, and how generate → deploy → play fits together.Open engine docs
Hizi Engine GeneratorYou are writing a game engine and need to turn millions of simulated outcomes into the compact JSONL files the engine serves. It covers entry merging, buy-feature pools, and KPI math.Read the Generator docs
Hizi Engine SDKYou are building a game frontend against a running engine. It covers the login, loadConfig, placeBet, and collect lifecycle, typed responses and errors, and a guide per game type.Read the SDK docs
Operator InterfaceYou are wiring a game client to an operator's or aggregator's lobby. It covers the client-side event protocol, methods, events, and per-operator notes.Open Operator Interface docs