G3XNSBR Platform
Web platform modernization for a long-running Counter-Strike: Source server. A public site with live player data, fast APIs and an admin back-office, rebuilt from a legacy stack that had become a security risk, all on free-tier infrastructure.
Overview
My role
Redesigned the database architecture so it keeps scaling Built the public site in React Wrote every API on Bun, tuned for minimal resource usage Reimagined the admin flows: bans and onboarding new admins
G3XNSBR is a Counter-Strike: Source server older than most of its players. Its website and admin panel had aged with it, to the point of becoming a security risk.
When CS2 replaced CS:GO, I moved to Counter-Strike: Source and found this community. I became one of the server admins: I join matches to help out and ban players who cheat. Seeing the admin tools from the inside made it clear they needed a rewrite.
Together with another developer who works on the game server itself, I rebuilt the web platform: a public site that brings together player data, who is playing right now and who stands out with each weapon; a set of APIs behind it; and a back-office where admins manage bans and onboard new admins.
The constraint that shaped every decision was money: the whole platform runs on free plans, so everything had to be fast and light enough to fit inside them.
The Challenge
The legacy website and admin panel were built on outdated patterns: slow, hard to maintain and exposed to security issues. Thousands of players a day depend on the server, and the new platform had to serve all of them without any paid infrastructure.
Legacy admin panel with security problems Outdated database architecture limiting growth Strict free-tier limits on compute and storage
The Process
The rebuild went piece by piece, keeping the game server untouched while everything around it was replaced.
- 01
Audit
Mapped the legacy site, admin panel and database, and listed the security and performance problems that had to go first.
- 02
Database Redesign
Remodeled the schema with Drizzle ORM on Supabase so player data, bans and admins have a structure that scales.
- 03
APIs & Public Site
Wrote the APIs on Bun and built the React site with live player data and weapon highlights.
- 04
Admin Back-office
Rebuilt the admin flows for bans and onboarding new admins, simpler and safer than the old panel.
The Solution
The public site was rebuilt in React with Vite, replacing the legacy pages with a fast, component-based app that shows live server data. Every API behind it runs on Bun, chosen because it is quick and light enough to fit the free plans the community can afford.
The database was remodeled on Supabase with Drizzle ORM, giving the whole data layer type safety. Admins got a dedicated back-office to manage bans and add new admins. Only the game server itself was kept from the legacy system.
Built with
The whole data layer became type-safe: no more hand-written SQL strings.
In the product
The public site players use every day.
The Results
A faster, safer platform for a community that plays every day, with no hosting bill.
The legacy web stack is gone. Players get live data and admins get a safer back-office, all running on free plans.
Every tool, and why
Every tool had to earn its place on a free-tier budget.
Frontend
2- React
- Component-based public site with live player data
- Vite
- Fast builds and a small production bundle
Backend
3- Bun
- Fast, lightweight runtime for every API
- Drizzle ORM
- Type-safe queries instead of raw SQL
- Supabase
- Managed Postgres that fits the free plan