Hi.Events has released version 2.1.0 of its open-source ticketing platform, published on GitHub on 6 November 2026. If you sell tickets with it, you can now show a registration question only when an earlier answer calls for it, stop people who are not eligible from finishing their order, and let a buyer on a pay-later order tell you they have paid or send a payment link to whoever is paying. The release also redesigns the registration questions builder, adds a Czech translation and fixes a promo code fault that let one single-use code unlock hidden tickets for several buyers. This report is based on the v2.1.0 release notes and Hi.Events’ own help centre pages; we have not tested the release.
Follow-up questions show only when an earlier answer needs them
A follow-up question appears at checkout only when the buyer picks one of the answers you choose on an earlier question. Hi.Events’ registration questions guide gives the example of asking “Which dietary requirement?” only after someone answers yes to “Do you have dietary requirements?”.
- Follow-ups can only hang off choice questions (single choice, checkboxes, dropdown and multi-select dropdown).
- A follow-up can have its own follow-ups, up to five levels deep.
- A required follow-up is only required when it is shown.
- An attendee question can depend on an order question, but an order question can only depend on other order questions.
- If a buyer changes an earlier answer and a follow-up disappears, its answer is thrown away when the order is placed.
For organisers this means a shorter checkout for most buyers, with the extra detail collected only from the people it applies to.
Eligibility questions stop an order before payment
An eligibility question blocks registration when a buyer picks certain answers, and shows them a message you write. Hi.Events suggests it for age limits, member-only events and events for a particular profession. At least one answer must still allow registration. Among the new ready-made templates is an “Age check (18+)” question where “No” blocks the order, alongside a code of conduct checkbox, dietary requirements, t-shirt size, accessibility needs and “How did you hear about us?”.
The check works on what the buyer says, so it is a filter at checkout rather than proof of age or membership. If your event needs proof, you would still check ID or membership on the door.
A redesigned questions builder with a live checkout preview
Order questions and attendee questions now sit on one page, in two sections: “Asked once per order” and “Asked for each attendee”. A checkout preview panel beside them shows what buyers will fill in and updates as you edit; the pull request that added it says answers typed into the preview reveal follow-ups and eligibility messages without saving anything. Options can be dragged to reorder, pressing Enter adds the next option, and pasting a list splits it into options.
Attendee questions can now apply to “All tickets”, which includes tickets you add to the event later, so a question set up early in an on-sale is not missed when a new ticket type goes live. Questions about merchandise or other non-ticket products still need the specific products picked.
Buyers can report a payment or send a payment link
Two changes help events where people pay by bank transfer, invoice or purchase order. According to the offline payments guide:
- “I’ve paid” reporting. On an unpaid pay-later order, the buyer can add a short note such as a PO number and click “I’ve made the payment”. The order shows as “Payment reported” and the organiser gets an email. It does not mark the order as paid: you still check the money has arrived and mark it paid yourself. This setting is on by default once offline payments are turned on.
- Payment links. When someone else is paying, such as a company finance team buying staff tickets, the buyer can send them a link to pay. The person paying sees the order and the amount due, and can pay by card or choose pay later if you allow it, but cannot see the tickets or change the registration. Places are held for 72 hours by default while the link is open, never past the start of the event, and are released if nobody pays. This setting is off by default.
Holding places behind a payment link needs Stripe turned on as well as offline payments. Sharing payment details after a pay-later order does not need Stripe.
Fixes worth checking if you run Hi.Events
- Single-use promo codes. A single-use code that unlocks hidden products could be shared and used by any number of buyers while the first checkout using it was still open. Hidden products now need a code with uses left.
- Embedded checkout tracking. Embedded checkout could report the same order to the host page more than once, so sites tracking the order-completed event counted some sales twice. If you use that event for analytics or ad conversions, your past figures may be slightly high.
- Spam checks and sitemap. Archived events and custom email templates are now spam-checked, and the events sitemap lists only live events that are upcoming or ended in the last 120 days.
- Self-hosted Docker installs. Installs still using the example JWT secret now get Docker-specific instructions in the log.
The release also lets platform administrators suspend accounts, which sends that account’s events and organiser pages back to draft and stops its members signing in or using API keys.
Where this fits
Version 2.1.0 follows v2.0.0 on 23 October 2026, the first stable v2 release, which added recurring and multi-date events, embedded checkout and team permissions. Hi.Events is free to self-host under the AGPL, and its hosted service charges per paid ticket; our Hi.Events profile has the current pricing and features.
Conditional registration questions and pay-later handling are things to compare when you choose a ticketing tool. Other self-serve options in our registration and ticketing directory include pretix, Tito, Ticket Tailor and Humanitix. Our guide to choosing event registration software covers the other questions to ask.
Sources: github.com, hi.events
Companies in this story
- Hi.EventsYou can sell tickets with no monthly fee and pay nothing on free events, because the 1.25% + $0.60 fee on a paid ticket can go to the buyer, or self-host the open-source version free.
- pretixSell tickets, run the door and print badges from one backend with no monthly fee on the hosted service, which charges 2.5% per paid ticket, never more than €15, excluding VAT.
- TitoYou get registration and ticketing for technology, developer and B2B conferences without a subscription, with an embeddable widget, developer documentation and a standard fee of 3% per paid ticket.
- Ticket TailorSell tickets from £0.22 each (+ VAT) on prepaid credits or £0.60 pay as you go, take payouts straight into your own processor account, and scan entry with a free iOS and Android app.
- HumanitixFree events cost nothing and paid tickets carry a per-ticket booking fee (4.67% + £0.46 excl. VAT in the UK) that buyers pay by default, with every feature on every plan and no contract.
