Quick start

Gamealia hosts web games (HTML5, Unity WebGL, Godot 4 web, GameMaker HTML5, Construct and other web exports) and shares the ad revenue they make with their developers. This page takes a game from your folder to a submitted version in five steps.

There are three ways to publish. They all end in the same review:

1. Create your developer profile

Sign in at /developers with Google, pick the name players will see and accept the developer terms. The CLI and the MCP sign in through the same page with a device code, so you never paste passwords or keys.

2. Add the SDK

Load the SDK in your index.html, before your game scripts:

<script src="https://gamealia.app/sdk/v1.js"></script>

Then call it from your game:

const { locale, user, device } = await Gamealia.init(); // first call, at startup
Gamealia.game.loadingStart();
// ... load your assets ...
Gamealia.game.loadingStop();   // required: the game is ready to play

// When real play starts and stops:
Gamealia.game.gameplayStart();
Gamealia.game.gameplayStop();

// At a natural break (game over, between levels):
await Gamealia.ad.requestMidgame();

Outside the portal the SDK runs a local mock (fake ads, a fake player, saves in localStorage), so you can develop and test without uploading anything. See the SDK reference.

Using Unity or Godot? Follow the Unity or Godot guide. Coming from CrazyGames or Poki? Swap one script tag: CrazyGames, Poki.

3. Test it locally

gamealia test (or the MCP tool gamealia_run_autotest) runs the same autotest the server runs: headless Chromium at desktop and mobile sizes, with screenshots. Fix every failing required check before uploading.

4. Create the listing and upload

Create the game page (slug, title, description, controls, tags, cover and thumbnail) in the developer portal or with gamealia_create_game. Then upload a build: a folder or zip with index.html at its root, at most 250 MB and 5000 files. The server runs the autotest again. See Game requirements.

5. Submit for review

When the version is tested, submit it. A person reviews every new game and every update before it goes live. If it is rejected, the reasons come with fixes: fix them, upload a new version and submit again. While a new version waits for review, the previous one stays live.

Next: Ads (how you earn), Revenue and payouts, FAQ.