Hi.Events

Tickets, registration and check-in for coworking events

Review status: Research backlog. Research candidate with incomplete checks; not a vetted recommendation.

open-core planned guide

Overview

Hi.Events lets organizers sell tickets, collect registrations and check attendees in. A coworking team could use it for a paid workshop or networking event while staff control capacity, refunds and arrival exceptions. Reserved seating, box office and company single sign-on require paid enterprise features.

At a glance

Field	Value
Categories	`event-management`
Deployment	`self-hosted`, `managed-saas`
License class	open-core
Cost model	`open-core-paid-features`
Implementation difficulty	`hard`
Maintenance burden	`high`
Maturity	`unknown`
Freshness status	`partially-verified` (2026-10-23)
Completeness	`partial`
Confidence	`medium`
Directory tier	`research-backlog`

Cost reality

Community self-hosting has no platform fee but needs hosting, email, administration and payment processing. Hosted ticket fees and payment processor fees apply. Paid enterprise licensing or add-ons cover restricted features and attribution removal.

Plans, provider terms and prices change; check official sources before making a budget or deployment decision.

Official pricing

Tasks reduced or augmented

Software does not replace community or ops staff. It may reduce or augment:

Collect event registrations and send ticket confirmations
Maintain attendee lists and record event check-in

Human oversight still needed

Approve event capacity, pricing, accessibility information and refunds
Resolve payment failures, attendee disputes and door exceptions

Manual process this can replace

Structured task-fit review has not been completed for this tool. Treat the free-text examples above as evaluation prompts, not replacement claims.

Data held

attendee names and email addresses
registration answers
ticket orders and payment references
check-in records
Personal data: yes
Payment data: yes / possible

Orders and payment references can be personal data. Actual card-data handling depends on provider and configuration and was not tested.

Risks

Area	Notes
Vendor lock-in	Export, migration and restore behavior have not been tested; retain a practical manual fallback before depending on the tool.
Security	Protect organizer accounts, payment credentials, attendee exports and check-in links. Keep the application updated and test a restore before public ticket sales.
Compliance	Staff remain responsible for event taxes, refund terms, marketing consent, accessibility and attendee-data retention.
Licensing	Community code requires visible Powered by Hi.Events attribution on generated pages and emails. Files under backend/ee and frontend/src/ee have an Enterprise Licence. Do not treat reserved seating, box office or company SSO as free community features.
Operational	Check the exact free versus enterprise feature boundary. Retain a staff-readable attendee list and a payment/refund exception process; software check-in does not determine physical venue safety.

Coworking fit

Roles: event-coordinator, community-manager, finance

Workflows: event-lifecycle

Problems: run-events, reduce-manual-admin

Smallest useful experiment

Create a private test workshop with ten places, register staff, test one approved low-value payment and refund if payments are needed, and reconcile check-in counts before opening sales.

Implementation guide

No implementation guide is published yet.

Verification

Status: partially-verified
Completeness: partial
Confidence: medium
Tier: research-backlog
Last reviewed: 2026-10-23
Sources:

Bounded official-source metadata review only. Features and edition boundaries were read; installation, task-fit evaluation, operator outcomes, integrations, security and recovery were not tested. Retained in Research Backlog; not a recommendation.