Alf.io

Open-source event ticketing, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: Open-source (GPL-3.0) ticket reservation and event attendance management system — think Eventbrite, but running on your server and charging attendees exactly what you decide, with no per-ticket platform fee going to a third party [README][1].
• Who it’s for: Event organizers — conferences, trade shows, workshops, meetups — who are tired of Eventbrite’s percentage cut and want full control over attendee data, payment flows, and pricing [website].
• Cost savings: Eventbrite charges ~6.95% + $1.79 per paid ticket on its standard plan. A 200-person conference at $50/ticket sends roughly $290 to Eventbrite alone. Self-hosted Alf.io on a $6 VPS sends $0 to a platform vendor — you pay only Stripe or Mollie’s direct processing fee [website].
• Key strength: A surprisingly complete ecosystem: web ticketing shop, backoffice for organizers, mobile check-in app (iOS + Android), and an optional Raspberry Pi-powered offline check-in station for high-throughput events [website].
• Key weakness: Java-based stack with a real setup bar — you need JDK 17 and PostgreSQL before you start. Third-party review coverage is thin (1,571 GitHub stars as of this writing), which signals niche adoption rather than broad community validation [README][1].

---

What is Alf.io

Alf.io (pronounced [ˈalfjo], a Sicilian given name) is a free and open source event attendance management system. The pitch on the homepage is direct: the project was “developed for event organizers who care about privacy, security and fair pricing policy for their customers” [website]. That sentence tells you who built it and why — someone who ran events, got annoyed at platform fees and data lock-in, and built the tool they wished existed.

The project covers the full lifecycle of a ticketed event. Attendees visit a public-facing ticket shop to browse, reserve, and purchase tickets. Organizers manage everything from an admin backoffice: attendee lists, check-in, reporting, payment reconciliation, and communication. When attendees arrive, organizers run check-in from a mobile app or, for large events with badge printing, a Raspberry Pi station that operates fully offline [website].

That last part is worth pausing on. The Alf.io-PI component — a GPLv3 RaspberryPi-powered check-in station — is not a feature you find on Eventbrite’s feature page. On first startup, stations form a cluster, download an encrypted attendee list from the main Alf.io instance, and from that point can operate without internet connectivity. A ticket can’t be checked in twice across two different stations, even offline [website]. This is purpose-built hardware-tier thinking for real-world conference logistics, not a dashboard checkbox.

The project sits at 1,571 GitHub stars. That’s modest compared to general-purpose tools like n8n or Activepieces, but it’s not a fair comparison — event ticketing is a narrower problem space than workflow automation. The relevant comparison is against Pretix (the other major open-source ticketing system), not against tools with ten times the market size.

---

Why people choose it

Third-party review coverage of Alf.io is genuinely thin. The only independent source available [1] mirrors the README rather than offering original analysis. That’s an honest signal: Alf.io has a committed user base among European conference organizers (the project originated in the Italian open source community and the UI ships in nine languages including Italian, German, Dutch, French, and Romanian) but it hasn’t broken through to broad English-language developer media [website][1].

What does appear consistently across the GitHub project, the OpenCollective sponsors page, and the Alf.io website itself is the organizer-side value proposition: you keep your attendee data, you set your own fees, and the platform doesn’t take a cut of your ticket revenue [website].

The alternative — Eventbrite — charges a percentage of every ticket sold, routes attendees through its own brand experience, and owns the relationship with your attendees in ways that are uncomfortable when you’re building a recurring community around an annual conference. Organizers who have run events of any size will recognize the specific pain: Eventbrite’s fee structure makes economic sense for a one-off event, then becomes increasingly irritating as you grow.

The Swicket managed version (the premium hosted offering built and run by the Alf.io creators) acknowledges that self-hosting is a real barrier. The website describes it as designed for organizers who need “Hassle-Free Hosting: No server setup or maintenance,” “Advanced Features: CRM integrations, advanced lead capture, badge printing & more,” and “Dedicated Support: Email, chat, and video call support from the creators of Alf.io” [website]. That this exists at all is a good signal — the creators are invested enough in the project to run a commercial service around it, which means long-term maintenance is more likely than for a pure volunteer project.

