Enterprise Features

The box office, reserved seating and per-account single sign-on are Hi.Events’ Enterprise features. This page is for people running Hi.Events on their own servers.

Which Features Need a Licence

Most of Hi.Events is open source under the AGPL and free to self-host. Three features are Enterprise features and need a paid licence. The platform licence (other organizers selling through your install) includes them; on a licence for your own events they’re a paid add-on, priced on request at [email protected]:

Help center articles for these features carry a badge like this one, under the title:

Everything else is part of the AGPL core and needs no licence key, including instance-wide sign-in with Google, Microsoft or your own OpenID Connect provider, team access controls (roles, access limited to particular organizers or events, and required two-factor authentication), API keys and the API, lineup and schedule, and widgets. Instance-wide sign-in is set up with environment variables on the server: see Setting Up Single Sign-On.

A licence key also removes the “Powered by Hi.Events” link, which the AGPL terms otherwise ask you to keep.

Turning Them On

The code for Enterprise features lives in the backend/ee and frontend/src/ee folders of the repository. It’s covered by the Hi.Events Enterprise Licence rather than the AGPL, which covers everything else.

To turn the features on, add your licence key to the backend environment:

APP_LICENCE_KEY=your-licence-key

Then redeploy the backend so it picks up the new environment. With Docker Compose, run docker compose up -d; docker compose restart doesn’t reload the environment. A superadmin can check the key was accepted on the Licence page of the admin area.

Your licence key unlocks the Enterprise features it was issued for. Without a key they stay hidden, and the rest of Hi.Events works as normal. To work on them locally, set APP_LICENCE_KEY=development. That unlocks them for development and testing only, not production, and shows a “Development licence” notice once they’re in use.

See the licences on the licensing page, or email [email protected] with questions.

If Your Licence Doesn’t Include a Feature

If a feature is already set up but your licence doesn’t include it, for example seat maps on an own-events licence without the seating add-on, account admins see Not in licence next to Licence in the user menu, and clicking it explains which features aren’t included. The admin area’s Licence page lists each feature as Included or Not included. Setup for that feature is locked in the same way as an expired licence (below): what’s set up can still be viewed, switched off or removed, but nothing new can be set up. To unlock it, ask [email protected] to add the feature, put the new key in APP_LICENCE_KEY and redeploy the backend.

If a Licence Expires

You get 30 days’ grace after a licence expires. After that, setup is locked: you can’t create or change seat maps, link tickets to bands, hold seats back, create or edit box offices, set PINs or pair card readers. What’s already set up can still be viewed or removed.

Nothing already on sale breaks: seated events keep selling online, tickets already sold stay valid, and you can still move attendees between seats. Box office staff who are already signed in can keep selling until their sign-in ends (24 hours at most), but nobody can sign in to a box office again until you renew.

Single sign-on keeps working too: members keep signing in through a connection that’s already on. Account admins can’t create, edit or test a connection, add or verify domains, or turn the connection, required single sign-on or a member’s requirement on. They can still view the setup, turn those things off, remove domains and delete the connection.