Aeion BaaS for Social Gaming

Social-driven games — MMOs, life-sim, social-deduction, friend-co-op — live and die by their social fabric. Aeion ships the full social surface natively: chat channels (global / regional / guild / friend), a guild system for clans + ranks + applications, guild wars for competitive guild-vs-guild events, voice rooms, safe player-to-player trading with escrow, an auction-house marketplace, and an in-game inbox.

The Social Stack

A social-heavy game's backend has specific shapes:

Friend Graph via the Chat Channel System

Aeion models the friend graph + chat hierarchy on top of its chat channel data model.

Guild System

Aeion's guild system handles the full guild lifecycle.

Guild Wars

Competitive guild-vs-guild events drive retention + social cohesion. Aeion's guild war engine:

Player Trading with Escrow

Item trading between players requires safety primitives — escrow, trade window, anti-scam.

Player Marketplace (Auction House)

Asynchronous player-to-player listings. Aeion's marketplace engine:

FAQ

Aeion's friend graph data model is built on Postgres + Redis caching and scales the way relational graphs generally do — through partitioning and indexing as row counts grow. We haven't published a specific tested-scale benchmark for this; talk to your Enterprise TAM about sizing for your expected user + friend-count scale.

Yes — friend graph is global, but match-making prefers same-region. Friends can play together across regions (with the network latency cost).

Yes — Aeion's voice chat system creates a persistent voice room per guild (or party); members can drop in. Quiet by default (no auto-join); members tap to join.

Anti-cheat rules flag: high-value trades to brand-new accounts, rapid trades to same partner, currency flow patterns matching known RMT vendors. Banned via the ban management pipeline.

Aeion's friend graph is global — works across server-shard architectures. Match-making + game-server-affinity is configurable per-game-mode.

Aeion doesn't ship an age-gated DM-disable default today — if your game serves under-13 players, age-gating DMs and other COPPA-relevant chat controls is something you'd build using Aeion's chat-channel permission model (Aeion doesn't know a user's age unless you capture it).

The appeals queue covers ban appeals; a similar pattern for in-game reports (chat abuse, harassment) — operator-configurable. Aeion ships the data model; moderation workflow is operator-customized.

Social-driven games on first-class social primitives.