Aeion BaaS vs Supabase — Game-Native Backend
Supabase is the modern Firebase alternative — Postgres + auth + realtime + storage + edge functions, polished developer experience. Aeion BaaS is purpose-built for games — Glicko-2 matchmaking with Rating Deviation tracking, double-entry virtual currency ledgers, sandboxed JS/TS serverless functions via QuickJS WASM, rule-based anti-cheat engine, battle passes, guild wars, tournaments, voice chat via WebRTC SFU adapters, push campaigns across APNs / FCM / Web Push. 45 services + 70 collections built around the game-backend operating model.
What Supabase Is — And Isn't
Supabase is genuinely great for what it is: a general-purpose backend platform with first-class Postgres + a polished developer experience. The pitch:
Where Supabase Wins
Honest assessment of Supabase's strengths:
The Game-Backend Argument
Games have specific backend requirements that general-purpose BaaS platforms don't address:
Migration FAQ
Yes — if you've crossed the "wait, we need matchmaking + economy" threshold. Supabase data migrates cleanly (Postgres → Postgres). Plan ~2-3 sprints for the auth + storage + functions migration; gaming primitives (matchmaking, currency, anti-cheat) you'd be building either way.
Aeion's function runtime runs QuickJS WASM (not Deno). Migration: extract function logic into Aeion's function-deploy schema; rewrite Deno-specific imports for QuickJS. Most function code (pure logic, fetch calls, JSON manipulation) ports without changes.
Yes, same Postgres. Aeion's collections are Postgres tables with conventions (tenantId column, ULID id, audit timestamps). Supabase tables migrate to Aeion collections; the wrapper service code (matchmaking, currency, anti-cheat) is new code.
Aeion's realtime layer provides similar subscribe-to-change semantics, but via Redis pub/sub triggered by application events (not Postgres replication). The trade: Aeion's broadcaster lets you broadcast custom events, not just row changes; Supabase broadcasts every row change automatically.
Aeion's admin UI at `/admin/baas` covers similar surface — players, matches, currencies, anti-cheat flags, function deployments. Less polished than Supabase Studio for raw table editing; more game-specific tooling for matchmaking + economy + live-ops dashboards.
Yes — Aeion's `/modules/files` supports S3 + GCS + Azure Blob + Cloudflare R2 + local. Migration: re-target the bucket, copy objects, swap the credential. Player avatars + game assets are typically S3 anyway.