Ravensight

One title, one project, one game per environment

Your development build and your shipped build must not share an event stream, or a week of debugging quietly becomes your retention number. Ravensight keeps them apart by making each one its own game, and groups the games of one title into a project.

The three scopes

ScopeWhat lives there
Environment, one game Its own ingest key, its own tracking and history switches, and its own events, sessions, players, funnels, journeys, retention, reports and digests. The presets are production, early access, demo, beta, alpha, staging and development, and a project can also name its own, such as qa. At most one game per label per project.
Project, one title Name and engine, the environments underneath it, and the studio records filed under it. Project-scoped pages read the project rather than one build.
Studio, your org Members and roles, billing and the prepaid balance, the studio context graph, studio notes, cross-game analytics and the audit log.

Picking one

The switcher at the top of the sidebar picks a project. Beside it in the header, on the pages whose numbers come from one build, an environment control picks which environment you are looking at. A project with a single environment needs no second choice, and the pages that belong to the whole project do not show the control at all.

The switcher also offers All games. Brainstorm, Strategy matrix, Design, Dashboards, Muninn, Marketing, Sales, Pulse, Publishers and Studio data follow the selection: one game shows that game's records, and All games shows every game's, along with records that have no game. There, each record can be moved to a game with Move to game. Every other page shows one game at a time and asks you to pick one under All games. This is a filter inside your studio, not a change in who can see what: every member still sees every game.

Managing them

Settings > Projects is where projects are renamed, merged, and given new environments. Because every existing game was migrated into a project of its own, two environments of the same title can start out as two projects. Ravensight proposes the merge when their names normalize to the same thing and their environment labels do not collide, and nothing is merged until you accept the proposal. Dismiss one and it stays dismissed. You can also move a single environment from one project to another, or delete a project once it is empty.

Creating, renaming, merging and deleting all need an admin role or above. Everyone in the studio can read the list.

Analytics queries are still keyed on one game, which is why a number on screen always belongs to exactly one environment. A project-level or studio-level number is the same per-game query asked of several games and summed, never a new aggregation with its own rules.