Case study
Creator Control Room
A realtime analytics dashboard for tracking Twitch creator events such as gifts, followers, and subscriptions.
Context
Overview
Creator Control Room helps teams monitor live Twitch activity across signed-on creators. The frontend receives realtime events while the backend fans updates out to tenant rooms with PostgreSQL as the operational store.
At a glance
Product
A realtime analytics dashboard for tracking Twitch creator events such as gifts, followers, and subscriptions.
Audience / need
Creator teams need a live view of gifts, follows, and subscriptions without stitching together multiple dashboards.
Ownership
Built a Next.js frontend with Socket.io client updates
Context
The problem
- Live creator operations data is hard to monitor across multiple channels in one place.
Approach
The solution
- A Socket.io-backed dashboard with Express APIs, Redis adapter support for scale-out, and PostgreSQL event storage.
Role
What I owned
- Built a Next.js frontend with Socket.io client updates
- Implemented Express and Socket.io backend patterns for creator rooms
- Modeled company, creator, member, and event relationships in PostgreSQL
Product
Core product flow
- Realtime event feed for gifts, followers, and subscriptions
- Creator filtering and interactive dashboard views
- Twitch authentication sign-on
- Tenant-aware event fan-out with Socket.io rooms
System
Architecture
High-level system pieces involved in the product.
- 01
Next.js frontend with Socket.io client
- 02
Node.js Express REST API and Socket.io server
- 03
Redis adapter for multi-instance event broadcast
- 04
PostgreSQL operational store with tenant isolation considerations
- 05
Object storage for brand assets
Engineering
Important decisions
Constraints
Challenges and trade-offs
Tools
Technology stack
- Frontend
- TypeScript · React · Next.js
- Backend
- Node.js · Express · Docker · AWS S3
- Data
- PostgreSQL · Redis
- Other
- Socket.io
Visuals
Additional screenshots
