Eventleaf and event67: registration stays put, the app comes from us

Eventleaf (Eventleaf is a trademark of Jolly Technologies Inc.) publishes a product built around getting people registered and through the door. Its own site sets out online event registration and ticketing, attendee check-in with onsite badge printing, polls, Q&A and surveys, the Eventleaf Guide attendee application for iOS, Android and Windows covering schedules and engagement with presenters, exhibition booth sales and lead retrieval, abstract and proposal submission management, and gamification and engagement tooling alongside virtual event capabilities, made by Jolly Technologies Inc. of Redwood City, California (eventleaf.com, accessed 3 September 2026). Registration, money, badges, booths and abstracts: that is a commercial and logistical spine.

event67 has precisely none of that spine. No registration form that sells anything, no payment collection, no printer, no booth sales, no abstract review, no speaker portal. Our forms gather responses and never money. Which is why the useful framing here is addition rather than substitution — the two products touch the same attendee at different moments, and there is no configuration in which we take over the first moment.

So what does the second moment look like when you buy it separately? The attendee experience Eventleaf publishes runs inside the Eventleaf Guide application, which attendees download under that name; no branded or white-label app carrying the organiser's own store listing is published on the Eventleaf site as checked on 3 September 2026. event67's whole delivery model is the opposite one: the app is published to the App Store and Google Play under the organiser's own name, with the organiser's logo, colours and typography flowing through every screen. Alongside that, event67 adds surfaces Eventleaf's published pages do not describe — a shared photo album with moderation, admin-only team chat, Apple Wallet passes with an iOS Live Activity, and a console-side email campaign and template system with a themed signature footer on every send.

On the money, both sides publish, and neither figure belongs in our prose. Eventleaf's pricing page carries a free starter allowance measured across a year, per-attendee tiers above it, a call-for-price tier for custom attendee numbers, a separate percentage on registration sales that varies with the payment processor, discounts for nonprofits and universities, and no contract on the published tiers (accessed 3 September 2026). event67 charges the organiser per activated attendee and never takes a cut of a registration, because we never touch one. The comparison table on this page carries what each side publishes.

For the job it is bought to do, this is not a contest. Eventleaf publishes online registration and ticketing, attendee check-in with onsite badge printing, exhibition booth sales with lead retrieval, and abstract and proposal submission management (eventleaf.com, accessed 3 September 2026). event67 has none of those, will not have them, and cannot be configured into them. If your requirement is to sell places, take the money, print a badge and review the abstracts, Eventleaf answers all four and we answer none.

Price matters too, and honestly. Eventleaf's published per-attendee tiers sit below event67's published rate at small and mid scale, and its free starter allowance is measured in attendees across a year rather than a single event — a materially different shape from event67's free tier of one live event up to 50 activated attendees (eventleaf.com/Pricing, accessed 3 September 2026). A small nonprofit running several modest events in a year may find that annual allowance covers the whole calendar, where our free tier covers one event and then meters.

And the attendee app is not empty. Eventleaf publishes the Eventleaf Guide application for iOS, Android and Windows with schedules and engagement with presenters, along with polls, Q&A and surveys, plus gamification and engagement tooling (accessed 3 September 2026). An organiser who wants a single vendor, a single invoice and a single support conversation across registration, badges and the attendee app has a coherent case for staying exactly where they are. Adding a second product adds a second relationship, and that is a real cost even when the software is good.

1. Registration stays where it is

   Keep selling and collecting exactly as you do now. event67 has no opinion about your registration flow and no ability to run one, so nothing about that half changes.

2. Export the confirmed list when it settles

   Name, email and whichever profile fields belong in the attendee directory. event67 imports from CSV. Re-import later if late registrations arrive; invites are unlimited and never metered.

3. Build the programme and the brand in the console

   Sessions, tracks, rooms, speakers and sponsors, plus workshop capacities where you want server-side RSVP limits. Then the theme — logo, colours and typography — with the WCAG AA advisory reporting alongside as you set each pair.

4. Invite, run the days, then settle up

   Bulk invites carry per-recipient delivery tracking. The console meter counts activated attendees from publication onward, the amount is emailed before any card is charged, and the charge lands 48 hours after the event ends.

The awkward part of running two tools is the seam between them, and it is worth naming rather than glossing. Your registration list lives in one system and your app audience in another, so late registrations mean a second import and cancellations mean a manual tidy-up. Attendees also meet two brands: they register on one surface and then install an app named after your association, which needs explaining in the confirmation email rather than being left to chance. Neither is difficult, but both are somebody's job, and pretending otherwise would be the fastest way to make this arrangement fail.