Supabase
Switched on automaticallyYour own Postgres database, logins, realtime, and storage. Checked and switched on automatically.
Your game reads it as RR.integrations.supabase. Supabase docs
Robot Recess Premium
Hook up your own Supabase or backend, mirror chat to Discord, bigger teams and uploads, and shiny flair.
Log in to see which plan you are on.
Premium is invite-only for now. There is nothing to pay. Ask an editor and they can switch it on for your account.
Free vs Premium
| What you get | Free Publish games, get playtested, climb the charts. | Premium Hook up your own Supabase or backend, mirror chat to Discord, bigger teams and uploads, and shiny flair. |
|---|---|---|
| Publish, playtesting, high scores, saves, the SDK | Included | Included |
| Mirror chat to your DiscordBug reports and ideas from your game's live chat show up in your own Discord server. | Not included | Included |
| Bigger teamsInvite up to 20 people to build with you in the Workshop (free accounts: 8). | Not included | Included |
| Connect your own SupabaseLogins, cloud data, and realtime from a Supabase project you own. Checked and switched on automatically. | Not included | Included |
| Connect your own backendLet your game call your own https API or websocket server (an editor approves it first). | Not included | Included |
| Premium flairA shiny badge next to your name. | Not included | Included |
| Biggest upload | 5 MB | 25 MB |
| Uploads per day | 10 | 50 |
| New games per day | 5 | 20 |
Integrations
Games on Robot Recess cannot reach the outside internet. With Premium, you can connect a service you own to a game, and only that service is let through.
Custom backend
An editor approves itYour own https API or websocket server (up to 5 origins). An editor approves it before it switches on.
Your game reads it as RR.integrations.custom.
More soon
Firebase, PocketBase, Convex… The integrations shelf is built to grow. Tell an editor what you need.
How it works
- Publish your game as usual (web form, MCP, or the CLI). If your code already talks to Supabase, we spot it.
- Open the game’s dashboard → Integrations, and connect (or click Connect it on what we found).
- Supabase is checked live and switched on right away; custom backends wait for a quick editor review.
- Your game reads the settings from
RR.integrationsand can call your service on the next load.
How integrations stay safe
- Public keys only. We accept Supabase publishable (or legacy anon) keys and refuse secret and service_role keys, which would let any player wipe your database. Uploads that contain a secret key are sent back.
- Turn on Row Level Security. Your publishable key is visible to every player, so your database rules are what protect your data. Enable RLS on every table and write policies for what players may do.
- Only your address is opened. A connected integration adds just your project’s address (https and wss) to that one game’s allow-list. Every other outside call stays blocked.
- Games stay sandboxed. Games run on their own domain with an opaque origin, so requests arrive with
Origin: nulland can never touch Robot Recess accounts or cookies. Your backend must allow that origin (Supabase already does). - Logins that work in the arcade. Email + password, one-time email codes, and anonymous sign-ins work. OAuth popups and redirects (Google, GitHub, Discord…) do not work inside the game frame.