At a Glance:
Cal.diy is a community-maintained, fully open-source scheduling platform forked from Cal.com, distributed under the MIT license with all enterprise features removed and designed for self-hosting by individuals who want a license-key-free solution.
Overview:
Cal.diy is a self-hosted, community-driven scheduling platform that serves as a fully open-source alternative to commercial scheduling solutions. It is a fork of Cal.com with all enterprise and commercial code removed, licensed entirely under MIT without any proprietary "Enterprise Edition" features. The project is built on Next.js, tRPC, React.js, Tailwind CSS, and Prisma.io, and provides calendar scheduling infrastructure that users can deploy on their own servers. It is explicitly intended for personal, non-production use and requires advanced server administration knowledge for installation and configuration. Cal.diy removes Teams, Organizations, Insights, Workflows, SSO/SAML, and other enterprise features found in the upstream project, focusing instead on providing core scheduling capabilities without requiring a license key or commercial account.
Key Decision Points:
Self-hosted only: There is no hosted or managed version—users must run Cal.diy on their own infrastructure using Docker, Railway, Northflank, Vercel, Render, or Elestio.
No enterprise features: Teams, Organizations, Insights, Workflows, SSO/SAML, and other enterprise-level features from Cal.com have been intentionally removed.
MIT-licensed with no license key: The entire codebase is MIT-licensed and works out of the box without requiring a Cal.com account or commercial license key.
Personal and non-production use recommended: The README explicitly warns against production use and recommends Cal.diy for personal self-hosting scenarios only.
Calendar integration setup required: Google Calendar, Microsoft Office 365, Zoom, and other integrations require users to obtain their own API credentials through respective developer consoles.
Core Features:
Self-hosted scheduling: Users can deploy and manage their own scheduling instance using Docker Compose with a local Postgres database.
Calendar integrations: Supports connection with Google Calendar, Microsoft Office 365/Graph, Zoom, Basecamp, HubSpot, Webex, ZohoCRM, Zoho Calendar, Zoho Bigin, and Pipedrive through API credential configuration.
Setup wizard: First-time initialization guides users through defining an initial user account and configuring the instance.
Calendar-less setup option: Users can skip connecting a calendar during setup by navigating directly to the event types dashboard at
/event-types.Optional rate limiting: Integration with Unkey is available for users who want to enable rate limiting, though it is not required for self-hosting.
Content Security Policy support: Option to enable a non-strict CSP policy via the
CSP_POLICYenvironment variable.
Use Cases:
Individuals seeking self-hosted scheduling: Users who want to run their own scheduling infrastructure without depending on a commercial SaaS provider can deploy Cal.diy on personal servers.
Developers evaluating scheduling infrastructure: Developers can use Cal.diy to explore the scheduling capabilities of the Cal.com ecosystem in a fully open-source, MIT-licensed form.
Personal calendar booking pages: Individuals who need basic appointment scheduling can set up personal booking pages with calendar integration support.
Open-Source Alternative Value:
Cal.diy provides a fully open-source scheduling platform by removing the commercial and enterprise layers from Cal.com, resulting in an MIT-licensed codebase that requires no license key or proprietary account to operate. Unlike the upstream project’s open-core model, Cal.diy contains no split between community and enterprise features—the entire available codebase runs under a single permissive license. Its self-hosting requirement means users retain control over deployment and data, though this comes with the explicit caveat that it is recommended only for personal, non-production use and demands server administration competence. The project offers a path for users who need core scheduling functionality without commercial dependencies or licensing requirements.
