Multi-tenant volleyball tournament platform with real-time brackets, capability-based permissions, drag-and-drop scheduling, and white-label branding.
What I Learned
Capability-based auth is worth the upfront complexity
Real-time needs to be core infrastructure, not an afterthought
AI agents can ship production code if you give them constraints
The Problem
Tournament management is fragmented across spreadsheets, emails, and outdated software. Directors need a modern platform for registration, scheduling, brackets, and scoring.
The Approach
Built the entire platform solo using AI coding agents with my AEGIS governance framework. Started with a comprehensive architecture document, then implemented features in parallel. Treated the AI as a team member that needed clear specs and guardrails.
Architecture Decisions
Capability-based permission system (not role-based)
Real-time bracket updates via WebSocket
Multi-tenant architecture with RLS
WCAG 2.1 AA compliance throughout
Why I Built It This Way
Chose capability-based permissions over RBAC for flexibility
Built real-time features from day one, not bolted on
Used Supabase for rapid iteration without DevOps overhead
Technology Stack
Next.js 15React 19TypeScriptSupabasePostgreSQLTailwind CSSRadix UIWebSocket
Outcomes
Production multi-tenant SaaS
Real-time tournament bracket management
Drag-and-drop scheduling
White-label branding for operators
Started: 2025-10
7 days initial, ongoing iteration