Alf.io vs Rallly
| Tagline | Open-source ticket reservation platform for events of any size | 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 | 1.6k | 5.1k |
| Language | Java | TypeScript |
| License | GPL-3.0 | AGPL-3.0 |
| Self-host difficulty | 4/5 Involved | 3/5 Moderate |
| Deploy options | Docker Docker Compose Manual | One-Click Docker Docker Compose Manual |
| Managed hosting | ||
| Last updated | 4 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.
Alf.io
- No built-in recurring appointment booking (1:1 scheduling like Calendly)
- Mobile app for attendees is not provided; check-in relies on a separate web view
- Analytics and post-event reporting are basic compared to Eventbrite or Cvent
- Initial Java/PostgreSQL setup is heavier than typical SaaS onboarding
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
Choose Rallly if you want the lower-effort setup; 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.