SlateCourt - Badminton Venues & Games

Find a court. Remember the good ones. Settle up after.

Most venues have no booking API, so Slate never pretends to book for you — it shows what is genuinely open, sends you to the venue to book, then turns the game itself into the product: who came, what it cost, who has paid, what gear was used. Bilingual (en/zh), installable, and gated behind personal invite codes.

Stack: Next.js 16
TypeScript
FastAPI
Python
PostgreSQL
Redis
Better-Auth
Cloudflare Workers
Docker
Category: Full-stack

Why This Exists

A real product for a real circle

Soft launch, real users

Built for my own Sydney badminton circle: sign-up is invite-gated, every member mints a personal invite code, and the social layer — friends, groups, game-invite links — grew out of how we actually organise play each week.

Honest data

No fake "live" promises. Court availability shows only where a venue's own booking system can actually be read — 16 of 54 venues today — and the rest stay an honest directory with one-tap redirect-out booking.

Personal Use Only

Demo · Invite-only

SlateCourt is a personal, non-commercial demo built for my own playing circle — registration requires an invite code. The availability feature reads only the public, log-in-free booking pages the venues themselves publish, at a low, cached cadence, and every result links back to the venue's own booking site. No venue data is republished or sold, and the project is not affiliated with any venue or booking provider.

At a Glance

By the numbers

Venues: 54
Live-availability Venues: 16
API Endpoints: 91
DB Migrations: 26
Notification Types: 11
Languages: 2

Across the Stack

Seven dimensions

FE Frontend: PWA & interface
Next.js 16
TypeScript
TanStack Query v5
openapi-fetch types
Tailwind + shadcn/ui
PWA · offline
BE Backend: Typed API
FastAPI
Python 3.14
SQLAlchemy 2.0 async
Pydantic v2
91 endpoints
DB Data: Persistence & cache
PostgreSQL 18
Alembic · 26 migrations
Redis 7
UUIDv7 + audit columns
ID Auth: Invite-gated
Better-Auth
passkey + magic link
email + password
JWT verified by FastAPI
LV Availability: Scrape pipeline
Cloudflare Worker
2 platform adapters
APScheduler hot/warm
Redis slot grids
QA Testing: Quality gates
pytest · 84 files
mypy + ruff
Playwright E2E
Alembic drift check
OPS DevOps: The layer that ships everything
Docker
Dokploy
Traefik
Postgres 18
Redis 7
GitHub Actions
ruff
mypy
pytest
typecheck
build
deploy

See It Live

Desktop · Mobile

Slate sign-in — "Find a court. Remember the good ones. Settle up after." — Desktop — invite-only sign-in

A logged game in the ledger: four attendees, costs split evenly, everyone settled — Mobile — game ledger & bill split

How Live Availability Works

Scrape pipeline

Most venues publish no API, but their public booking pages render date-parameterised HTML any visitor can open. Adding a venue is configuration, not code.

Venue config(platform, base_url, id) — config, not code

Worker fetchPublic, log-in-free pages · cached

AdaptersYEPbooking · SportLogic HTML parsing

NormaliseSlot grids per court, per day

ScheduleAPScheduler · hot/warm tiers

CacheRedis grids with TTL

ServeFastAPI availability endpoints

DiscoverLive badge + open-at-your-times filter

Trade-offs

Decisions that held

A game ledger, not a booking engine

Most venues have no public booking API, so Slate never fakes in-app booking. You book through the venue; Slate records the game — who came, what it cost, who has paid. The record and the bill split are the retention loop.

Next.js + FastAPI split monorepo

SQLAlchemy 2.0 async exposes every Postgres feature the data model wants; FastAPI auto-emits OpenAPI, and openapi-typescript keeps the frontend contract typed end to end with zero hand-written API types.

Better-Auth up front, JWT verified behind

Best-in-class passkey UX for free in Next.js; FastAPI trusts a shared-secret JWT through one small dependency. Same-domain routing via Traefik means cookies just work — no CORS, no domain juggling.

Reading public pages via a Cloudflare Worker

The venues' booking pages are anonymous, date-parameterised HTML — no log-ins bypassed, no headless browser. A lightweight Worker reads them at a low, cached cadence for personal use, keeping the 8 GB origin box light.

Live site

Want the full walkthrough?

Happy to talk through the architecture, the decisions, and the trade-offs behind this build.

Visit project →Get in touch