Aeion BaaS Architecture
45 backend services, 70 collections, organized into 8 functional surfaces — matchmaking + match-lifecycle, virtual economy + inventory, anti-cheat + ban pipeline, battle pass + tournaments + achievements, social + guild system, voice + presence + push, cloud functions + live ops, GDPR + analytics. End-to-end flows from queue ticket through Glicko-2 matchmaking to match room broadcast to anti-cheat enforcement to currency settlement.
Module Inventory
Services (45)
by category — matchmaking (8), economy (7), anti-cheat (3), battle pass + tournaments (5), social + guild (5), voice + presence + push (6), functions + live ops (5), GDPR + analytics + other (6)
Collections (70)
by domain — matches + tickets + queues (10), currency + inventory (7), anti-cheat + bans (4), battle pass + tournaments + achievements (10), guild + chat (6), voice + presence + push (8), functions + remote config (6), live ops + alerts + analytics (8), GDPR + retention (4), other (7)
Provider adapters
voice (LiveKit — self-hosted/embedded or LiveKit Cloud/external; no Mediasoup or Agora adapter exists today), push (APNs / FCM / Web Push adapters)
Function runtime
Node `vm` sandbox (hard timeout + best-effort memory cap, minimal global surface) with dedicated deployment, execution, and event-trigger pipelines — full QuickJS WASM isolation is roadmapped, not yet implemented
Realtime broadcasting
Redis pub/sub powering match-room events and platform-wide broadcast channels
AI agents
built-in operational AI for development assistance, DevOps automation, and security monitoring (BaaS-specific)
Queue infrastructure
BullMQ-on-Redis for async job processing
Tests
extensive automated test coverage across the module
Service Map — 8 Functional Surfaces
`
End-to-End Match Lifecycle
Real flow from "player taps Play" to "match-end currency settlement."
Glicko-2 Implementation
Aeion implements Glicko-2 (the modern Elo replacement) directly. The key differences from naive Elo:
Cloud Function Execution Flow
`