---

Features: what it actually does

Based on the README, website, and project repository:

Ticketing and registration:

• Public-facing ticket shop where attendees reserve and purchase tickets [website]
• Free-of-charge events and paid events [website]
• Multiple payment methods per event: pre-pay by credit card (Stripe, Mollie), PayPal, Revolut, bank transfer, or on-site payment at the door [website]
• Supported payment processors: Stripe (credit cards), Mollie (credit cards, iDEAL, Bancontact, ING Home Pay, Belfius, KBC/CBC, Przelewy24), Revolut, PayPal [website]
• PCI compliance handled through Stripe/Mollie — no card data stored on your server [website]
• No account required for attendees [website]
• Multi-language ticket shop: Italian, English, Spanish, German, Dutch, French, Turkish, Romanian, Portuguese [website]

Admin backoffice:

• Attendee management and reporting [website]
• Google Analytics integration with anonymous stats and IP scrambling enabled by default (EU cookie law compliant) [website]
• Extensions system for integration with third-party tools like CRM systems [website]
• REST API for external integrations [merged profile]

Check-in ecosystem:

• Alf.io Scan — iOS and Android mobile app for check-in operators and sponsor lead capture [website]
• Alf.io-PI — Raspberry Pi powered, touchscreen, offline-capable, high-throughput check-in station with on-site badge printing. Stations cluster, sync an encrypted attendee list on startup, and operate fully offline thereafter. One ticket cannot be checked in twice across two stations [website]

Infrastructure:

• Docker and Docker Compose deployment [merged profile][README]
• PostgreSQL backend (version 10 or later required) [README]
• Java 17 runtime [README]
• Cloud deployment tutorials available for Heroku, OpenShift, Pivotal Cloud Foundry, SAP Cloud Platform, Google Kubernetes Engine, and Clever Cloud [website]
• Row-level security policies in PostgreSQL (database user must not be SUPERUSER) [README]
• HTTPS enforcement with strict Content Security Policy [website]
• Session persistence in the database via jdbc-session profile [README]

---

Pricing: SaaS vs self-hosted math

Alf.io self-hosted:

• Software: $0 (GPL-3.0 license) [README]
• Hosting: ~$5–10/month for a VPS adequate for small-to-medium events
• Payment processing: Stripe charges 2.9% + $0.30 per transaction (or Mollie’s equivalent) — this you pay regardless of which ticketing platform you use

Swicket (managed version by Alf.io creators):

• Pricing not disclosed publicly on the website — contact for details [website]. This is common for event-software-as-a-service with white-glove setup.

Eventbrite for comparison:

• Free events: $0
• Paid events (Flex plan): 6.95% of ticket price + $1.79 per ticket
• Paid events (Pro/Premium plans): pricing by quote

Concrete math for a mid-size conference:

A 300-person conference, tickets at $75 each, $22,500 in gross ticket revenue:

• Eventbrite Flex: $1,564 + $537 = **$2,100 in platform fees**, plus Stripe processing on top
• Self-hosted Alf.io on a $10/month VPS: $10/month hosting + Stripe processing only — the 6.95% platform fee disappears entirely

Across two annual conferences per year at this size, switching from Eventbrite to self-hosted Alf.io saves roughly $4,200/year in platform fees. The setup cost is one afternoon of technical work, or a one-time deployment service fee.

For smaller events — a $20 workshop with 50 attendees — the math is less dramatic ($207 vs. near-zero) but the principle is the same: every ticketing platform’s percentage fee compounds as you grow.

---

Deployment reality check

Alf.io has a harder setup floor than most tools in this review series. This is not a “docker run one line and done” situation — it’s a Java Spring Boot application backed by PostgreSQL, and it shows in the requirements.

What you actually need:

