# Architecture

The control plane is split into stateless web/API processes, a BullMQ worker,
MySQL as the source of truth and Redis for queues and horizontal realtime scaling.
Organization membership is the tenant boundary. Game-specific behavior enters
through versioned contracts; FiveM uses protocol v1.

Requests receive correlation IDs and structured redacted logs. Current state lives
on `Server`; raw server events have a retention window and are not used as an
unbounded metrics store.