:Tixora — Event Ticketing Platform with Fraud Detection
A production-grade event ticketing system built end-to-end to handle real-world booking traffic, payments, and fraud — not just a CRUD demo.
What it does:
Tixora lets users browse events, book tickets, and manage bookings — while the backend handles the hard parts: preventing overselling under concurrent demand, processing payments reliably, and catching fraudulent activity before it becomes a problem.
Key engineering decisions:
⚙️ FastAPI + PostgreSQL (Supabase) for a scalable, type-safe backend
🔒 Redis distributed locking to guarantee no double-booking or overselling during high-traffic ticket drops
💳 Stripe integration with webhooks for real-time, reliable payment confirmation
⏱️ APScheduler to auto-expire abandoned/pending orders and free up inventory
🛡️ ML-based fraud detection (XGBoost/scikit-learn) to flag suspicious booking patterns
🎫 QR-code ticket generation for fast, secure check-in
🐳 Dockerized deployment on Railway
Why it matters:
Ticketing systems fail in production in specific, predictable ways — race conditions on popular events, payment/webhook mismatches, silent fraud. Tixora is built to handle these from day one rather than patch them after launch.
Then: 1 month, 1 template.
Now: 1 week, 15 templates.
Same designer, different workflow.
I wrote up how I built no-code.supply: fifteen website templates, each with its own brand, in HTML and React, and some in Framer too. Claude Code did most of the typing. I did the directing.