YourRank
Hosted leaderboards for streamers and communities. Prize pool, referral code and ranked players, all editable from one dashboard. The public page updates the instant you hit save.
Outcome
Self-serve SaaS: a streamer creates a leaderboard page in under a minute, no code, no hosting.
- Live in production at yourrank.site
- Self-serve onboarding: account → live page in under a minute
- Automatic standings via postbacks. Zero manual score entry.
- Save or postback → public page updates in under a second
Founder-built and self-funded, currently growing its user base. The figures above are measured technical launch metrics, not customer-revenue claims.
Real-time updates, billing and self-serve onboarding, running in production without support tickets. The unglamorous parts an MVP lives or dies on.
THE LIVE PRODUCT
A real screenshot captured from the live product, no mock UI. Click it to open the site itself and judge the real thing.
The problem
Streamers run prize races and referral contests out of spreadsheets and Discord screenshots. Numbers go stale within hours, players dispute standings, and every update means editing an image or re-posting a wall of text. Existing leaderboard tools wanted a developer, a deploy, or both.
What I built
A hosted page per streamer, yourrank.site/you, driven entirely from a dashboard. Prize pool, countdown and ranked players are editable fields, not code. A signed postback API lets any backend, Google Sheet or external feed push scores in, so standings update themselves. Free tier forever, Pro adds custom domains, an OBS overlay, and Discord/Telegram notifications, billed in crypto.
How it went
Shipped UI
No staged wireframes here: this is the actual product as it runs today, captured from production.
- One accent color (#7c5cff) doing all the signaling work
- Real empty, error and loading states designed before the happy path
- Type and spacing tokens shared between marketing and product surfaces
Engineering details — architecture, APIs, data and stack
Architecture
- Multi-tenant public pages keyed by handle (yourrank.site/you), statically rendered for speed
- Postback ingestion endpoint with HMAC-signed score updates, source-agnostic by design
- Redis-backed standings cache: dashboard save or postback → public page updates instantly
- Per-plan feature gating (badge, domains, overlay, webhooks) enforced server-side
APIs
- Signed score postback API
- Discord webhooks
- Telegram notifications
- Crypto billing (BTC · ETH · USDT · 100+)
- CSV import/export
Database
Postgres: pages, players, score events, analytics rollups
Authentication
Session-based dashboard auth, scoped strictly to owned pages
Stack
Measured quality
Self-reported — how these were measured
I ran Lighthouse myself against the production builds. Your device, connection and Lighthouse version will move these numbers.
Performance
Public leaderboard pages are static-first: instant loads on stream chats and mobile.
SEO
Public pages ship full metadata and semantic HTML, so a streamer's page ranks for their name.
Accessibility
Standings are real tables, not div soup. Keyboard-navigable dashboard throughout.