How the platform works

The apps, data stores and background jobs behind the panel, how they stay inside Roblox's limits, and how sign-in, deployment, notifications and the assistant work.

Platform

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

The platform's parts. The collector reads Roblox, Rolimon's and GitHub on schedules and writes Postgres. The API reads Postgres, caches answers in Redis and serves the panel, which is the only door from the internet. The assistant app reads through the API as the person asking and calls the studio's own language model.

How the platform is built

  • Architecture

    The panel, the API, the collector, the assistant and the website; Postgres and Redis; how a request flows; where it is hosted.

  • Data model

    The main tables, what each holds, which history can never be rebuilt, and how the schema changes.

  • API and caching

    How the API is organised, its Redis read cache and how new data invalidates it, rate limits and errors.

  • Deployment and releases

    CI checks, release images, the deployment pull request, Argo CD, the homelab and backups.

Collection and background work

  • Collector and freshness

    The collector's jobs and schedules, what happens when Roblox is slow or down, and the Collector page.

  • The Roblox budget

    Why requests to Roblox are limited, how the budget is shared, and what opening an untracked game costs.

  • Jobs and queues

    Every worker job, its schedule, lock, retries and the run log.

The assistant, notifications and security

  • The assistant

    What it can read, how it finds answers in this handbook, its limits and what it never does.

  • AI infrastructure

    The studio's own GPU server: the model, its speed, how many questions at once, privacy.

  • Notifications and push

    Every kind of notification and its rule, preferences, and phone push through the Home Screen app.

  • Security and privacy

    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