This section explains what runs underneath the panel, for curious members and for developers. What each number means is in Metrics and data.
The platform in one picture
How the platform is built
The panel, the API, the collector, the assistant and the website; Postgres and Redis; how a request flows; where it is hosted.
The main tables, what each holds, which history can never be rebuilt, and how the schema changes.
How the API is organised, its Redis read cache and how new data invalidates it, rate limits and errors.
CI checks, release images, the deployment pull request, Argo CD, the homelab and backups.
Collection and background work
The collector's jobs and schedules, what happens when Roblox is slow or down, and the Collector page.
Why requests to Roblox are limited, how the budget is shared, and what opening an untracked game costs.
Every worker job, its schedule, lock, retries and the run log.
The assistant, notifications and security
What it can read, how it finds answers in this handbook, its limits and what it never does.
The studio's own GPU server: the model, its speed, how many questions at once, privacy.
Every kind of notification and its rule, preferences, and phone push through the Home Screen app.
Sign-in, sessions, roles, what is stored, how keys are kept, and the audit log.
Authentication and permissions
GitHub sign-in, sessions, roles, membership checks, the assistant's assertion and game keys.
Updated