Hi.Events - Event Technology Platform Review

Cloud and self-hosted event ticketing with Stripe payment integration and documented webhooks.

Hi.Events offers a managed cloud service and a self-hosted deployment route. That distinction matters for an organizer's operating model: cloud users rely on the service provider's hosting, while self-hosting means budgeting for infrastructure, updates, backups and support ownership. The pricing page describes buyer-paid or organizer-absorbed cloud platform charges and notes that payment processing is additional. Its self-hosting section sets out open-source licensing with conditions and separate commercial licences. “Free to self-host” does not mean payment processing or operating the server costs nothing.

Licence and payments

The same pricing and licence FAQ distinguishes a self-hosted installation selling one organization's events from a platform installation serving third-party organizers. It says Stripe and Stripe Connect are the out-of-the-box payment gateways. Before procurement, establish whether you are selling only your own admissions or offering ticketing to clients; ask legal and technical owners to review licence obligations rather than assuming one licence covers both. Check Stripe account availability in your country, processor fees, chargeback responsibilities and settlement terms separately from the Hi.Events platform charge.

Hi.Events' webhooks guide describes event-level and organizer-level subscriptions for changes such as orders and check-ins, with JSON posted to a configured endpoint. It also distinguishes the event lifecycle types available only to organizer-level webhooks. If you need a live feed into a CRM or reporting warehouse, test event selection, signature verification, retries, missing deliveries and cancellation handling before production; use the integrations and webhooks guide. A documented webhook is not the same as a maintained, ready-made connection to your particular system.

Demonstrate ownership

Have staff publish a paid event, complete a test purchase, check in one ticket and cancel another. Confirm which party can refund the buyer, what happens to transaction charges and whether the door list is immediately reconciled; the refunds and chargebacks guide is a useful script. For self-hosting, ask who patches the application, stores backups, monitors webhooks and responds during an event. For cloud, request the applicable data-processing, export and support terms.

Test the mobile and keyboard buyer journey rather than inferring accessibility or security compliance from open-source availability. Ask for retention settings, staff roles and incident procedures using the privacy, accessibility and security checklist. Hi.Events is a candidate when deployment control is a real requirement, but the technical and licence work should be costed beside ticketing charges.

Key Features

Pros

Cons

Best For

Teams evaluating cloud ticketing or able to operate their own ticketing infrastructure under appropriate licence terms.

Pricing

Confirm current cloud buyer/organizer fee allocation, Stripe processing and local availability; review self-host licence conditions and operating costs.