// the find
HiEventsDev/Hi.Events
Open-source event management and ticket selling platform — perfect for concerts, conferences, and everything in between 🎟️ If you find this project helpful, please consider giving us a star ⭐️
Hi.Events is a self-hosted event ticketing platform built on Laravel + React, positioned as a drop-in replacement for Eventbrite/Tickettailor. It covers the full ticketing lifecycle: checkout, QR check-in, refunds, promo codes, Stripe Connect payouts, and attendee management. Aimed at promoters, venues, and conference organizers who want to avoid per-ticket fees and retain their own data.
- Architecture is well-structured for a PHP app: proper domain objects, DTOs, service layer separation, and generated abstract base classes suggest intentional design rather than a spaghetti Laravel CRUD app.
- Docker-first deployment with one-click options for DigitalOcean, Render, Railway, and Zeabur means actual humans can get this running without reading 40 pages of docs.
- Feature set is genuinely competitive: Stripe Connect with instant payouts, capacity assignments across ticket types, affiliate tracking, webhook integrations, and tiered pricing are all things you'd normally pay SaaS fees for.
- Active maintenance with CI workflows, Dependabot, a real SECURITY.md, and regular releases — not an abandoned dump of someone's side project.
- AGPL-3.0 with 'additional terms' is a red flag for commercial users. The licensing page is behind a marketing site, not in the repo itself, so you won't know the restrictions until you're already invested.
- Payment processors are effectively Stripe-only (Razorpay domain objects exist but appear incomplete). If you're not in a Stripe-supported country or need PayPal/offline-first flows, you're blocked.
- The Generated/ directory with abstract domain object classes hints at a code-generation approach that will make contributing or extending the data model confusing — any schema change likely requires running a generator that isn't clearly documented in the README.
- No mention of load testing or high-concurrency handling for ticket sales. Race conditions during ticket inventory exhaustion (the classic 'oversell' problem) are notoriously hard to get right, and there's no visible documentation of how this is handled under pressure.