Original Contear Guide Development · Official API

Build a Brawl Stars website that keeps the token secret.

Go from one useful idea to a secure backend, connected domain and trustworthy launch—without pretending the frontend can safely hide an API key.

Start with the idea ↓Official developer portal ↗

8 practical sectionsBeginner → intermediateNo framework required

OutcomeA secure launch blueprint

What you chooseStack, hosting and domain

What you protectAPI token and user trust

Brawlytix homepage with its player-tag search

Explore the live project ↗

OWNED BY PINEAPPLE + CHOSEN

Meet Brawlytix.

A Brawl Stars analytics project owned by Pineapple and Chosen. It brings player profiles, meta research and leaderboards into one place.

Use it as inspiration: pick a question players actually ask, make the answer easy to find, and build from there.

Player profilesMeta researchLeaderboards

Visit Brawlytix ↗

Section 1 of 8

Choose what to build

Start with one useful feature and a clearly defined visitor.

✓
Player profile viewer
✓
Club tracker
✓
Leaderboards
✓
Match history viewer
✓
Brawler statistics
✓
Meta tracker
✓
Reward tracker
✓
Tournament website
✓
Creator-code landing page

Section 2 of 8

Get access to the Brawl Stars API

Create a developer account at the official portal, create an API key and configure its allowed public IP address.

✓
Sign in at developer.brawlstars.com
✓
Create a descriptive key
✓
Add the public IP used by your backend
✓
Test a small player or club request
✓
Handle rate limits and API errors

Open official developer portal ↗

Section 3 of 8

Protect the API token

Recommended request path

Website frontend
→ Your backend or API proxy
→ Official Brawl Stars API

Section 4 of 8

Choose a technology stack

Pick the simplest path that matches what you already understand.

Beginner

✓
HTML, CSS and JavaScript
✓
Small serverless backend

Python option

✓
Python with Flask or FastAPI
✓
React or static frontend

Database options

✓
Firebase
✓
Supabase or PostgreSQL
✓
Cloudflare D1
✓
No database for simple projects

Section 5 of 8

Buy and connect a domain

Choose a short, memorable name that does not imply official Supercell ownership.

✓
Compare .com with suitable alternatives
✓
Configure root-domain and www DNS records
✓
Enable HTTPS
✓
Use domain privacy when available
✓
Keep registrar recovery details secure

Section 6 of 8

Choose hosting

Match the hosting model to the application rather than choosing the most complicated platform.

Static website

✓
Cloudflare Pages
✓
Netlify
✓
Firebase Hosting

Serverless API

✓
Cloudflare Workers
✓
Vercel Functions

Persistent backend

✓
VPS with Nginx
✓
PythonAnywhere for suitable Python projects

Database-heavy application

✓
Managed PostgreSQL
✓
Supabase
✓
Firebase
✓
Cloudflare D1

Section 7 of 8

Add essential pages

Trust and transparency are product features.

✓
About
✓
Contact
✓
Privacy Policy
✓
Terms
✓
Fan-content disclaimer
✓
Affiliate disclosure
✓
Data attribution
✓
Error and maintenance pages

Section 8 of 8

Launch and grow

Make the first release measurable, discoverable and recoverable.

✓
Google Analytics
✓
Google Search Console
✓
Sitemap and robots.txt
✓
Metadata and Open Graph images
✓
Mobile optimisation
✓
Performance monitoring
✓
Social sharing
✓
Uptime monitoring
✓
Backups