BeatKhana, documented
BeatKhana brings tournament registration, map pooling, brackets, match coordination, TournamentAssistant, broadcast graphics, and public discovery into one platform. This wiki explains how those pieces fit together and which role owns each decision.
Platform status
These pages describe the public BeatKhana platform as of August 2026. Features explicitly marked work in progress should not be treated as production commitments.
Choose your path
Run a tournament
From TA setup and private draft to public visibility and the final match.
Coordinate matches
Prepare players, run picks and bans, record scores, replays, and results.
Build a broadcast
Create scenes, reusable components, browser sources, and desktop outputs.
Integrate the API
OAuth 2.0, typed REST resources, Socket.IO, MessagePack, and TA state.
Platform map
| Area | What it owns | Main users |
|---|---|---|
| Tournament management | Identity, lifecycle, registration, rules, pages, timeline, permissions | Organisers |
| Brackets and matches | Divisions, brackets, matches, advancement, declared winners | Head coordinators |
| Pooling | Suggestions, votes, flairs, pool slots, imports, publishing and archive | Head poolers, poolers |
| Coordination | Match selection, players, maps, picks/bans, TA state, score submission | Coordinators, referees |
| Hosting and casting | Stream assignment, broadcast credentials, match presentation | Stream hosts, casters |
| Dynamic overlay | Live documents, reusable components, scene renderer and outputs | Broadcast operators |
| Public site | Discovery, registration, brackets, qualifiers, teams, timeline | Players and viewers |
| Developer platform | OAuth applications, REST client, sockets, CDN and integration hooks | Developers |
Before you begin
An operational BeatKhana tournament normally needs:
- A BeatKhana tournament created as a private draft.
- A real TournamentAssistant tournament and server configuration when using live TA integration.
- At least one match flow before picks/bans or match progression can operate correctly.
- Staff roles and permissions assigned to the people running pooling, coordination, refereeing, casting and hosting.
- Divisions, brackets, matches and pools that agree with the published rules.
- A visibility request after the public identity, schedule, rules, registration and staff setup are ready for review.
Translation model
Each topic is an independent MDX file. To add a translation, copy a page to the locale naming convention (for example organisers.hu.mdx), translate prose without changing slugs or code, and add the locale to the Fumadocs i18n configuration. Navigation lives in content/docs/meta.json, so translators do not need to edit React components.