Hi.Events vs Rallly
| Tagline | Self-hosted event management and ticketing for any scale | Self-hosted scheduling polls to find the best time for a group to meet |
| Category | Scheduling & Booking | Scheduling & Booking |
| Replaces | Calendly, Acuity Scheduling | Calendly |
| GitHub stars | 3.9k | 5.1k |
| Language | Docker | TypeScript |
| License | AGPL-3.0 | AGPL-3.0 |
| Self-host difficulty | 3/5 Moderate | 3/5 Moderate |
| Deploy options | Docker Docker Compose Manual | One-Click Docker Docker Compose Manual |
| Managed hosting | ||
| Last updated | 14 days ago | today |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
Hi.Events
- Payment gateway support is limited to Stripe; no PayPal or regional gateways out of the box
- No recurring event / subscription ticketing support
- Email marketing and attendee re-engagement tools are minimal
- Mobile check-in app is not available; badge printing requires third-party tools
Rallly
- Focused on group availability polling rather than one-on-one booking pages, so it does not replace Calendly's personal booking links.
- No direct calendar-availability checking or two-way calendar sync to auto-block busy times.
- No built-in payment collection or paid-appointment support.
- Requires PostgreSQL and SMTP configuration to self-host; not a single-binary deploy.
Bottom line
Both are a similar lift to self-host; choose Rallly for the larger community and ecosystem. Rallly has seen more recent development. Open each guide below for deploy steps and the full feature gap.