Fider vs Rallly
| Tagline | Open platform to collect, vote on, and prioritise user feedback | 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 | 4.4k | 5.1k |
| Language | Docker | 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 | today | 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.
Fider
- categorySlug is 'scheduling' but Fider is a feedback/voting tool; replaces options are limited to scheduling slugs in the ref
- No roadmap visualisation or timeline planning built in
- Integrations with Jira, Linear, or Slack require custom webhooks
- No in-app surveys or NPS measurement
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. Open each guide below for deploy steps and the full feature gap.