Gamestage takes a game prototype that runs in a browser and turns it into a live fan game. Your page keeps its interface. The Engine, a server run by Gamestage, holds the answers, works out the scores, enforces the play limits and settles results.
A prototype keeps its answers in the page, where anyone who opens the developer tools can read them. That is acceptable for a demo and stops being acceptable when strangers play for something. Moving the answers off the page also gives a live game logs, monitoring and limits on how often one person can play.
How Gamestage changes your game
Your web app sends each play to the Engine. The Engine holds the material a player must not see, works out the result and sends back what it decided.
BROWSER BEFORE BROWSER AFTER
────────────────────────────── ──────────────────────────────
interface and input interface and input
answers and values ↓ intent
scoring and limits ┌────────────────────────────┐
│ ENGINE │
│ answers, scoring, locks, │
│ attempts, settlement │
└────────────────────────────┘
↓ committed outcome
the page renders what it is toldThe decisions move to the server and you keep the interface.
Who Gamestage is for
Gamestage is for creators and developers who have a browser game prototype and a coding agent such as Claude Code or Codex. You install the CLI tool. The agent then reads your existing source, moves private material into the App Manifest, wires a newly generated client and runs a series of checks.
You make the decisions an agent should not: rights, audience, identity, and anything that changes what a live audience can touch.
You do not need to have used Monterosa before. Inspecting your game and scaffolding its manifest need no account. Running it against the Engine needs one, once you reach that step.
What you provide
- The game. You write the interface, the visuals and the page. Gamestage does not draw anything, own a scene graph or ask you to adopt a framework.
- Player identity. Gamestage ships no identity provider. It accepts OIDC through JWT tokens: a game that wants named players points at its own issuer and keys, and Gamestage checks the tokens your existing login already hands out.
What Gamestage provides
- The Engine. It holds one game format's rules and answers questions about a play.
- Hosting. Every deployed game, on Starter and above, is a project on Monterosa Interaction Cloud with real editions. Starter games are served from a Playground environment. A paid plan changes which Space your projects sit in and adds Studio's content management and live-operations tooling. Hosting comes with the Monterosa platform on every plan.
Where the product is today
Gamestage is in Preview and is being tested with Monterosa customers. The two halves of the product are at different stages.
The local route is active. Inspecting a game, choosing its format and scaffolding the manifest need no account. Playing the game and proving the result in a browser need one, because both play against the deployed Engine on your account, as test plays that reach no leaderboard.
The hosted route is in Preview. The CLI points at https://api.gamestage.ai, and Backstage needs an approved account rather than open signup.