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

Meta Open Sources Code Enabling Developers to Build Custom Muse AI Hardware Gadgets
Open Source

Meta Open Sources Code Enabling Developers to Build Custom Muse AI Hardware Gadgets

Meta has officially open sourced code and software development kits that allow makers and developers to construct custom hardware gadgets powered by its new Muse AI agent. According to reports from The Verge, the release provides firmware and SDKs for accessible microcontrollers and computers, specifically off-the-shelf ESP32 boards and Raspberry Pi systems. Meta highlighted several prospective DIY builds, such as mounting Muse on ambient color E Ink screens for glanceable reminders, utilizing HDMI sticks for living room television displays, and assembling handheld touchscreen companions that echo the form factor of the upcoming Muse Charm. Alongside the open-source software release, Meta produced an initial batch of 5,000 Muse Home Link USB-C reference devices to connect the agent directly to local smart home networks.

OpenClaw Hits GitHub Trending as a Universal Cross-Platform AI Engineered for Practical Real-World Execution
Open Source

OpenClaw Hits GitHub Trending as a Universal Cross-Platform AI Engineered for Practical Real-World Execution

The open-source repository OpenClaw has achieved trending status on GitHub, catching the developer community's attention with its focus on practical artificial intelligence. Self-described as an AI capable of truly getting real work done, the project emphasizes broad operational utility across any operating system and any platform. Styled under the distinctive moniker "The Way of the Lobster" and represented by the lobster motif, OpenClaw highlights cross-platform accessibility as a primary foundation. While extensive technical specifications and architectural details remain concise within the trending repository listing, the core premise focuses directly on addressing real-world operational challenges rather than purely conversational or theoretical capabilities. This report analyzes the project's stated mission, its emphasis on universal compatibility, and its growing visibility within the open-source software ecosystem.

NVIDIA Introduces OpenShell: A Secure and Private Open-Source Runtime Built for Fleets of Autonomous AI Agents
Open Source

NVIDIA Introduces OpenShell: A Secure and Private Open-Source Runtime Built for Fleets of Autonomous AI Agents

NVIDIA has released OpenShell, a specialized, open-source runtime environment engineered to provide security and privacy for autonomous AI agents. Featured prominently on GitHub Trending, OpenShell directly tackles one of the foundational operational hurdles in deploying intelligent agents: executing automated actions, accessing data, and interfacing across systems without compromising enterprise security or exposing private infrastructure. By establishing a dedicated execution boundary, OpenShell allows developers and organizations to run autonomous workflows with rigorous isolation and governance. As artificial intelligence advances from conversational chatbots to autonomous agents capable of independent execution, runtimes that prioritize data safety, environmental isolation, and confidentiality have become paramount. OpenShell marks a critical milestone in strengthening the foundational infrastructure required to scale trustworthy agentic AI systems across modern production environments.