Boxman Studio beta
Stake Engine docs Open Studio
Early access — free while in beta

Build Stake Engine slots without the boilerplate.

Math, assets, animation, testing and publishing — one studio in the browser, on top of the official Stake Engine math and web SDKs.

Open Studio Read Stake Engine docs

Output: static frontend bundle + math package, ready for the Stake Admin Control Panel.

Built on the official Stake Engine toolchain, unmodified.

  • math-sdk (Python)
  • Rust optimizer
  • web-sdk (PixiJS + Svelte)
  • Stake ACP file format
How it works

Six tabs, one game. The same order you would do it by hand.

Every step writes real files into a real math-sdk game and a real web-sdk app. The studio just removes the typing between them.

  1. 01

    Project

    Start from a math type: lines, ways, cluster, scatter pays or expanding wilds. Each maps to an official math-sdk template and a matching web-sdk app, so the skeleton is correct from the first save.

    0_0_lines0_0_ways0_0_cluster
  2. 02

    Math

    Edit symbols, paytable, paylines, reel strips, bet modes and win distributions in a visual editor. Run a simulation in one click and get RTP, hit rate and distribution stats back from the official math SDK and its Rust optimizer.

    game_config.pyreels/*.csvlookup_tables
  3. 03

    Assets

    Upload Spine skeletons, sprite sheets, audio sprites and bitmap fonts. Preview Spine animations in the browser, then map each asset to a slot: symbols, background, reel frame, big win, loader.

    .skel / .atlasaudio sprite.fnt
  4. 04

    Events

    For every book event, decide what the client does: which sound plays, how long to wait, which animation runs, and any extra visual events to emit. Rules compile into the game source, not into a hidden runtime.

    revealwinInfofinalWin
  5. 05

    Test

    Play any generated book in the real game engine, in-browser. Pick a book by number, by criteria or from the force file, or run the full bet cycle against a mock RGS that answers from your own lookup tables.

    books_base.jsonl.zstforce_record/wallet/play
  6. 06

    Publish

    Build a static frontend bundle and a math package in exactly the format Stake ACP expects — compressed books, lookup CSVs, index and config files. Download the zip and upload it.

    publish_files/index.html.zip
Why Boxman

No proprietary runtime. No lock-in. Just less typing.

The studio orchestrates the official SDKs; it does not replace them. What you get out is what you would have written yourself, only faster.

Official SDKs underneath

Math runs on the open-source math-sdk; the client is the open-source web-sdk. The same code Stake Engine documents, with nothing in between.

Plain files you own

Every build is a folder: Python game config, reel CSVs, books, lookup tables, a static web app. Export it at any point and keep going by hand.

Teams and versions

Organizations with owner, admin, editor and viewer roles. Every math run and frontend build is kept with its summary and logs, so nothing is lost between iterations.

Nothing to install

Simulation, optimization and Vite builds run on cloud workers. You need a browser and a Stake Engine account; no Python, Rust or Node toolchain on your machine.

export · pharaoh-lines · build 14what you download
math/
  games/pharaoh_lines/
    game_config.py        # paytable, paylines, bet modes, distributions
    reels/BR0.csv  FR0.csv
    library/
      publish_files/       # books_base.jsonl.zst, lookUpTable_base.csv, index.json
      lookup_tables/  forces/  configs/
      stats_summary.json   # rtp 0.9652 · hr 0.274 · std 8.13
frontend/
  apps/bx_pharaoh_lines/
    src/game/config.ts  assets.ts  boxmanEventRules.ts
    dist/                # static bundle for Stake ACP
pharaoh-lines-build-14.zip
Math types

Start from a template that already passes.

Each type corresponds to a sample game in the official math-sdk and a game app in the web-sdk. Change what you need; the rest is known-good.

Lineslines

Classic left-to-right paylines over a 5×3 board with configurable line sets, paytable and free-spin reel strips.

Waysways

Adjacent-reel wins in any row position — 243, 1024 or whatever your board dimensions allow.

Clustercluster

Connected groups of matching symbols with tumbling reels and per-position board multipliers up to a configurable cap.

Scatter paysscatter

Pay-anywhere wins counted across the whole board, with tumbles and variable rows per reel.

Expanding Wildsexpwilds

Line pays with wilds that expand to fill a reel, and a landing-wild distribution you tune per bet mode.

Lines + Feature Matchlines_feature_match

Line pays with multiplier wilds in free spins and a feature-match trigger — the heavier lines template for feature-driven games.

FAQ

Questions developers ask first.

Anything else — hello@boxman.studio.

Is this official Stake software?

No. Boxman Studio is independent tooling built on top of the open-source Stake Engine SDKs (math-sdk, web-sdk). It is not affiliated with, endorsed by or operated by Stake.com. Publishing to Stake Engine still happens through your own account in the Admin Control Panel.

Do I still need Python or Node installed?

Not to use the studio. Simulations, the Rust optimizer and the Vite build run on cloud workers. If you export a project and want to continue locally, you will need the normal SDK toolchain: Python 3 for the math, Node and pnpm for the frontend.

Can I export and continue by hand?

Yes. What you download is a standard math-sdk game directory and a standard web-sdk app — game_config.py, reel CSVs, the generated library/, and a Svelte app with a generated config.ts, assets.ts and event rules. Open it in your editor and keep working; nothing depends on the studio.

How much does it cost?

Early access — free while in beta. Pricing for teams will be announced before the beta ends, and projects created during the beta stay exportable regardless.

Who owns the game files?

You do. Your assets, configuration, generated math and builds belong to you. The studio stores them so you can work on them; it claims no rights to your game, and the SDK code inside the output keeps its original open-source licence.

How does testing work without an RGS?

Two ways. The book player loads the real web-sdk game in an iframe and feeds it any book from your build over postMessage, so you can replay a specific outcome, a random one, or a forced one from force_record. The mock RGS implements /wallet/authenticate, /wallet/play and /wallet/end-round from your lookup tables, so the game runs its full bet state machine exactly as it will on Stake Engine.

Open the studio and run your first simulation.

Pick a math type, hit run, and read the RTP a few minutes later. Free during the beta.

Open Studio Talk to us