• A Linux VPS with at least 2–4GB RAM
• Java 17 (JDK required, not just JRE, for builds) [README]
• PostgreSQL 10 or later [README]
• Docker and docker-compose if going the container route
• A reverse proxy (nginx or Caddy) for HTTPS termination
• An SMTP provider for transactional email (ticket confirmations, etc.)
• A Stripe or Mollie account if accepting card payments

The database user requirement is non-obvious: PostgreSQL row security policies that Alf.io relies on only work if the database user is not a SUPERUSER. This is noted in the README [README][1] but will surprise anyone who provisions a database with a default admin user and wonders why security checks don’t apply.

Docker Compose caveat: The README explicitly states that “Running alf.io in production using Docker compose is not officially supported” [README][1]. You can do it, but you need to add port 8443 mapping, handle SSL termination separately, and remove the development profile environment variable. This is honest documentation, but it’s also a warning that the Docker path is not as turnkey as you’d find with a tool designed from the ground up for container deployment.

What can go sideways:

• The Gradle build requires JDK 17 specifically — not 11, not 21’s latest. Java version mismatch is a common first-timer error.
• The PostgreSQL SUPERUSER restriction is easy to miss and will cause silent security policy failures.
• Email configuration for ticket delivery requires proper SMTP setup — if this isn’t done, attendees receive no confirmation after purchase, which is a bad first impression at any event.
• The README notes that the main branch “may contain unstable and untested code” while v2 development is in progress [README][1]. Production deployments should use a Released version.

Realistic time estimate for a developer: 1–3 hours to a working instance from scratch, assuming comfort with Linux and Docker. For a non-technical organizer following a guide: this probably requires a developer’s help. Budget a deployment service or a technical co-organizer for your first setup.

---

Pros and cons

Pros

• No platform fee on ticket revenue. The entire point of self-hosting — Eventbrite’s ~7% per-ticket cut disappears. You pay only payment processor fees (Stripe/Mollie), which you’d pay through Eventbrite anyway [website].
• Full attendee data ownership. No third-party platform claiming a relationship with your conference attendees or emailing them about other events [website].
• Complete event ecosystem. Web ticketing shop, admin backoffice, mobile check-in app, and an offline Raspberry Pi check-in station — this is not a minimum viable ticketing page [website].
• Multiple payment processors. Stripe, Mollie, Revolut, PayPal, bank transfer, and on-site payments — unusually broad gateway support for an open source project [website].
• PCI compliance done right. Card data never touches your server; handled entirely by Stripe/Mollie [website].
• Nine languages out of the box. European-origin project that ships with real internationalization [website].
• Privacy-first defaults. Anonymous analytics, IP scrambling, no attendee account required [website].
• Offline check-in. The Alf.io-PI cluster can operate fully offline while preventing duplicate check-ins across stations — a real conference-grade feature [website].
• Managed option available. Swicket provides a commercial hosted version by the creators if self-hosting is not viable [website].

Cons

• Java/Spring Boot stack. Heavier than PHP or Node.js alternatives. Requires JDK 17, PostgreSQL, and non-trivial RAM — not the lightest self-hosted footprint [README].
• Docker Compose not officially supported for production [README][1]. The containerized path needs manual work that other tools handle automatically.
• main branch is unstable. Active v2 development means the latest code is explicitly flagged as potentially untested [README][1]. You must track releases, not main.
• Thin third-party review coverage. 1,571 GitHub stars and nearly no independent English-language reviews means you’re taking more of a bet than with more widely-adopted tools [1]. Community troubleshooting resources are limited.
• Swicket pricing is opaque. The managed option exists but pricing isn’t public — makes it hard to evaluate as a Heroku-style “just host it for me” alternative [website].
• Extension/plugin ecosystem is small. REST API exists but the integration library is limited compared to SaaS platforms; CRM integrations require custom extension development [website][merged profile].
• No native email marketing. Alf.io manages ticketing; post-event communication is your responsibility via whatever email platform you integrate.

---

Who should use this / who shouldn’t

Use Alf.io if:

