Case study · Media and gaming
FanClash
Asia's largest fantasy esports platform.
- Client
- FanClash
- Service
- Design, development, platform architecture
- Sector
- Media and gaming
- Scale
- Thousands of active users
At a glance
What it handles
By its own positioning, across multiple esports titles.
Participating in tournaments, with peak traffic concentrated around major events.
Major esports events create spikes rather than growth curves, and the platform holds through them.
Security as a trust requirement in a category where regulatory scrutiny is constant.
The brief
Fantasy sport mechanics, esports audience, money in the middle
Fantasy esports sits at an awkward intersection. The mechanics come from fantasy sport, the audience and titles come from competitive gaming, and real money moves through the middle. At the time there were few platforms that were secure, usable and integrated with the titles people actually followed.
The third problem is the one that kills platforms in this category: regulatory uncertainty. Building something that scales while the rules around it are still moving means the architecture has to tolerate change it cannot predict.
Traffic here does not grow, it spikes. The architecture is sized for the tournament, not the average.
The build
Built for the spike
The load profile is the defining engineering fact. A major esports event concentrates most of a month's activity into a few hours, so the platform is sized for peaks it hits occasionally rather than a load it carries continuously. It handles that traffic during major events without degrading.
Security is the second pillar, and in this category it is commercial rather than technical. Two-factor authentication and encrypted transactions are what let the platform be described as trusted, which in a space under constant regulatory scrutiny is the asset.
Stack: Flutter for the apps, ReactJS on the web, Python behind it, MongoDB for data, AWS underneath, and AI-powered analytics on top.
What it does
Play, track, reward
Fantasy team creation
Drag-and-drop drafting of customised teams, which is the core loop and therefore the thing that has to feel effortless.
Live leaderboards
Real-time ranking that tracks performance as matches run, because a fantasy contest with delayed standings is a spreadsheet.
Rewards and multi-title
A points based reward system for engagement and tournament wins, across dynamic integration with multiple esports titles rather than a single game.
Stack
What it was built with
- Flutter
- ReactJS
- Python
- MongoDB
- AWS
- AI analytics
- 2FA
Questions
FanClash, answered
What is FanClash?
Asia's largest fantasy esports platform. Wow Labz handled design, development and platform architecture, covering fantasy team creation, live leaderboards, rewards and multi-title esports integration.
How does it handle major event traffic?
The architecture is built for spikes rather than steady load, because major esports events concentrate activity into a few hours. It handles peak traffic during those events without degrading.
How is money kept secure?
Two-factor authentication on accounts and encrypted transactions for financial processing, which is what underpins its positioning as a trusted platform in a category under regulatory scrutiny.
What is it built with?
Flutter, ReactJS, Python, MongoDB and AWS, with AI-powered analytics.
Keep reading
Related work
Let's talk
Got a developer product nobody finishes integrating?
Tell us what you are building. We will tell you how we would ship it.