Booking pages and embeds, now self-hosted as Cal.diy
Cal.com is a scheduling platform. Each user sets up event types and connects their calendars, and guests book a free slot from a public page or a widget embedded on a website. For years the project billed itself as "the open-source Calendly successor".
Since April 15, 2026, Cal.com's code has been private. The public repository, renamed calcom/cal.diy, now holds only Cal.diy, a community edition under the MIT license with the commercial code stripped out. Unless you are an enterprise customer, the Cal.com you can host yourself is Cal.diy.
The comparison of open source scheduling tools puts Cal.diy next to Easy!Appointments, built around services and providers, and Rallly, which finds a common date through a poll.
MIT-licensed booking engine with CalDAV and video calls
- MIT license: you can modify the code, ship it inside a product or run it as a service without publishing your changes, which the AGPLv3 on the old repository required.
- Cal.com's booking engine: recurring, seated and paid events (Stripe, PayPal), private links, buffer times, minimum notice, booking limits, out-of-office.
- Calendars: Google, Outlook and Office 365, Apple, Exchange, Zoho, ICS feeds and CalDAV, so a self-hosted calendar server works too.
- Video calls: Jitsi, Zoom, Google Meet, Microsoft Teams, Webex, or Cal Video, which runs on the Daily.co service.
- Embedding and automation: inline, pop-up or floating-button widget, webhooks, a REST API (v2), and connectors for n8n, Make and Zapier.
- Translated interface: 44 locale folders in the repository, French among them.
Closed source upstream and no release since the split
Cal.com is no longer open source. The company announced the switch to closed source on April 14, 2026, on the grounds that AI can now scan a public codebase for vulnerabilities. Customers who self-host the enterprise edition get an invite to the private GitHub repository. The company says its production code has "significantly diverged", with major rewrites of authentication and data handling.
Paid features left the public code. Until April 2026, an AGPLv3 core sat next to two ee folders under a commercial license. Cal.diy has none, and the commercial features were removed: teams, round-robin and collective events, workflows (reminders, automations), routing forms, SAML and SCIM, the Insights dashboard, the admin panel and API v1. The feature table in the Cal.diy docs has the full list. On the hosted service, teams start at $12 per user per month (Teams plan), SAML and SCIM at $28 (Organizations plan).
Personal, non-production use, by the vendor's own account. The Cal.diy README opens with a warning: "Use at your own risk", "strictly recommended for personal, non-production use". Self-hosting, it adds, "requires advanced knowledge of server administration, database management, and securing sensitive data", and commercial use is sent to Cal.com. According to Cal.com, the repository is maintained by former Cal.com interns who became its official maintainers.
No release since the split. The latest release is v6.2.0, from March 1, 2026, which predates Cal.diy. The docs point to a calcom/cal.diy image on Docker Hub, but that image repository, created on April 14, 2026, was still empty on October 7. The code keeps moving: 99 commits from April 16 to October 7, 2026, 63 of them tagged fix and 2 tagged feat.
Installing means compiling. Cal.diy needs Node.js 18 or later and PostgreSQL 13 or later, and the Compose file adds Redis for the API v2 service. With no published image, you build your own: the README requires a database reachable during the build and DOCKER_BUILDKIT=0, and the Dockerfile lets Node's heap grow to 6,144 MB. Anonymous telemetry stays on unless CALCOM_TELEMETRY_DISABLED is set to 1.