An Eventbrite Alternative on Your Own Site: When It Makes Sense

A community class selling 60 tickets at £8 hands over a meaningful slice of a small margin in per-ticket fees — and every one of those attendees came off the organiser’s own mailing list. Nobody discovered anything. The fee was paid for an introduction that had already happened, years ago.

That is the case for self-hosted ticketing, and it is narrower than the usual pitch. Eventbrite is genuinely worth paying for in a lot of situations. Knowing which situation you are in is the entire decision.

What the fee actually buys

Two things, and it is worth separating them because only one is about software.

Discovery. There are people browsing for something to do this weekend with no particular event in mind. That marketplace is real, you cannot replicate it, and a cut of tickets sold to people who found you there is a fair price for an introduction you did not have to make.

Trust. This one gets overlooked and matters more than organisers expect. When a stranger hands money to an organiser they have never heard of, a known brand in the middle is doing real work — there is a recognisable refund path and someone to complain to. Take that away and a first-time attendee is trusting your website on nothing but its appearance.

Both are worth paying for when you need them. The problem is that the fee does not distinguish between the stranger who found you by browsing and the regular who has come to your thing every month for three years and clicked a link in your own newsletter.

Per-ticket fees bite hardest exactly where community events live

Percentage fees are proportionate; per-ticket components are not. A fixed fee per ticket is a rounding error on a £120 conference seat and a serious bite out of a £6 community night.

So the events that can least afford the fee — cheap tickets, high volume, thin or nonexistent margin, often run by volunteers — are the ones where it lands hardest. A 200-person church fundraiser at £5 a head is precisely the case where fees are most painful and discovery is least needed, because everyone attending already goes to the church.

The split to run before changing anything

Take your last three or four events and sort attendees into two groups. You may need to ask, and asking is worth it:

• Found us by browsing the marketplace. People who did not know you existed and discovered the event on the platform. The fee earned its money here, cleanly.
• Came from our own channels. Your mailing list, your social accounts, a poster in the venue, word of mouth, or people who simply come to everything you run. Every one of these paid a discovery fee for an audience you already owned.

If the first group dominates, the platform is doing real work and you should stay. If the second group dominates — and for recurring community events it usually does, overwhelmingly — you are renting access to your own people.

One nuance worth holding onto: the same organiser can be in both positions depending on the event. A monthly members’ night and an annual public showcase are different problems, and there is no rule saying you have to answer them the same way.

What you take on

Three things move to you, and the third is the one people underestimate.

Checkout and refunds. If you already run WooCommerce this is largely solved — your gateway, your tax setup, your refund process. If you do not, this is a genuine setup cost and not a small one.

Attendee communication. Reminders, changes, cancellations, the “I never got my ticket” email. The platform handled some of that, and it handled it without waking you.

You lose discovery entirely. Not reduced — gone. Nobody browses your website looking for something to do on Saturday. If a meaningful share of your attendance comes from the marketplace, moving away does not save you the fee; it costs you the attendance.

When staying put is the right answer

Stay on the platform for a first-time event where nobody knows to look for you. Stay for anything public-facing that depends on strangers finding it. Stay when your attendees are mostly people who have never dealt with you, because the third-party trust is doing real work. And stay if you simply do not want to run another system — a volunteer-run organisation with one person handling everything has a perfectly good reason to pay for someone else to handle ticketing.

What self-hosted ticketing actually needs

Less than people expect. A price on the event, a checkout, a ticket the attendee can show, and a way to check it at the door. If you already run WordPress with WooCommerce, you have the middle two.

The one design decision that matters is when the ticket gets issued. It must happen on payment, not on registration — otherwise abandoned checkouts email valid tickets and quietly consume seats at an event you believe is sold out. That single detail is covered properly in the technical walkthrough, along with why the QR should carry an opaque token rather than the attendee’s details.

The cheap first test

Do not migrate everything. Take one recurring event you reliably sell out to your own list — the monthly meetup, the members’ night, the class that always fills — and sell that one on your own site. Keep the platform for anything public-facing.

You lose no discovery, because that event never depended on discovery. You find out within one cycle whether your audience will click a different link, which is the only genuinely uncertain part. And if it works, you have removed the fee permanently on your highest-frequency event for a one-time cost.

If it does not work — if attendance drops because people genuinely needed the platform’s reminders and familiarity — you have learned that cheaply, on one event, and you can go back.

Running recurring events and tired of paying to reach your own list? Tell us what you run.