Remote game server
Rounds, outcomes, payouts and settlement. Every figure a player sees was decided here.
Your own title, exclusive to your brand — the mechanic, the maths and the theme built for you, running on our remote game server and launched through the same one-call integration as our catalogue.
Four stages, and you see it working at every one of them. No stage is a black box that ends in a demo.
We start from what you actually want: a mechanic, a season, a market, or a game you have seen work and cannot license. We come back with a shape, a maths outline and an honest estimate — including when the honest answer is that it is not worth building.
Return to player, volatility, the payout ladder and the caps, agreed with you and implemented in the engine rather than assumed on a spreadsheet. The numbers are tested against the code that will run them.
Art direction, the client, the animation and every ending it can have. Built in the open with playable builds throughout, so the first time you see it is not the week before launch.
It ships on our remote game server with your configuration, your limits and your currencies. We keep it running, and changes to limits or theming are configuration rather than a release.
We are not a front end on somebody else's engine. The server that decides a round is ours, which is why configuration, reporting and a fix all come from one place.
Rounds, outcomes, payouts and settlement. Every figure a player sees was decided here.
Stakes, wins and every movement recorded against the round that caused it.
RTP, stake limits, maximum payout, currency and per-game settings, applied without a client release.
Operators, games, limits, rounds and reporting, with an approval trail on the changes that need one.
Clients are served from a single origin and routed by game code, so the token never leaves the domain it was minted for.
Append-only audit records, configuration snapshots against rounds, and a client that cannot decide anything.
There is no per-game SDK and no bundle to host. Your server asks ours for a session; we hand back a URL; you open it. The token in that URL is the session, and it is short-lived.
→ 201 { "launchUrl":
"https://game.gundabadstudios.com/spire?token=…" }Your platform opens a session for a player with an API key. The response carries a launch URL with a short-lived token in it.
Point the player at that URL, in an iframe or a tab. The token is the session: no second handshake, no SDK to embed, no per-game integration.
All of our titles are served from a single domain and routed by the game code in the path. Adding your next game is a configuration change, not an integration.
It depends on the mechanic — a new instant-win title is a very different build from a new multiplayer round-based game. We scope it properly before quoting, and we would rather tell you early that an idea is expensive than discover it halfway through.
That is part of the agreement, and we are flexible about it: exclusivity for a period, exclusivity in a market, or an outright exclusive title. We will put it in writing before any work starts.
Our platform exposes a session API for launching games and a wallet boundary for stakes and wins. Tell us what your platform expects and we will tell you plainly what fits and what needs an adapter.
Certification depends on the licence you hold and the market you are in. We supply the maths documentation, the RNG and engine detail and the build artefacts a testing house asks for, and we work to the requirements your licence sets.
Often, yes — the games read their theming and configuration from the platform rather than from hard-coded values. It is the fastest route to something that feels like yours, and it can be the first step towards a dedicated title.
A mechanic, a season, a sponsorship, a market nobody serves properly — bring the idea and we will tell you honestly what it takes to build it.
Or write to hello@gundabadstudios.com