Badasha Ticketing Platform (Contract) · 🇮🇳 · February 2026 - Present
Badasha Ticketing Platform (Contract): A Seat Map Built for a Touring Show
Full-stack developer — frontend, backend, and data modelType
Contract
Location
Remote
Duration
February 2026 - Present
The Brief
Since February 2026, Ayush Jhunjhunwala has been building a custom event ticketing website for Badasha, a touring magic and illusion show. Instead of paying per-ticket commission to a marketplace ticketing platform, the production gets its own online ticket booking system: an interactive seat map where the audience picks exact seats, a timed checkout flow, and an admin wizard for managing shows and multi-city tour schedules — all on a SvelteKit frontend with a FastAPI and PostgreSQL backend.
What I Built
- → Interactive seat map — the audience selects exact seats, not just a quantity
- → Five-minute booking session timer that holds selected seats during checkout
- → Four-step checkout flow from seat selection to confirmation
- → Admin wizard for creating shows, runs, and multi-city tour schedules
- → Booking history and role-based access for audience and admin accounts
- → FastAPI + PostgreSQL backend with versioned Alembic schema migrations
- → Soft-delete data integrity — shows and bookings are archived, never destroyed
Technical Highlight
A Seat Map Built for a Touring Show
Most ticketing tools assume one fixed venue. Badasha tours — the same production plays different cities on different dates. The platform models this as shows, runs, and time slots, so each city gets its own schedule while the seat map and checkout pipeline stay identical. During checkout, selected seats are held for five minutes with a visible session timer, preventing the classic double-booking race where two buyers grab the same seat. The data model enforces integrity end to end: every schema change ships as a versioned Alembic migration, and nothing is ever hard-deleted.
Outcome
The platform is in final backend integration ahead of public launch. For the production, the economics are the point: marketplace ticketing platforms take a commission on every ticket sold, while a custom-owned ticket booking system is a one-time build — the savings compound with every show on the tour.
FAQ
What is the Badasha ticketing platform?
Why build a custom ticketing system instead of using a ticketing marketplace?
How does the seat booking system prevent double bookings?
How much does it cost to develop a ticket booking system?
Working on something similar?
Let's build it together.
I'm available for contracts — local businesses, startups, and everything in between.
