BrightStar is built on a modern serverless architecture optimized for high-availability event ticketing. This document provides a technical overview of the system components, data flow, and integration points.
Seeker / Creatorbrowser
Next.js on VercelApp Router · SSR
SupabasePostgres · Auth · RLS
Stripe · Brevo · Muxpayments · email · video
Core System Components
Frontend Layer
•Next.js 14 with App Router
•Server-side rendering for SEO optimization
•Edge-cached static pages (< 50ms TTFB)
•Progressive Web App capabilities
API Layer
•RESTful API with JSON responses
•Rate limiting: 100 requests/minute (authenticated)
•Response time SLA: < 200ms (p95)
Database Layer
•PostgreSQL with read replicas
•Real-time subscriptions via Supabase
•Automatic daily backups with 30-day retention
Payment Processing
•Stripe Connect (Standard & Express)
•PCI DSS Level 1 compliant
•Real-time webhook processing
Data Flow Architecture
Ticket Purchase Flow
1. Customer selects tickets → Client validates availability 2. Checkout initiated → Server reserves tickets (5-minute hold) 3. Payment processed → Stripe webhook confirms 4. Order created → Email dispatched via SendGrid 5. QR codes generated → Cached at edge for scanning
Real-time Updates All dashboard data uses WebSocket connections for live updates. Sales, check-ins, and capacity changes reflect within 500ms across all connected clients.
Event createddashboard
StoredSupabase
Renderedserver-side
DiscoverableSEO + AI search
Infrastructure Specifications
Hosting
•Vercel Edge Network (global CDN)
•99.99% uptime SLA
•Auto-scaling to 10,000+ concurrent users
Security
•TLS 1.3 encryption in transit
•AES-256 encryption at rest
•SOC 2 Type II compliant
•GDPR compliant data handling
Performance Targets
•Event page load: < 1.5s (LCP)
•Checkout completion: < 3s
•Scanner response: < 100ms
For high-volume events (5,000+ tickets), contact support 48 hours in advance to ensure optimal infrastructure scaling.