Game studios shipping an online game

The game backend your AI assistant can tune, and you release.

Players, friends and messages, lobbies, config, saves, currencies, cards, progression, commerce, analytics, crash reports and Sign in with GreenMind. Every service in a test and a production environment, managed from one console and reached through one API. Config and crash reports each have an MCP server, so the assistant you already use can change a test environment and queue a change to production for a person to release.

The console's Compare environments page: one new and five changed config values in test, ticked, with a button to promote them to production now or add them to a release called Autumn storms.
Compare: see what differs between two environments, then promote what you choose.

Who it is for

It is built for AI-first game development: an assistant signed in with GreenMind can read crash reports and tune config in test, and a person releases what reaches players.

It is for a studio that would rather make its game than run accounts, lobbies and config servers. We built it for our own games and opened it to other studios, so an org on the platform uses the same services ours do.

Give your game server a key, sign your players in, and read config, flags and lobbies from one API. In Unreal Engine, the free GmPlatform plugin does that for you, and GmCommon, the framework our own games are built on, is there under licence.

What your game gets

  • Players

    A player table, sign-in, and the tokens your game client uses.

  • Sessions

    Lobbies your players create, join and ready up in, started by your game server.

  • Config

    Values your game reads at runtime and you change without a new build.

  • Feature flags

    Switch features on and off per environment.

  • Tours

    Guided introductions, each shown to a player once.

  • Blog

    News and patch notes, written in the console and read through the API.

  • Support

    Support requests and player reports, worked by your support staff.

  • Legal documents

    Your terms and policies, and a record of which version each player accepted.

  • Player saves

    Saved data per player, in slots you name, with safe concurrent writes.

  • Sign in with GreenMind

    OAuth clients that let players sign in to your game or site with GreenMind.

  • Analytics

    Visits to your website, counted in a dashboard of the environment's own.

  • Crash reports

    Your game's crashes from Unreal's crash reporter, grouped into bugs for triage.

  • Commerce

    Sell in your game through Steam with your own keys: products, orders, entitlements and currency your server collects.

  • Realms

    Seasons, or any span of time that starts every player with a fresh inventory.

  • Inventory

    Currencies with a ledger, and items: bought with currency, or granted by your server.

  • Cards

    Card types and templates, the cards each player owns, and their decks.

  • Progression

    XP, skill trees whose nodes are bought with currency, and unlocks.

  • Stats

    Counters per player and per environment, in one realm or across all of them.

  • Friends and messages

    Players add friends, see who is online, message each other and report abuse, signed in with the same player token your game already holds.

How it works

  1. Sign up, and your org is there

    Every GreenMind account comes with an org. Name it for your studio and invite your team as its admins.

  2. Add a project

    One per game. It starts with a production and a test environment, each with its own data.

  3. Connect your game

    Give your game server a key, sign your players in, and read config, flags and lobbies from one API.

Test first, then release

Each environment is its own app, with its own players, keys and config, so you can build against something that is not live. Change values without a new build, and move them to production when you are ready, on your own or together in a release.

  • Releases

    Gather changes from test into a release, and production takes them all at once when a person releases it.

  • History

    Every change to every environment is kept, with who made it and the note they left.

  • Your own backend too

    Connect your game's own backend, and its config tables are compared and promoted in the same console as the platform's.

When a game is live

Live figures, trends over any range, and a heat map of where players died, drawn over a picture of your map.

The console's heat map for a production environment: deaths over the last thirty days drawn as cells over a picture of a harbour map, with filters for players and builds.
The heat map: where players died, over the map they died on.
  • Crash reports

    Unreal's crash reporter sends to the platform, per environment, so a crash can be read and triaged in the console.

  • Players and support

    Look a player up, and answer the support requests players send from your game.

  • Limits you can see

    Your plan's limits, and what each environment has used against them, are on the console's Usage page.

Before you sign up

  • An org comes with every account

    Rename it for your studio from your GreenMind account, or sign up with your studio's email address so the org is not tied to anybody's own account.

  • More orgs are for supporters

    One org is all a studio needs. Making more, for a second studio or a side project, is for supporters of GreenMind, who keep them if their support ends.

  • Plans and licences on request

    Every org starts on the Free plan. Ask for a higher plan or a GmCommon licence from the console, and your request reaches us with your usage attached.

How it works with the rest

It works on its own. These connections are there when you want them, and each is something you turn on.

Game Designer
Parameters and catalogues bound to a project's config are changed in the design, and show in the console as managed by that game.
GreenMind Marketing
A brand that markets the project sees its builds, config releases and crash fixes, and reads its store reports.
Your AI assistant
Config and crash reports each have an MCP server. An assistant connects by signing in with GreenMind, and can change a test environment directly, or queue a change to production in a release for a person to release.

How to get it

Our review
Anybody can sign up and make a project. GreenMind reviews every new project before it can use the platform. Until then nothing reaches players, though you can still set it up.
Plans
Every org starts on the Free plan, sized for building and testing a game with a small group. Ask for a higher plan from the console, and your request reaches us with your usage attached.
Unreal Engine plugins
GmPlatform is free to anybody signed in. GmCommon is licensed per org: ask for a licence on the org's page in the console. Both are compiled for Windows and Linux and downloaded from the console's Downloads page.
Agreements
An admin of the org accepts the Publisher Terms, the Data Processing Addendum and the Acceptable Use Policy with its first project.

Screenshots on this page show made-up sample data.

Build against test today

Make a project and set it up while we review it. It starts with a test environment of its own, so nothing you try there touches production.