Platform

Platform is where the bdr team runs the platform as a whole. Only platform admins see Platform in the top bar. Anyone else who opens it is sent back to the home page with "That page is for platform admins."

The platform pages

A tab bar ties the admin's pages together:

Statistics

Recorded every ten minutes. The top row is now: drivers on the platform's pool servers, drivers signed up (and how many more are known from result files, without an account), races (and pickup races on open servers), laps and communities.

• Drivers online counts the drivers on every server a machine's agent runs, the platform's and the communities'. Servers a community runs by hand are not in it.
• The chart shows each period's median as a line, and its quietest to busiest minute as a band. Pick 24 hours, 7 days, 30 days or All; the longer periods put the ten-minute records together into hours or days.
• The small charts below show how the other figures grew. They start on the day statistics were switched on; drivers online goes back 45 days before that.

Health

Four tiles at the top. A tile that needs you is highlighted.

Waiting for you

Stewarding counts what waits on the steward desk: Official races, Appeals, Contact patterns, Flagged sessions and Waiting in communities. Next to Waiting in communities it shows how many reports have waited 3 days or more. Steward desk opens the desk.

Ranked status requests lists the communities waiting for an answer, with how long ago they asked. Select one, or Review, to decide it on the Communities tab. If there is none, it says No request waiting.

Machines, jobs and notifications

• Machines lists up to eight machines, those in trouble first, with who operates them (Platform fleet or the community), how many race servers are running, and a badge: Online, Offline or … failing. All machines opens the full list.
• Failed jobs · last 24 h groups failed jobs by name, with how often each failed, when it last did, and its last error. … gave up means that many will not be tried again; the others are retried on their own. Jobs that succeeded after failing are not listed. If there is nothing, it says Nothing failed.
• Notifications says whether platform alerts reach the platform's Discord webhook. Without one, machine alerts and ranked status requests reach nobody but this page. When messages failed, it shows how many and the last error.

Running the platform's own events

Platform events and leagues run in a community like any other: BDR Official, which bdr creates by itself when there is no official community yet. Nobody owns it and nobody has to join it; every platform admin finds it on Organise and runs it like its own. Another community can be made official as well, by setting its level to Official on the Communities tab. An official community:

• runs ranked races, like a ranked one;
• has its races and open servers on the platform's own machines, without a limit. Every other community runs on machines it registered itself, unless it was given a grant (below). For its series, choose Machines running the host agent as Servers;
• has no machines of its own: its page lists the platform's machines, and Register a machine there adds one to the platform fleet;
• has its reports decided by the platform's stewards directly, under Official races on the Steward desk. There is no appeal.

Platform machines for a community

A community other than the official one can be given free use of the platform's machines, for example a partner community without machines of its own. On the Communities tab, select Grant in its Platform machines column and set:

The column then shows what is used, for example 1/1 lobbies · 0/1 seasons · 30 per race · until 31 Dec 2026. Select it to change the grant or Revoke it. The community sees its grant on its page, and a booking that does not fit tells it why. Its own machines are used first, if it has any. The platform's Balance of Performance sets stay the official community's, and its races stay unranked unless it becomes ranked.