Your meetup sold out in twelve minutes and Eventbrite just emailed about a fee you did not budget for. The attendee list lives in someone else's dashboard. GDPR questions land in your inbox while you are still setting up the badge printer.
alf.io (alfio-event/alf.io) is the open-source exit lane. About 1,600 GitHub stars, built for conferences, trade shows, workshops, and meetups that want ticket reservations without surrendering buyer data to a US ticketing giant. The project pitches fair pricing and privacy on purpose; you run the app, you own the database.
What it does
alf.io handles event creation, ticket categories, reservations, payments (you wire your own provider), check-in, and the operational glue around them. Organizers get an admin UI at /admin. Buyers get a flow that is meant to feel professional, not like a spreadsheet with a credit card form stapled on.
It is a Java/Spring stack: Java 17 to build and run, PostgreSQL 10+ for storage. The README is explicit that the DB user should not be a PostgreSQL superuser, or row-level security policies will not apply. That detail matters if your security reviewer asks real questions.
Docker images live on Docker Hub (alfio/alf.io). Compose is marked experimental for production; most serious deployments terminate TLS at nginx or HAProxy and treat the container as an app tier, not the whole internet edge. Wallet pass support includes Apple certificate assets in the tree for PassKit-style tickets, with expiry dates called out in the docs.
The maintainers warn that master may carry unstable v2 work. If you self-host today, their guidance is often the 2.0-M4-maintenance branch for production-ready code. Read the release notes before you pin a version for a paying conference.
Why self-host?
Ticket platforms optimize for their margin, not your attendee privacy policy. Self-hosted alf.io means names, emails, dietary notes, and payment metadata sit in your Postgres on infrastructure you choose. Canadian meetups and B2B conferences can point to Canadian VPS or dedicated hosting when procurement asks where registrant data lives.
You still pay payment processing. You still do event ops. What you skip is per-ticket platform tax and the "export attendees" ritual when the vendor changes terms.
What running it takes
Budget a small VPS or cloud VM, not shared PHP hosting. You need JVM memory, Postgres backups, and someone who can rotate TLS certs. Local dev is ./gradlew -Pprofile=dev :bootRun against a local database named alfio. Production is closer to: Postgres, Java runtime or Docker image, reverse proxy, monitoring on the admin password printed at first boot (save it somewhere sane).
Integrations and jobs (email, payment webhooks, scheduled tasks) mean you watch logs after go-live. Spring profiles like demo and disable-jobs exist; do not accidentally ship demo mode to a paid event.
Good fit / skip it
Good fit: developer conferences, user groups, training workshops, trade shows with reserved seating, orgs allergic to Eventbrite fees, teams with a Java-friendly ops person.
Skip it: simple RSVP Google Forms, stadium-scale ticketing, organizers who want zero database admin, or events that need a fully managed SaaS with phone support at 3 a.m.
Hosting in Canada
Pair alf.io with a CloudBox VPS or dedicated slice in Toronto or Cambridge. Run PostgreSQL on the same box or a small managed instance, snapshot nightly, and keep TLS at the edge. Event data and check-in logs stay north of the border if that is what your sponsorship contract requires.
Bottom line
alf.io is self-hosted event ticketing: reservations, payments you configure, and attendee data in your Postgres. Plan Java, Postgres, and a stable branch; then run conferences without renting someone else's CRM.
Talk with Swift Host if you want alf.io on Canadian VPS hosting with TLS, backups, and someone who answers the phone. We are in St. Albert.