Hey everyone! 👋 EventPass started from a real frustration. I was helping organize a multi-day tech conference, and the ticketing was a nightmare — attendees had to register for each session separately, ending up with 8–10 different QR codes. People showed up to the wrong room, lost tickets, and organizers had zero visibility into who actually attended what. Every ticketing platform out there (Eventbrite, Ticketmaster, etc.) treats events as flat, isolated things. None of them really understood that a festival or a congress is one experience made of many sessions. So I built EventPass around a "parent-child events" model. You create a festival as a parent, add its sessions as children, and the attendee picks what they want — but gets one single QR code that works across every session they bought. Organizers finally get unified attendance tracking: "Juan went to 8 of 12 talks." The process evolved a lot. My first version tried to generate one ticket per session — it worked but recreated the same multi-QR mess. The breakthrough was realizing the QR should represent access rights, not a single seat. That meant rebuilding the booking model around a manifest of sessions, plus solving the harder problems underneath: distributed locking to prevent overselling, HMAC-signed tickets, offline check-in, and a refund-reconciliation system for when Stripe and the DB disagree. It's now a full multi-tenant SaaS — any organizer can launch their own branded store. Built with NestJS, PostgreSQL and Redis, ~94% test coverage. Would love your feedback, especially from anyone who's organized a conference and felt this pain. What would you want from an ideal ticketing flow? 🙌

PrimeLane

Launch your own branded ticketing store.

Launch your own branded ticketing store.