# Use the SpawnKit dashboard

Find your games, upload a browser build, inspect deployments and logs, and navigate project management in the SpawnKit dashboard.

The dashboard manages your hosted games. Your editor or AI agent remains where you change and build your game source.

<a id="start"></a>

## Sign in and find your project

1. Open [Dashboard](https://spawnkit.cloud/dashboard) and sign in with the account that owns or can access the game.
2. Choose your project from the project list. Confirm its name and game URL before making changes.
3. Use the project's navigation to open Overview, Deployments, Logs, Domains, or Settings.

If a game is missing, check the signed-in account and project access. Downloading a kit does not create a hosted project. Local game development needs no account; dashboard operations use your authenticated access.

<a id="create"></a>

## Create locally or upload a finished game

Use the [starter builder](https://spawnkit.cloud/templates) to choose an engine and tools and download source for local development. Use [Upload game](https://spawnkit.cloud/dashboard/upload) when you already have a working browser build. These are different starting points: a source kit is editable code; an upload is a built release.

Follow [Upload an existing game](https://spawnkit.cloud/docs/upload-existing-game) for packaging, listing details, media, deployment progress, and the final live check. No platform repository checkout is needed.

<a id="deployments"></a>

## Read deployment progress and releases

1. Open Deployments for the selected project.
2. Inspect the environment and release before taking an action. A build in progress is not yet a successful live release.
3. Open a release, then choose Build logs to inspect its output. Use Copy version ID in its details when sharing the release ID; deployment IDs and release IDs serve different purposes.
4. When the deployment succeeds, open Overview and use Copy production URL, or open the hostname link. Paste that URL into a new browser tab and verify gameplay.

Look for the first failure in build output and any media warnings. A warning about an omitted cover or trailer differs from a failed game build. Use available environment and release filters to find the run you intended; do not confuse an older successful release with the latest attempt.

Promotion and rollback depend on the project's environment, retained releases, permissions, and enabled capabilities. Review the displayed action and target before confirming. Rollback restores compatible artifacts, not database history.

<a id="navigation"></a>

## Know where to look

| Area | Use it for |
| --- | --- |
| Overview | Orient yourself in the selected project and its current activity. |
| Deployments | Inspect releases, environments, and deployment activity. |
| Logs | Inspect available project logs; use the release's build output for a build failure. |
| Domains | Inspect which hostname points to each environment before sharing it. |
| Analytics | Review recorded activity; empty data is not proof that loading is broken. |
| Settings | In General, read the Project ID and use Copy project ID. Project name is the dashboard label. |
| Users / Backend | These areas require the relevant configured game services. They are not required for a static browser upload. |

Some controls depend on account permissions, the selected plan, and backend availability. An unavailable or preview control does not complete a hosted operation. Read the result shown by the dashboard and verify the resulting project state.

<a id="help"></a>

## Recover from a failed operation

Record the project, environment, deployment ID, and the first relevant error. Check [Testing and debugging](https://spawnkit.cloud/docs/testing#diagnosis) for asset and build problems, or [Accounts and access](https://spawnkit.cloud/docs/authentication) for sign-in problems. If the dashboard cannot perform the operation you need, contact [support](https://spawnkit.cloud/contact#support) with those details, excluding credentials.