Back to list
Cal.diy Launched as MIT-Licensed Open-Source Community Fork of Cal.com for Self-Hosters
Open SourceSelf-HostingOpen SourceScheduling Software

Cal.diy Launched as MIT-Licensed Open-Source Community Fork of Cal.com for Self-Hosters

Cal.diy has been introduced as a community-driven, fully open-source scheduling platform, serving as a fork of Cal.com. Unlike the original platform, Cal.diy removes all enterprise and commercial code, offering a 100% MIT-licensed solution without proprietary features. It is specifically designed for individual self-hosters who require full control over their scheduling infrastructure without commercial dependencies or license keys. The project is strictly recommended for personal, non-production use and requires advanced technical knowledge in server and database management. Built with a modern stack including Next.js, tRPC, and Prisma, Cal.diy operates entirely on user-owned infrastructure with no managed or hosted version available from the developers.

Hacker News
Share

Key Takeaways

  • Pure Open Source: Cal.diy is a 100% MIT-licensed fork of Cal.com with all enterprise and proprietary code removed.
  • Self-Hosted Only: There is no hosted version; users must manage their own infrastructure, including servers and databases.
  • Non-Production Focus: The project is strictly recommended for personal use and carries a "use at your own risk" warning.
  • Feature Set: Enterprise-only features like SSO/SAML, Teams, Organizations, and Insights are excluded to maintain a lean, open-core-free codebase.

In-Depth Analysis

A Shift to 100% MIT Licensing

Cal.diy represents a significant departure from the "Open Core" model often seen in commercial open-source software. While the original Cal.com includes proprietary enterprise features, Cal.diy is stripped of all commercial dependencies. This ensures that the entire codebase is accessible under the MIT license, removing the need for license keys or Cal.com accounts. It is positioned as a community-maintained alternative for those who prioritize software freedom and want to avoid the split between open and closed-source features.

Technical Requirements and Self-Hosting Responsibilities

Transitioning to Cal.diy requires a high level of technical proficiency. The project documentation emphasizes that self-hosting necessitates advanced knowledge of server administration, database management, and data security. Built with a stack comprising Next.js, tRPC, React.js, Tailwind CSS, Prisma.io, and Daily.co, the platform requires Node.js (v18.x or higher) and PostgreSQL (v13.x or higher). Because there is no managed service, the responsibility for securing sensitive scheduling data rests entirely with the individual user.

Strategic Distinction from Cal.com Enterprise

The developers maintain a clear boundary between Cal.diy and Cal.com's commercial offerings. Cal.diy lacks enterprise-grade tools such as Workflows, Insights, and Organizations. For users requiring commercial-ready or enterprise-ready scheduling infrastructure, the project explicitly directs them toward Cal.com’s hosted or on-premise enterprise solutions. This positioning ensures that Cal.diy serves the hobbyist and individual community without overlapping with the professional requirements of large-scale organizations.

Industry Impact

The release of Cal.diy highlights a growing demand within the open-source community for truly sovereign software that is free from commercial "upselling" tactics. By providing a version of a popular tool that is entirely community-driven and devoid of enterprise hooks, Cal.diy sets a precedent for how commercial open-source projects can offer a "community-first" branch. However, the strict "non-production" warning also underscores the risks associated with community forks that lack the dedicated security and support infrastructure of a commercial entity.

Frequently Asked Questions

Question: How does Cal.diy differ from the standard Cal.com?

Cal.diy is a fork that removes all enterprise-only features such as SSO/SAML, Teams, and Insights. It is 100% MIT-licensed, requires no license key, and is designed exclusively for self-hosting by individuals.

Question: Can I use Cal.diy for my business or enterprise?

The project documentation strictly recommends Cal.diy for personal, non-production use. For commercial or enterprise-ready needs, users are advised to use the official Cal.com hosted or on-premise services.

Question: What are the technical requirements to run Cal.diy?

Users need a server with Node.js (>=18.x) and PostgreSQL (>=13.x). Knowledge of server administration and database management is required as there is no managed version available.

Read original article

Related News

Univer by dream-num: The Unified Office Toolkit Designed for AI Agents Across Documents and Spreadsheets
Open Source

Univer by dream-num: The Unified Office Toolkit Designed for AI Agents Across Documents and Spreadsheets

Univer, an open-source project created by dream-num and featured on GitHub Trending, introduces an Office toolkit engineered specifically for AI agents. The framework consolidates six essential productivity modalities—spreadsheets, documents, slides, canvas, relational tables, and PDFs—into a single, cohesive runtime environment. By unifying these diverse document types and data formats under a shared architecture, Univer eliminates the fragmentation typically encountered when integrating multiple disparate software libraries. This single-runtime design enables autonomous AI agents to seamlessly read, generate, and manipulate complex data structures, visual layouts, and text-based documents without switching between disconnected engines or managing incompatible file formats. The release represents a major advancement in agent-ready developer infrastructure, streamlining how automated systems interact with multi-modal enterprise documents.

Claude Code Templates Surges on GitHub Trending as a Dedicated CLI Tool for Claude Code Configuration and Monitoring
Open Source

Claude Code Templates Surges on GitHub Trending as a Dedicated CLI Tool for Claude Code Configuration and Monitoring

The open-source repository claude-code-templates, authored by developer davila7, has gained widespread community traction after trending on GitHub. Built specifically as a command-line interface (CLI) tool, the project is designed to configure and monitor Claude Code workflows. As AI-assisted coding tools transition directly into terminal environments, managing configuration settings and overseeing operational behavior have become critical considerations for developers. By providing a specialized command-line utility for these exact tasks, claude-code-templates addresses the fundamental requirements of configuring AI parameters and monitoring execution details within developer environments.

Google Introduces ax: An Open Agent Orchestration Runtime Emerging on GitHub Trending
Open Source

Google Introduces ax: An Open Agent Orchestration Runtime Emerging on GitHub Trending

Google has surfaced on developer charts with the open-source repository ax, defined specifically as Google's open agent orchestration runtime. Published under Google's official GitHub organization, the project has quickly gained traction on GitHub Trending. As artificial intelligence architectures increasingly shift toward autonomous systems, orchestration runtimes play a foundational role in managing agent workflows, task execution, and interaction models. While the disclosed repository metadata currently highlights its identity as an open agent orchestration runtime without publishing exhaustive functional benchmarks or external documentation, the release reflects Google's continued engagement with open developer frameworks in the agent space. This article examines the core significance of Google's ax repository and the architectural context surrounding agent orchestration runtimes.