> ## Documentation Index
> Fetch the complete documentation index at: https://docs.qwacks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Studios & Games

> The two top-level objects every Flock integration is built around.

## Studios

A **studio** is your team and tenant. It owns your games, members, billing, and plan. You create a
studio once in the [dashboard](https://flock-saas.qwacks.com); everything else lives under it. The studio
is resolved automatically from your game's credentials — you never deal with it in the SDK.

## Games

A **game** is the container for a single title's backend: its players, economy, configuration,
versions, and analytics. Each game has:

* **Credentials** — the API Key, Game ID, and Game Version you configure the SDK with.
* **A signing key** — Flock secures each game's player sessions with a per-game key, so a session
  for one game is never valid for another. The SDK uses this transparently.
* **Versions** — see [Versions](/concepts/versions).

<Card title="Create a game" icon="gamepad" href="https://flock-saas.qwacks.com">
  Studios and games are created in the dashboard. Grab the game's credentials from its settings.
</Card>

## How they fit together

```
Studio  ──owns──▶  Game  ──issues──▶  credentials  ──▶  configured in the SDK
                     │
                     └──secures──▶  player sessions (managed by the SDK)
```

Because the studio and game come from your credentials, integration stays simple: configure the SDK
once, sign a player in, and call into features.