• You run recurring conferences, workshops, or meetups where Eventbrite’s percentage fee is a genuine line item in your budget.
• Attendee data privacy is a stated value — you don’t want a platform knowing your attendees and marketing to them.
• You have a developer on the team (or budget to hire one for setup) and don’t need to have zero technical overhead.
• You accept European payment methods — Mollie’s iDEAL, Bancontact, and KBC/CBC support is built in, which few alternatives match.
• You need offline check-in for high-throughput events with badge printing.

Skip it (use Swicket or hire deployment help) if:

• You want Alf.io’s features but can’t manage a Java server. The managed option exists specifically for this case.
• You’re running a one-off event with uncertain future — the setup investment isn’t worth it for a single event.

Skip it (use Pretix) if:

• You want a Python-based alternative with a larger English-language community and a broader plugin ecosystem. Pretix is the other serious open-source ticketing option and has more third-party integrations [website].

Skip it (stay on Eventbrite) if:

• You value Eventbrite’s built-in event discovery and audience. Eventbrite has a marketplace; self-hosted Alf.io does not. Attendees find your event through your own marketing, not through an Eventbrite browse page.
• Your events are small and infrequent enough that the platform fee is less than the setup cost.
• Your organization’s IT policy won’t approve self-hosted infrastructure.

Skip it (use Ticket Tailor) if:

• You want no per-ticket fees but also no server to run. Ticket Tailor charges a flat monthly fee (not a percentage) and requires no infrastructure.

---

Alternatives worth considering

• Pretix — The other major open-source ticketing platform. Python-based, broader plugin ecosystem, more English-language community resources. Direct comparison with Alf.io: Pretix wins on plugin breadth, Alf.io wins on payment gateway diversity and the offline check-in hardware ecosystem.
• Eventbrite — The incumbent. Built-in discovery, zero setup, attendee account management. Costs ~6.95% + $1.79 per paid ticket. The right choice when platform fees are acceptable and discoverability matters.
• Ticket Tailor — Flat monthly fee with no per-ticket percentage. Closed-source SaaS, but the pricing model is closer to self-hosted economics than Eventbrite. Worth evaluating before committing to self-hosting infrastructure.
• Swicket — The managed hosted version of Alf.io built by the creators. If you want Alf.io’s features without the server — this is the answer, pricing permitting.
• Open Event — Another open-source event management platform with a broader feature set (including sponsorship management and a public event directory). More complex setup, more features.
• Attendize — Simpler open-source ticketing, PHP-based. Lighter than Alf.io but less actively maintained.

---

Bottom line

Alf.io solves one problem very specifically: conference and event organizers paying Eventbrite a percentage of every ticket sold, when that percentage is pure platform rent rather than value delivered. The project is mature enough — with a real payment ecosystem, a mobile check-in app, and an offline hardware check-in station — that it handles actual production events, not just demos. The GPL-3.0 license means you own the deployment and owe no ongoing licensing fee.

The honest caveats are real. The Java stack and the unsupported Docker Compose path mean setup is heavier than comparable open-source tools. Third-party review coverage is thin enough that you’re leaning more on the GitHub commit history and the OpenCollective sponsors list than on the kind of community validation that tools like n8n or Nextcloud have built. And if you need Eventbrite’s discovery marketplace — the browseable events directory that brings in organic attendees — no self-hosted alternative replaces that.

But for an organizer running recurring events with a known audience, the fee savings are real and compound. For a 300-person conference at $75/ticket, a single event saves over $2,000 in platform fees. Two events a year, and the self-hosting math pays for a part-time technical co-organizer. If you’re at that volume and the setup barrier is the only thing stopping you, that’s exactly what unsubbed.co’s parent studio upready.dev handles — one-time deployment, you own the infrastructure from there.

---

Sources

1. Libre Self-hosted — Alf.io project page (community listing with GitHub stats and README mirror). https://libreselfhosted.com/project/alfio/

Primary sources:

• GitHub repository and README — https://github.com/alfio-event/alf.io (1,571 stars, GPL-3.0 license)
• Official website — https://alf.io/
• Swicket (managed Alf.io) — https://alf.io/ (referenced on homepage)