Cal.diy

What Cal.diy does

Cal.diy is a booking-page scheduler in the Calendly mold. You define event types (a 30-minute call, a recurring session, a seated workshop), connect your calendars so busy times are blocked, and share a link where guests choose a slot. The booking lands in your calendar with a video link and email confirmations, and it can be embedded on a website inline, as a popup or as a floating button.

It is the open source continuation of Cal.com. On 15 April 2026 Cal.com announced that its production code had moved to a private repository and that the open code would carry on as Cal.diy. The old calcom/cal.com repository address now redirects to calcom/cal.diy, so the GitHub history and stars carry over. According to the announcement, Cal.diy is maintained by former Cal.com interns who are now its official maintainers, while Cal.com’s engineers work on the commercial product.

What was removed

Cal.diy is Cal.com without its enterprise code. The project lists the missing features plainly: teams and organizations, round-robin and collective team events, managed event types, routing forms, workflows (automations), instant booking, SAML SSO, insights, API v1, booking audit, impersonation and video recordings. What remains is the scheduling engine for individual hosts, the app store framework and the booking infrastructure.

That makes Cal.diy a strong Calendly replacement for one person, and a weak one for a sales or support team that relies on distributing meetings between colleagues.

License

The entire repository is under the MIT license. Before the split, Cal.com used AGPL-3.0 with a separately licensed enterprise directory; Cal.diy drops both the copyleft and the open-core split, and needs no license key.

Self-hosting Cal.diy

The project publishes a calcom/cal.diy Docker image and a Docker Compose setup that can include its own PostgreSQL database. A source install needs Node.js 18 or later, PostgreSQL 13 or later and Yarn. Before the first start you must generate NEXTAUTH_SECRET and CALENDSO_ENCRYPTION_KEY, plus VAPID keys for web push, and a setup wizard then creates the first user. If you build the image yourself, a database has to be reachable during the build.

Integrations are where most of the work lies: Google Calendar, Microsoft 365, Zoom and the CRM apps each need an OAuth app or API key that you register with the provider. Anonymous telemetry is on unless you set CALCOM_TELEMETRY_DISABLED=1. The README also lists third-party deploy templates (Railway, Northflank, Render, Elestio) and notes that Vercel needs a paid plan.

The README is unusually blunt about risk: it says “use at your own risk”, recommends Cal.diy for personal, non-production use and warns that self-hosting it requires real experience with servers, databases and protecting sensitive data. Commercial users are pointed back to Cal.com.

Hosted version

There is none. The README states that Cal.diy is self-hosted only. Cal.com’s hosted service is a separate, closed-source product, and changes made there do not flow back into Cal.diy.

Limitations

The missing team features are the main gap. Beyond that, Cal.diy is a large Next.js monorepo that takes real resources to build, and its future depends on a new community-led maintainer team rather than the company that wrote most of the code. The maintainers’ own non-production warning deserves weight before you put client bookings on it.

Who it suits

Cal.diy suits developers, freelancers and consultants who want the most complete open source booking page available, with broad calendar, video and payment support, and who are comfortable running a Node.js and PostgreSQL application. For a lighter install see Tymeslot; to find a date for a group rather than take bookings, see Rallly. The scheduling guide compares the options.