Koloboard
A platform for conducting CS2 tournaments, managing matches, rosters, HUDs, overlays, and replay scenarios.
CS2 Tournament Production Platform
The idea was born after the first 2025 ZOFK tournaments, when it became clear that small organizers pay with time, nerves, or money for basic things: brackets, team rosters, match data, HUD, and broadcast overlays.
Market Problem
Free solutions often cover only one part of the process: the bracket, overlay, or team table. For a real tournament, this is not enough. The organizer needs a system that keeps the live match, roster preparation, visual broadcast, data import, and technical diagnostics in a single loop.
- Disjointed services create extra manual steps before going live
- Paid tools quickly become expensive for local tournaments
- Free alternatives often lack a normal CS2 production workflow
Who Koloboard was created for
- Local esports federations and clubs
- Tournament administrators who need to set up matches quickly
- Broadcast directors working with HUD, overlay, and vMix
- Teams who want to have neat rosters, flags, avatars, and match data
Tournament OS
Tournaments, bracket scenarios, matches, vetoes, team rosters, and quick match start from a single interface.
Broadcast Layer
HUD manager, output/display logic, overlay windows, HUD reload, and control over what the viewer sees.
Live Data
CS2 GSI, dashboard, troubleshooting, local database, and live updates for solid production.
Replay Foundation
Two-PC architecture, pair-sync, Main/Delayed PC roles, vMix Instant Replay, and observer-control foundation.
How it was developed
The project evolved from a personal pain point to a full desktop platform. First, I addressed the most obvious needs: matches, HUDs, overlays, and GSI setup. Then the system began to grow towards production features: tournament brackets, export for vMix, replay scenarios, accounts, subscriptions, and cloud synchronization.
- 01
Interface prototype for quick match management
- 02
Redesign of the HUD/overlay workflow for real broadcasts
- 03
Local SQLite model for offline operation
- 04
Firebase layer for accounts, entitlement, and synchronization
- 05
Replay-domain as a separate direction, not a set of hacks on top of vMix
Product Idea
Koloboard's free features should be stronger than free analogues, and paid features should be more affordable than competitors. This is not about putting basic things behind a paywall, but about an honest path: giving small tournaments a working start and monetizing advanced production features.