Profbot Betting System

Overview

I built Profbot for an esports company that needed tournament ops and sponsor betting in one place. Admins create tournaments and attach games. Sponsors place bets on players. Event state is supposed to move with the night — schedule changes, new bets, results — instead of a spreadsheet plus a group chat.

This is operations software for a live competitive scene. The Keystatic stack for this project is PHP and MySQL with an HTML/CSS/JS UI. The original article also described a Node/WebSocket approach for the live layer; I treat that as the real-time requirement, not a second product.

Problem

Brackets, games, and sponsor money drift when they live in disconnected tools. Odds, payouts, and “who is in this match” stop matching. Organisers needed one admin surface for the night and a sponsor surface that could bet without calling the TO.

What I built

Administrators define a tournament (name, date, teams, rules) and add games with player and rule detail. Sponsors see player/game context and place bets during the event. Updates and notifications were a first-class requirement so a result or a new wager is not discovered ten minutes late.

I structured the UI for organisers first: create, attach games, watch betting activity. Persistence and server logic sit on the PHP/MySQL stack recorded here.

Impact

It is a domain-specific ops tool, not a generic “bets” tutorial. It sits next to the earlier school Esport Club Management system as a more commercial betting layer. I do not publish handle, payout, or user counts.

Key features

• Admin tournament creation and configuration
• Per-tournament game and player records
• Sponsor betting on players during events
• Real-time-style updates for schedule, bets, and results
• Organiser-first admin UI

Technologies

HTML, CSS, JavaScript, PHP, and MySQL.

My role

Full-stack builder for the esports company’s event and betting workflow.