Publishing on the Playground
Two ways in, one review. Whatever you choose, a person looks at your game before it goes live.
Two ways in
From the Studio
Press “Publish on AikaHub”, fill in the game’s page, send it in. We host it for you on its own address: g-<name>.aikahub.dev.
From your own hosting
Your game lives on your own https address. In the Developer console you accept the agreement, create a client, add your testers, fill in the Playground page and send it in.
Review and updates
While you are developing, only you and up to 5 testers can log in to your game. Achievements and scores are test-only then (no XP, only you and your testers see them).
After you send it in, we try the game on a private, short-lived address. Unreviewed code never runs on the game’s real address.
Approved: the game is on the Playground, and its achievements and leaderboards go live.
An update is reviewed the same way; the current version keeps running until then.
Limits for games hosted by AikaHub
- Whole game
- 25 MB
- Number of files
- 600
- One file
- 16 MB
- HTML pages
- 100
- File types
.html .js .css .json .png .webp .jpg .svg .mp3 .ogg .wav .glb .vrm .txt .md .woff2 .woff .ttf .otf .wasm .ktx2 .hdr .bin- Never uploaded (folders)
server/tools/mock-hub/node_modules/__aikahub/__studio/- Achievements
- up to 50 per game; unlocked from the browser: at most 50 XP each, 450 XP together; the valuable ones (up to 250 XP, legendary) only from your own server
The security policy of a published game
- No inline <script> blocks: put your code into .js files. The one exception is the import map, allowed by its exact hash.
- Inline event handlers (onclick="…") do not run. Use addEventListener.
- No scripts, styles or fonts from other sites. Copy libraries into your game (pinned versions).
- Your game can connect only to itself and to aikahub.com.
- No service worker, no cookies. Saves go to localStorage or AikaHub cloud saves.
- Only AikaHub may show your game in a frame.
Every page of a published game gets exactly this Content-Security-Policy (the Studio preview uses the same one, so what works there works on the Playground):
Content-Security-Policy:
default-src 'self';
script-src 'self' 'wasm-unsafe-eval' blob:;
style-src 'self' 'unsafe-inline';
img-src 'self' data: blob: https://aikahub.com;
media-src 'self' data: blob:;
font-src 'self' data:;
connect-src 'self' https://aikahub.com;
worker-src 'self' blob:;
object-src 'none';
base-uri 'self';
form-action 'self' https://aikahub.com;
frame-ancestors 'self' https://aikahub.comOn your own hosting
Your own site, your own rules — but tokens stay in memory, the server key only on your server, and redirect addresses must match exactly. Details in the docs.