Cal.diy vs Rallly
| Tagline | Open-source online appointment scheduling built on Cal.com | 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 | 46k | 5.1k |
| Language | Nodejs | TypeScript |
| License | MIT | 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 | 2 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.
Cal.diy
- Self-hosted setup requires configuring PostgreSQL, email/SMTP, and OAuth providers
- Enterprise features (SAML SSO, workflows at scale, analytics) are cloud-only or require an enterprise license
- Payment collection integrations need additional third-party setup
- Admin UI for multi-tenant management is less polished than Calendly's hosted offering
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 Cal.diy for the larger community and ecosystem. Rallly has seen more recent development. Open each guide below for deploy steps and the full feature gap.