Join the waitlist

Plans and limits

What Starter plan includes, what it limits, and what a paid plan adds.

There are three plans: Starter, Publisher and Enterprise. Most of this chapter is about Starter, because it is the one you can reach on your own.

Starter is where you build and test a game. It is not where a game meets an audience. Registering costs nothing, and scaffolding, the dev loop and playing your game on the real Engine all work with no approval needed. A hosted deploy to a public Playground needs your account approved first, which the next section covers. The limits below are sized for development rather than for a crowd, and a game that needs to reach real fans needs Publisher or Enterprise, which a person at Monterosa arranges with you.

Going over a limit never charges anybody, on any plan. Most limits are counted rather than enforced while we learn how games are used: Monterosa sees what would have been capped and is alerted, and nothing is turned away. The allowances in games, the per-second limit and the per-player rate limit do refuse, because they protect the service for everybody. Reached limits lists what refuses and what is counted.

Availability now

Local inspection, scaffolding and validation work without an account. Running the dev loop and verify both require a signed-in session, and nothing more: an account waiting for approval can register up to three games and play them on the real Engine, each practice round capped at 100 plays a day, and gamestage status lists the games it has registered. Deploying waits for approval.

The hosted Starter path runs on the CLI's own default, https://api.gamestage.ai. Sign in, get the account approved, and deploy to a public Playground from the published route with nothing else to configure.

Approval is the gate rather than availability: gamestage login leaves an account pending and somebody at Monterosa approves it. Gamestage is not commercially launched, so that approval is a conversation rather than a form.

Dev and prod

A game is either dev or prod, and a game on Starter is dev. Two separate things have to be true before it counts as prod, and you control one of them:

  • You approve your own game. gamestage promote <game> records that approval, and always succeeds for a game that exists and is not archived. Approving your own game is not a purchase, so there is nothing here for a plan to refuse.
  • Monterosa moves your workspace onto a paid plan. Only an operator does that. gamestage plan live is refused with operator_required and changes nothing.

Until both are true the game is dev, and gamestage promote tells you which of the two you are waiting on.

What is built today is the record and the gate: the approval is stored, and the two are composed into one answer the CLI reports. Serving does not read the approval: a dev game and a prod game are reached the same way and play the same way, so promoting a game records the decision rather than changing what a fan meets. Promotion creates no second deployment and no second id either, so the files, the scores and the leaderboard are unaffected.

Declared limits

Backstage's contract currently defines:

MeterStarter limit
Games in development3
Live games1
Monthly devices1,000
Storage250 MB

Monthly devices counts distinct browsers, not distinct people: a player id is minted per session and kept in that browser's storage for that game, so one person playing on a phone and a laptop counts twice.

The one-live-game allowance is updated from game state and enforced on deploy and wake. The devices and storage meters are also real: devices sums what each game reports, storage is recomputed from what the bucket actually holds. Meters count real usage; reaching 1,000 devices or 250 MB does not refuse a deploy. Monterosa is alerted at 80% and 100% of each, once a month. Of the four, the one-live-game and three-games-in-development allowances refuse.

Each Starter game also has a daily limit of 100 plays, counted across all its rounds. Plays past it are still played and are counted as over the limit, and Monterosa is alerted at 80 and at 100 that day. Usage and plan in Stage shows today's plays, how many went over, and anything turned away.

Arcade and Mystery count differently. An Arcade game counts runs, and its daily limit is 5,000 runs, because one fan plays many short runs; it is alerted and counted the same way. A Mystery game's plays are counted in the same record with no daily limit, because its limit is the spend ceiling on the questions it asks.

Older planning files still call the plan Runtime and name 1,000 concurrent players and 10,000 monthly active players. Backstage's contract has no concurrency meter, so no concurrency figure anywhere is enforced. The App Manifest nomenclature and the contract above are the current source for the plan name and declared meters.

One live-game limit means a redeploy of the same live game is allowed. To put a different game live, suspend the first one:

gamestage suspend <game-id>
gamestage wake <game-id>

Suspension is reversible and returns the live slot. Archive is different: it takes the game off the air, retains its record and id, and moves its bundle outside the served prefix.

What Starter includes

  • Shared hosting: games are served from one shared Playground domain.
  • Your own Studio Space: your workspace gets its own Space, made on your first deploy. Nothing about it is shared with anybody else's games.
  • One live game: drafts do not consume the live-game allowance.
  • Managed Engine rules: the same built game formats as local development.
  • No surprise billing: the contract has refusal and busy outcomes rather than an overage charge.
  • Suspend and wake: sleeping, manual suspend and manual wake states exist.

What Starter does not include

The current entitlement rules reserve these for paid plans:

  • Signal: Monterosa's own engagement analytics, shown in Stage as Monterosa Analytics. It is available on Publisher and Enterprise only, and you switch it on for your workspace on Stage's Analytics page or with gamestage workspace signal on. Moving to a paid plan leaves that switch off, so turn it on there. It needs no change to your code.
  • Custom analytics destinations: the manifest can declare destinations, but changing routing is a paid entitlement.
  • In-game bug capture: on Starter, use your repository's issue tracker directly.
  • Prize promotions: a prize needs human approval and is refused below Publisher.
  • Ads: the shop panel is in preview, switched on per game by Monterosa, subject to approval and commercial terms, and the retail partner must approve each use. See Ads.
  • A contracted service level: an SLA belongs to an Enterprise agreement.

The manifest can declare a Monterosa Analytics destination. That declaration alone is not proof that analytics is flowing: production ingestion and Studio visibility are separate concerns from the manifest field.

Reached limits

LimitStarterPublisher and Enterprise
Live games, games in developmentRefusedRefused
Plays a second (2,560 a game)Refused with busy and capped, retry in a secondThe same
One player asking too fastRefused with HTTP 429 and Retry-AfterThe same
100 plays a game a day (Arcade: 5,000 runs; Mystery: none)Counted, not refusedNo daily limit
Fair-use limit (the per-second limit held across the audience for 30 seconds)The game pauses for 30 minutes, refusing with fair_use, and Monterosa is toldMonterosa is told and the game keeps taking plays
Monthly devices, storageCounted, not refusedCounted, not refused

Monterosa can switch an individual limit to refuse for one workspace while it trials capping. A day cap that refuses answers busy with capped_today and the seconds until midnight UTC; a devices or storage cap refuses a deploy with meter_breached.

Expected refusals carry a stable code:

  • live_allowance_reached: suspend the other live game or change plan.
  • meter_breached: a devices or storage cap that Monterosa has switched on for your workspace is reached.
  • tier_required: the declared feature needs a paid plan.
  • operator_required: the plan you asked for is one a person arranges. Your workspace is unchanged.

A refusal is returned as a normal command result and exits 1. In JSON, branch on code. Do not retry a refusal without changing its cause.

The stored plan keys are runtime, live and enterprise; creator-facing surfaces call them Starter, Publisher and Enterprise.

Publisher and Enterprise are human conversations rather than a completed self-serve purchase flow. Paid customer onboarding also needs a Monterosa account and org created by a person. Do not use gamestage plan as evidence that commercial approval or dedicated infrastructure exists.

gamestage plan enforces that. Starter is the only plan a workspace can move itself onto; asking for Publisher or Enterprise is refused with operator_required and changes nothing. An operator moves a workspace onto a paid plan out of band. Moving back down to Starter is not refused, because it grants nothing.