Self-Hosted / Projects / Cal.diy
Cal.diy
StableSpecs verified October 1, 2026 · against vv6.2.0
Overview
Self-hosted Cal.com community edition for personal scheduling.
Cal.diy is the open-source community edition of Cal.com for people who want to run personal scheduling and booking infrastructure on their own server instead of relying on a hosted calendar service.
Why people choose Cal.diy
It covers event types, recurring bookings, availability rules, calendar integrations, conferencing links, webhooks, embeds, and API access in one scheduling application. That makes it useful for a personal booking page or a small homelab project that needs control over the deployment.
What is included
The official comparison documents Google, Outlook, Apple, CalDAV, Exchange, ICS, Zoom, Google Meet, Teams, Webex, Jitsi, webhooks, Zapier, n8n, embeds, API v2, and API keys as supported areas. Exact integrations still need their own credentials and configuration.
What to know before deployment
Cal.diy is not the same product or support tier as Cal.com. Its own documentation recommends it for personal, non-production use and says self-hosting requires advanced server administration, database management, and security knowledge. Teams, organizations, SAML, SCIM, routing forms, workflows, admin panels, and analytics insights are listed as gaps versus Cal.com.
Best fit
Choose Cal.diy when you want a personal, self-hosted Cal.com-style scheduler and accept responsibility for upgrades, database migrations, secrets, backups, and hardening. Use Cal.com or an on-prem enterprise arrangement for commercial or production-critical scheduling.
Interface previews
Screenshots of the Cal.diy interface.
Feature support
| Feature | Support |
|---|---|
| Event types and recurring bookingsThe official feature comparison lists event types, recurring event types, seated events, paid events, private links, and booking management. | Supported |
| Availability controlsSchedules, date overrides, buffer times, minimum notice, booking limits, travel schedules, and out-of-office settings are listed as supported. | Supported |
| Calendar integrationsGoogle, Outlook/Office 365, Apple, CalDAV, Lark, Feishu, Zoho, Exchange, and ICS feed calendars are listed in the official comparison. | Supported |
| Video and meeting integrationsZoom, Google Meet, Microsoft Teams, Webex, Jitsi, Cal Video, and other conferencing integrations are listed; provider credentials and setup are still required. | Supported |
| Webhooks, embeds, and API v2The comparison lists webhooks, automation integrations, embeds, API v2, API keys, and platform/OAuth clients. | Supported |
| Teams and organizationsThe official comparison marks Teams, team event types, organizations, and several enterprise scheduling controls as unavailable in Cal.diy. | Partial support |
Community signals
- Stars
- 49.2k
- Forks
- 15.4k
- Open issues
- 1.5k
- Last commit
- 3d ago
- Latest release
- v6.2.0
- Repo created
- Mar 2021
Includes open pull requests
8mo ago
Refreshed nightly from the GitHub API.
Questions
What is Cal.diy used for?
Cal.diy is used to run personal scheduling and booking infrastructure on your own server, with event types, availability rules, calendar connections, meeting integrations, embeds, and APIs.
Is Cal.diy a self-hosted Cal.com alternative?
Yes. Cal.diy is the open-source community edition spun out of Cal.com, but its documentation distinguishes it from Cal.com and recommends it for personal, non-production use.
Is Cal.diy suitable for production or commercial scheduling?
The official Cal.diy documentation says it is strictly recommended for personal, non-production use. Commercial and enterprise scheduling should use Cal.com or an appropriate on-prem enterprise arrangement.
Does Cal.diy support teams and organizations?
Not fully. The official comparison marks Teams, team event types, organizations, routing forms, workflows, and several advanced administration features as unavailable compared with Cal.com.
What does Cal.diy need to self-host?
You need a server, a supported deployment path such as Docker, a database and migrations, configured integrations, secrets, backups, and security hardening. The project documentation assumes advanced server and database administration knowledge.
What is the main tradeoff with Cal.diy?
You gain control over scheduling data and deployment, but you take responsibility for upgrades, database migrations, integration credentials, backups, security, and the limitations of the community edition.
support // the lab
Found this write-up useful?
If it saved you time or a rebuild, you can support more practical homelab guides.