4 Open-Source Calendly Alternatives You Can Self-Host (2026)
Calendly Teams costs $20 per user per month for round-robin scheduling, routing forms, and team booking pages. Cal.com — the most feature-complete open-source scheduling platform — covers the same ground on a Liquid Web 4 GB Managed VPS for a flat VPS fee with no per-seat limit.
The honest framing for this post: the open-source Calendly alternatives space is thinner than adjacent categories like project management or email marketing. Cal.com dominates it so thoroughly that listing four alternatives requires including its own predecessor name, a complementary tool combo, and a simpler utility — rather than four genuinely competitive platforms. If you're looking for a self-hosted Calendly replacement, Cal.com covers 90% of use cases. The alternatives below fill the remaining 10%.
1. Cal.com (AGPL-3.0, ★ ~35k)
Cal.com is the open-source Calendly replacement — feature parity at every tier Calendly offers, plus capabilities that only appear in Calendly's enterprise tier. It covers individual booking pages, team round-robin, collective scheduling, routing forms, automated workflows (reminders, follow-ups), and integrations with Google Calendar, Outlook, Zoom, Google Meet, Stripe, Salesforce, and HubSpot.
The self-hosted Docker deployment is community-maintained (Cal.com Inc. focuses on its cloud product), which means the Docker Compose setup occasionally lags behind the main release. The setup works reliably, but expect to reference community guides alongside the official docs when standing up a new instance.
Key features:
-
Unlimited event types and booking pages — no tier gates
-
Round-robin and collective scheduling for team events
-
Routing forms to direct bookings to the right team member
-
Workflow automation — pre/post-meeting reminders via email or SMS
-
Stripe integration for paid bookings
-
Webhooks for custom downstream automation (CRM sync, Slack notifications)
-
Stars: ~35k · License: AGPL-3.0 · VPS recommended: 4 GB (Next.js + PostgreSQL + Redis)
2. Calendso (same project as Cal.com)
Cal.com was launched in 2021 under the name Calendso. The project rebranded to Cal.com in 2022. There is no separate "Calendso" product — older documentation, GitHub issues, and community forum posts will reference Calendso, but all active development, the current Docker images, and the self-hosted deployment path are under the Cal.com brand.
If you encounter Calendso references while researching, they point to the same codebase. The current repository is github.com/calcom/cal.com.
3. Zcal
Zcal is a simpler, cloud-only scheduling page builder focused on visual customization. It is not self-hostable — it's a SaaS product with a free tier. It's included here because it appears in "Calendly alternatives" searches and offers a lighter-weight experience than Cal.com's full feature set.
If you want a self-hosted solution, Zcal is not an option. If you want a simpler cloud alternative to Calendly (fewer features, cleaner UI, free tier), Zcal is worth evaluating for individual use — but it does not match Calendly's team scheduling features and cannot be deployed on your own infrastructure.
4. Cal.com + Formbricks (combined workflow)
For teams that want booking pages combined with pre-meeting qualification surveys or post-meeting feedback forms, pairing Cal.com with Formbricks creates a workflow that Calendly only approximates with its routing forms.
The integration is lightweight: a Formbricks survey form can precede a Cal.com booking link (collect qualification data, then redirect to the appropriate event type), or a Cal.com webhook can trigger a Formbricks survey link in the confirmation email. Both tools deploy on the same 4 GB Liquid Web VPS — combined idle RAM for Cal.com + Formbricks is roughly 1.5 GB, well within the available headroom.
This combination is particularly useful for:
-
Sales teams qualifying leads before allowing meeting booking
-
Consultants collecting project details before discovery calls
-
Support teams capturing issue context before scheduling technical calls
Comparison table
| Option | Type | License | Self-hostable | Best for |
|---|---|---|---|---|
| Cal.com | Full scheduling platform | AGPL-3.0 | Yes | All scheduling use cases |
| Calendso | Former name for Cal.com | — | — | Same as Cal.com |
| Zcal | Cloud SaaS | Proprietary | No | Simple individual pages (cloud only) |
| Cal.com + Formbricks | Platform combo | AGPL-3.0 | Yes | Booking + qualification surveys |
Prices subject to change — verify Calendly pricing at calendly.com/pricing and Liquid Web at liquidweb.com/vps-hosting/managed-vps/.
Bottom line
If you want a self-hosted Calendly replacement, Cal.com is the answer. There are no other self-hostable open-source scheduling platforms at comparable maturity. The open-source scheduling space has consolidated around Cal.com in a way that the CRM or email marketing spaces have not — meaning you're making one decision here, not choosing between five credible options.
The practical question is whether to self-host Cal.com or use Cal.com Cloud. Self-hosting makes sense when you need unlimited event types and team members without seat fees, when you need data residency (booking data on your own infrastructure), or when you want to integrate Cal.com deeply with an existing self-hosted stack (Twenty CRM, Mautic, Chatwoot).
Cal.com's self-hosted deployment is moderately complex. It requires PostgreSQL, Redis, and environment variables for calendar provider OAuth apps (Google, Microsoft), video conferencing integrations (Zoom, Google Meet), and email delivery. The community-maintained Docker Compose file works, but expect to spend 60–90 minutes on initial configuration — longer than deploying Listmonk or Plane, shorter than Keycloak. The Cal.com community forum and GitHub issues are the best support resources for self-hosted deployments.
Yes, but you need to configure your own OAuth app credentials for each provider. For Google Calendar, create a project in Google Cloud Console and set up an OAuth 2.0 client with the Calendar API scope. For Outlook, register an app in Azure Active Directory. Once configured, users connect their calendars through the Cal.com settings panel the same way they would on Cal.com Cloud.
Yes. Cal.com's Stripe integration works on self-hosted deployments — add your Stripe secret key and publishable key to the environment variables, then enable paid event types in the Cal.com dashboard. Payments are processed through your own Stripe account, so you keep the full revenue minus Stripe's standard processing fee (typically 2.9% + $0.30).