21.10.2026 ВЗЛОМ САЙТА БЕЗ ПАРОЛЯ ЭКСПЛОЙТ ПУБЛИЧНЫЙ САЙТЫ АТАКУЮТ ПРЯМО СЕЙЧАС УТЕЧКА КЛИЕНТСКИХ БАЗ — ШТРАФЫ ДО 15 МЛН ₽ ПРОВЕРЬТЕ СВОЙ САЙТ ЗА 30 СЕКУНД ПРОВЕРИТЬ →
AUTOMATA.SALE Systems that bring in orders

cal.diy: what remains of Cal.com's open source

Evgeny Uryadov

This is an adapted English version. Original (Russian): automata.sale/blog/development/cal-diy-svobodnyy-planirovshchik/

cal.diy: what remains of Cal.com's open source

Cal.com spent years as one of the most visible open-source projects in scheduling: around 50,000 GitHub stars, 15,000 forks, a venture-backed company behind it, and a positioning line that promised “scheduling infrastructure for absolutely everyone”.

In April 2026 the company moved its production code into a private repository. The explanation it published reads like a sign of the times: the announcement was titled “Cal.com Goes Closed Source: Why AI Security Is Forcing Our Decision”. The argument was that open code makes it easier for AI-assisted attackers to find exploitable paths. The reaction on r/selfhosted was not enthusiastic.

The open part did not disappear. It was cut out of the commercial codebase and handed to the community as cal.diy, a separate repository under the MIT license. Seven months later it deserves a closer look: what is actually inside, what was removed, and what this fork says about the price of “open source” in 2026.

What cal.diy is

cal.diy is a self-hosted booking page: a visitor picks a slot on your calendar, confirms, and gets a video link. The Calendly pattern, except the database is yours. There is no hosted version to sign up for. You deploy it on your own infrastructure, and a setup wizard creates the first user on first launch.

The fork carries no license keys and no open-core split: the entire repository is MIT, and it works out of the box after a database migration. That alone makes it friendlier than many “community editions” that nag you about an enterprise key on every screen.

What survived the cut is a solid personal scheduler:

Feature groupIncluded in cal.diy
Eventsevent types, recurring events, seated events, paid events
Availabilityschedules, date overrides, buffer times, out-of-office
CalendarsGoogle, Outlook, Apple, CalDAV, Zoho
Video callsZoom, Google Meet, Teams, Jitsi, Cal Video (Daily.co)
Automationwebhooks, Zapier, n8n
Business systemsHubSpot, Pipedrive, Zoho CRM, Basecamp, Webex
Developer surfaceembed, API v2, API keys

What was removed

This is the more interesting list, because it shows exactly where the company drew the commercial line: teams, organizations, SAML SSO, SCIM, workflows, routing forms, the insights dashboard, the admin panel, API v1, video recordings.

Read that list again. Most of it is precisely what turns a scheduler from a personal tool into business infrastructure: a team of agents behind one booking page, corporate logins, analytics on where bookings come from, automated follow-ups. All of that stays in the paid product. cal.diy is deliberately a one-person tool, and the documentation says so in plain words: “strictly recommended for personal, non-production use”, “use at your own risk”, no security or safety guarantee from Cal.com Inc.

There is also a quieter caveat. Community contributions to cal.diy do not flow back into the production platform. The fork is a snapshot of one moment in time, maintained separately, while the real roadmap lives in the private repository.

Stack and deployment

The codebase will look familiar to anyone working with modern TypeScript stacks: Next.js and React on the front, tRPC for typed APIs, Prisma on PostgreSQL 13+, Node.js 18+, Zod for validation, Turborepo for the monorepo. Docker images exist, including ARM builds, so it runs on small ARM boxes too.

Deployment paths, from quickest to heaviest:

  • one-click installs on Railway, Northflank, Render or Elestio (hosting on Vercel requires a Pro plan);
  • docker-compose with a bundled PostgreSQL, which needs two generated secrets: NEXTAUTH_SECRET and CALENDSO_ENCRYPTION_KEY;
  • a local development setup via yarn dx that starts Postgres in Docker and seeds demo users.

Upgrades are a normal self-hosted routine: pull changes, reinstall dependencies, run the Prisma migrations. Integrations are wired through OAuth credentials in .env, one block per provider (Google, Microsoft, Zoom, HubSpot and so on). Optional extras include Unkey-based rate limiting and push notifications via VAPID keys.

Nothing exotic. Anyone who has deployed a Next.js app with a database will be through it in an evening.

The honest read

The Hacker News thread on the launch asked the sharpest question: is cal.diy 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 exactly what the project claims to be.

The honest framing is different. In April the company promised open source and delivered a free DIY tier with a narrow feature set, while the product itself went behind closed doors. Coverage of the switch describes cal.diy as thinner than the old open-source pitch, and the ecosystem reacted in kind: forks like Calnode appeared, and competitors such as SavvyCal ($5 per user per month) market directly against the gap.

None of this 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.

Who it fits

cal.diy is a good fit if you are one person who wants a booking page on your own domain, against your own PostgreSQL, without sending availability data to another SaaS. Developers embedding scheduling into their own product will find API v2 and webhooks sufficient for that job.

It is the wrong tool for 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 is the paid product. That is a fair trade, as long as you see it before you build on the free tier.

The broader lesson is not about Cal.com specifically. When a vendor closes source, the useful question is not “is the free fork good enough?” but “who owns the roadmap?”. cal.diy answers that with unusual clarity: the community owns a snapshot, the company owns the future. If scheduling is business-critical for you, that asymmetry belongs in the decision, whichever side you pick.

We run our own stack at automata.sale for the same reason: vendor promises are variables, your own infrastructure is the constant you can actually manage.

📞 +7 (906) 311-77-69 · ✉ hello@automata.sale · 💬 Telegram: @automatasale · 🌐 automata.sale

ИП Урядов Евгений Евгеньевич · ИНН 645112058391 · ОГРНИП 312645301900058 Работаем по России, Беларуси и Казахстану

Frequently asked questions

Is cal.diy free?

Yes. The entire repository is MIT-licensed, there are no license keys and no open-core split. The real costs are your server and your admin time.

How is cal.diy different from Cal.com?

It is the Cal.com codebase with all enterprise and commercial code removed: teams, organizations, SAML SSO, SCIM, workflows, routing forms, the insights dashboard, the admin panel and API v1 all stay in the paid product.

Can a company run on cal.diy?

The docs position it for personal, non-production use, and the team features are absent by design. For commercial use Cal.com points to its paid product.

Why did Cal.com close its source?

In April 2026 the company moved its production code to a private repository, citing AI-driven security risks. The open edition was spun out separately as cal.diy under MIT.

What is the tech stack of cal.diy?

Next.js, React, tRPC, Prisma on PostgreSQL 13+, Node.js 18+, TypeScript, Zod and Turborepo. Docker images exist with ARM builds, and one-click deploys are available on Railway, Northflank, Render and Elestio.