Eventbrite gets you live fast, then invoices you for every ticket and holds the attendee list hostage when you argue about fees. Your conference brand deserves its own checkout page, your Stripe account, and a database export that does not require a support ticket.
Hi.Events (HiEventsDev/hi.events on GitHub) is the open-source answer for concerts, club nights, workshops, and multi-day conferences. About 4,200 stars, AGPL-3.0 (with extra attribution terms), Laravel and React, PostgreSQL, Redis, and a Docker all-in-one path that lands on port 8123 for a first login.
What you get
Hi.Events is a full ticketing stack, not a Meetup clone. One-off and recurring events, tiered and donation tickets, promo codes, waitlists, embeddable widgets for your existing site, and payouts to your Stripe. Check-in tools cover phone cameras, USB scanners, door sales (box office on enterprise terms), PDF tickets, and reports for tax and promos.
Version 2.x added reserved seating, lineups, schedules, SSO, team permissions, and API keys. The marketing line positions it against Eventbrite, Tickettailor, and Dice.fm. That is fair for indie promoters and venues who want white-label checkout without surrendering customer emails.
Self-host with the docker/all-in-one compose file: set APP_KEY and JWT_SECRET, bring up the stack, create an organizer account. Plan PHP 8.3, Postgres, Redis, and enough RAM for Laravel plus SSR React. This is a small-team production app, not a single PHP file in public_html.
Licensing reality check
AGPL means network use has copyleft obligations. The project also requires keeping “Powered by Hi.Events” on generated pages and emails unless you buy a commercial licence. Reserved seating and box office features sit under enterprise licensing. Read hi.events/licensing before you promise a client a fully unbranded door scanner workflow.
Why self-host?
Ticket buyers hand you names, emails, and payment metadata. Canadian festivals and conference orgs often want that data on infrastructure they control. Self-hosted Hi.Events keeps Postgres in your tenancy, Stripe in your account, and exports on your schedule. You trade platform convenience for ops work: backups, TLS, upgrades, and reading release notes before 1.x jumps.
Compared with our alf.io post: alf.io is Java and PostgreSQL, strong for classic conference reservations. Hi.Events is the modern Laravel/React product with embeds, marketing pixels, and nightclub-friendly UX. Pick the stack your team can actually run.
Good fit / skip it
Good fit: venues, promoters, community conferences, anyone outgrowing Eventbrite fees who has Docker skills or a host like us to run it.
Skip it: single free RSVP form, teams allergic to AGPL attribution, or orgs needing enterprise seat maps without budgeting for Hi.Events commercial terms.
Hosting in Canada
Run the all-in-one image on a CloudBox VPS or dedicated VM with Postgres backups and Redis persistent. Point your domain at nginx, terminate TLS, and store attendee data in Canada if residency language matters in your sponsor deck.
Bottom line
Hi.Events is self-hosted event ticketing with serious checkout features, Stripe payouts you control, and AGPL trade-offs you read first. Docker up, wire Stripe, test check-in, then sell tickets on your brand.
Talk with Swift Host for Canadian VPS hosting with Docker, TLS, and backups. We are in St. Albert and actually answer the phone.