hizi docs

Appearance

Getting started in the hizi app ​

Welcome to hizi!

TIP

The system saves everything you configure in hizi as a draft first. Publish (see below) pushes your changes to the relevant sites.

Below is a summary of where to start, depending on your aims.

1. I want to build games with hizi ​

Build your game with the in-house hizi engine. Then bring it into the app under Hizi Engine Config. Launch the engine's own creator tool from there. Save your work as a config. The config has its own lifecycle: in progress, publishing, published. It also has its own versions. When you have a config you are happy with, attach it to a Game. Promote that version to staging or production. This is the same promotion mechanism as for every other game type. See the hizi engine documentation for details.

2. I want to import my own games ​

Do you have a game engine or code of your own? There are two ways to bring it onto the platform. Set the method as the Game's Origin:

  • Docker image: your engine runs in a container, hosted on hizi's infrastructure. Register your GitLab-based Docker registry once, under Docker Registries. Then hizi syncs your repositories and images automatically. On each Game, create a Docker version. Pick the synced image and tag. Promote it the same way as a hizi-engine build.
  • RGS-to-RGS: your game runs entirely on your own infrastructure. hizi's RGS only points at your wallet API over HTTP. You bring your own certified RNG (random number generator). We do not need core-docker or GitLab access on our side. This is the classic integration model. See the Game Studio API docs for the wallet contract.

In summary: pick Docker image if you want your engine hosted with us. Pick RGS-to-RGS if you want to keep it entirely on your own infrastructure.

3. Now I want to distribute my games ​

You can build games in any of the above ways. To distribute them to operators, use the Partner → Identity chain:

  1. Create a Partner for the operator or business relationship. Assign an Account for billing, a Legal Entity for invoicing, and any Geo Rules.
  2. Under that Partner, create one Identity for each operator brand or casino site. The Identity connects to a specific site. It carries its own integration settings and credentials. It can also carry Settings and Game Settings templates for consistency across many Identities.
  3. Set each Game's permissions to control which Partners or Identities can access it.
  4. Select Publish. This step pushes your published games, current versions, and permissions live to the operator sites. Everything before this step stays a draft.

Use Game Launcher and Wallet test runner along the way. Verify that a game launches correctly. Verify that your wallet integration behaves correctly before you go live.

Note

This is a high-level summary of the flow. It assumes the integration, contract, and any QA work with the relevant Partner or Identity are complete and signed off. Some operators may also have additional steps.