Full buildDesign, engineering and infrastructure by Catanull

Openstats

A multi-game player lookup. Search any account and see rank, match history and per-hero stats, with tier lists and builds for Deadlock and League of Legends.

Game Stats PlatformNext.js • React • TypeScript • Tailwind CSS • PostgreSQL • Drizzle • Docker
Visit Project
Openstats Deadlock homepage with player search, live match, weekly match chart and hero of the week
Openstats Deadlock homepage with player search, live match, weekly match chart and hero of the week

What We Built & Why

Openstats is a stats site for competitive games. Type in any account and it shows the player's rank, match history and per-hero performance, next to tier lists and builds. Deadlock and League of Legends are live, and the site is built so more games can be added. We designed the interface, wrote the site and the sync worker behind it, and run the servers it lives on.

Stats sites tend to be slow, crowded with ads and split across one site per game. We wanted one fast place to look up a player, with the numbers that matter first.

Player Profile

Rank, record and win rate at the top, then most played heroes, recent matches, trends against teammates and a six-month activity map.

Openstats player profile with rank, record, most played heroes and match history
Openstats player profile with rank, record, most played heroes and match history

Match Page

Both teams side by side with every player's build, damage and souls, a map of the fight and a timeline you can play back.

Openstats match page with both teams, item builds, the map and a replay timeline
Openstats match page with both teams, item builds, the map and a replay timeline

Key Features

•Player search by account name or profile link
•Deadlock and League of Legends, with more games planned
•Share images and metadata for every page
•Rank, match history and per-hero stats for each player
•Live page with current streams
•Zero-downtime deploys
•Hero tier lists and builds
•Background worker that keeps match data up to date

The Problem

Every ranked match adds up: storing them grows the database by about 700 MB a day

Our Approach

A separate sync worker fills a PostgreSQL store, so pages read from our own database instead of waiting on a game API

Development Challenges & Solutions

Step Tracking Accuracy

Challenge

Every ranked match adds up: storing them grows the database by about 700 MB a day

Solution

A separate sync worker fills a PostgreSQL store, so pages read from our own database instead of waiting on a game API

Inclusive Competition Design

Challenge

Game APIs have strict rate limits that a busy lookup site hits quickly

Solution

Requests to game APIs are queued inside each key's rate limits, with a separate budget for background collection

Real-Time Synchronization

Challenge

Pages must stay fast while the data behind them changes every minute

Solution

Next.js Cache Components serve prerendered pages and refresh only the parts that changed

Privacy & Social Balance

Challenge

Deploying a new version must not interrupt players who are on the site

Solution

Rolling updates with a health check: the old version keeps serving until the new one is ready

Openstats Deadlock page background artwork of city rooftops
Openstats Deadlock page background artwork of city rooftops