cal.diy: what actually remains of Cal.com's open source
I spent an evening with cal.diy: the repo, the docs, the launch thread. Here's my read. Cal.com spent years as one of the most visible open-source projects in scheduling. Around 50,000 GitHub stars, 15,700 forks, a ventu
I spent an evening with cal.diy: the repo, the docs, the launch thread. Here's my read.
Cal.com spent years as one of the most visible open-source projects in scheduling. Around 50,000 GitHub stars, 15,700 forks, a venture-funded company behind it, a positioning line that promised scheduling infrastructure for absolutely everyone.
In April 2026 the company moved its production code into a private repository. The announcement was titled "Cal.com Goes Closed Source: Why AI Security Is Forcing Our Decision". The argument: open code makes it easier for AI-assisted attackers to find exploitable paths. Reddit's r/selfhosted did not take it well.
The open part survived as cal.diy, MIT licensed, community maintained. Seven months in, it's worth an engineer's look, because the split tells you exactly where a vendor draws the commercial line. I went through the repo, the docs and the launch thread, and here's what I found.
What is inside the fork
It's a self-hosted booking page. A visitor picks a slot on your calendar, confirms, gets a video link. The Calendly pattern, except the database is yours. No hosted version, no signup, no license key: you deploy it, run the wizard, create the first user.
What I found inside:
- event types, recurring events, seated events, paid events
- availability schedules, date overrides, buffer times, out-of-office
- calendar sync: Google, Outlook, Apple, CalDAV, Zoho
- video: Zoom, Google Meet, Teams, Jitsi, Cal Video (Daily.co)
- automation: webhooks, Zapier, n8n
- CRM and messaging: HubSpot, Pipedrive, Zoho CRM, Basecamp, Webex
- developer surface: embed, API v2, API keys ## What was removed, and why that matters Teams. Organizations. SAML SSO. SCIM. Workflows. Routing forms. The insights dashboard. The admin panel. API v1. Video recordings. That's not a random feature list. It's precisely the set of capabilities that turns a personal scheduler into business infrastructure: a sales team behind one booking page, corporate identity, measurement of where bookings come from, automated follow-ups. All of it stays in the paid product, and I don't think that's an accident. The documentation is unusually blunt about the consequences: strictly recommended for personal, non-production use, use at your own risk, no security or safety guarantee from Cal.com Inc. You can't say they hid it. There is one more caveat that rarely appears in launch coverage: community contributions to cal.diy do not flow back into the production platform. The fork is a snapshot of one moment, maintained separately. The real roadmap lives in the private repository. ## Stack and deployment Familiar modern TypeScript stack: Next.js, React, tRPC for typed APIs, Prisma on PostgreSQL 13+, Node.js 18+, Zod, Turborepo. Docker images exist, including ARM builds. Deployment options, quickest first:
- one-click on Railway, Northflank, Render or Elestio (Vercel needs a Pro plan)
- docker-compose with a bundled PostgreSQL; you generate NEXTAUTH_SECRET and CALENDSO_ENCRYPTION_KEY
- local development via
yarn dx, which starts Postgres in Docker and seeds demo users Upgrades are routine self-hosting: pull, reinstall dependencies, run the Prisma migrations. I've done this dance on enough Next.js boxes to know it's boring in the good way. Integrations are wired through OAuth credentials in.env, one block per provider. Optional extras: Unkey-based rate limiting, VAPID keys for push. Nothing exotic. If you've shipped a Next.js app with a database, this is an evening. ## The honest read The Hacker News thread asked the sharpest question: is this anything more than a rebrand of the community edition that already existed? Functionally, the answer leans toward the same code with the commercial parts amputated, which is also what the project itself says it is. The more useful framing is about ownership. In April the company promised open source and delivered a free DIY tier with a narrow feature set, while the product went behind closed doors. Forks like Calnode appeared, competitors such as SavvyCal at $5 per user per month market directly against the gap. None of that makes cal.diy a bad project. It makes it a bounded one. The code is real, the license is liberal, the docs are honest about the limits. What changed is the promise: open source here no longer means the roadmap is public. It means the snapshot is public. I'd run cal.diy on my own domain tomorrow. I wouldn't build a company on it. ## Who should use it One person who wants a booking page on their own domain, against their own PostgreSQL, without sending availability data to another SaaS. If that's you, you'll be fine. Developers embedding scheduling into a product will find API v2 and webhooks enough for the job. Not a company. No teams means no shared booking pages for a sales or support org. No SSO means no corporate identity. No insights means no measurement. In those cases the vendor has one answer, and it's the paid product. I'd take that trade seriously before building anything on the free tier. The general lesson isn't about Cal.com. When a vendor closes source, I'd ask who owns the roadmap, not whether the free fork is good enough. cal.diy answers that with rare clarity: the community owns a snapshot, the company owns the future. --- This article was prepared with AI assistance (drafting and adaptation) and reviewed by the author before publishing. Originally published at https://automata.sale/en/blog/development/cal-diy-open-source-scheduling/ tags: opensource, selfhosting, webdev, nextjs
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.