Cal.diy: open-source community edition of cal.com

All‑open Cal.diy drops in — fans cheer, others cry “rebrand” and “retreat”

TLDR: Cal.com unveiled Cal.diy, a fully open, self-hosted calendar app meant for personal use, with enterprise features removed. Commenters are split: some applaud the openness, others call it a rebrand and a pullback—especially after an email about no public Docker images and “not for enterprise” stirred the pot.

Cal.com just launched Cal.diy, a fully open, community-run version of its calendar app — MIT license, no paywall, and all the business-only features (like Teams and single sign-on) stripped out. It’s self-host only, with a big red label saying it’s for personal, non‑production use, not a managed service. One commenter even shared an email saying, “we will no longer provide public Docker images,” and “please do not use Cal.diy — it’s not intended for enterprise use,” adding fuel to the fire. Repo’s here: github.com/calcom/cal.diy.

The community reaction? Pure chaos and popcorn. Long‑timers like bluehatbrit asked if this is just the same open version with a new paint job. Critics called it a strategic retreat from serious, on‑prem business installs, with FlamingMoe calling it a “180” from last year’s blog vibes about on‑prem being more secure. Others, like OsrsNeedsf2P, think Cal.com launched Cal.diy to stay ahead of a community fork. Meanwhile, devs like swyx are hunting for simpler, cleaner alternatives—proof that “just schedule a meeting” still causes a meeting. Memes rolled in fast: “DIY now means Don’t Install Yet,” “Open source, some assembly required,” and “No Docker? Guess we’re really building character.” In short: big release, bigger feelings, maximum drama.

Key Points

  • Cal.diy is a community-driven, fully open-source fork of Cal.com with all enterprise/commercial code removed.
  • It is 100% MIT-licensed, requires no license key, and is intended for self-hosted, personal, non-production use only.
  • There is no hosted version of Cal.diy; for commercial/enterprise needs, users are directed to Cal.com’s offerings.
  • The stack includes Next.js, tRPC, React.js, Tailwind CSS, Prisma, and integrates Daily.co.
  • Setup requires Node.js >=18, PostgreSQL >=13, Yarn, and offers a Docker-based quick start with seeded test users.

Hottest takes

"Is this just a rebrand of that line?" — bluehatbrit
"Please do not use Cal.diy — it’s not intended for enterprise use." — raphaelcosta
"Wow what a 180 from just a year ago" — FlamingMoe
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.