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

Tencent Launches TeamAI-CLI on GitHub to Help Engineering Teams Transition into AI-Native Workflows
Open Source

Tencent Launches TeamAI-CLI on GitHub to Help Engineering Teams Transition into AI-Native Workflows

Tencent has published a new open-source repository titled teamai-cli on GitHub, quickly gaining traction on GitHub Trending. Centered on the core philosophy 'Make every team an AI-native team' (让每个团队都成为 AI 原生团队), the project introduces a dedicated command-line tool aimed at organizational collaboration and artificial intelligence integration. While initial public repository documentation focuses primarily on branding, identity assets, and its central mission statement, the launch highlights Tencent's expanding contribution to open-source developer tooling. This report provides an in-depth examination of the repository's initial release, the strategic significance of command-line interfaces for developer teams, the broader industry shift toward AI-native engineering environments, and what technical leaders should observe as further technical implementation details unfold.

Cathryn Lavery Releases Diagram Design: 38 Editorial-Grade HTML and SVG Diagram Formats for AI Coding Environments
Open Source

Cathryn Lavery Releases Diagram Design: 38 Editorial-Grade HTML and SVG Diagram Formats for AI Coding Environments

The open-source project diagram-design, created by cathrynlavery and currently trending on GitHub, introduces 38 editorial-grade diagram types built specifically for AI developer environments including Claude Code, Codex, and Pi. The collection is engineered using independent, self-contained HTML and SVG markup, deliberately eschewing decorative drop shadows and substandard automated diagramming output. By providing a clean, publication-ready visual structure, the repository offers developers and technical writers an alternative to rough and generic Mermaid charts. Each diagram format is designed to be fully self-sufficient and lightweight, eliminating dependencies on external rendering pipelines while maintaining aesthetic clarity. This release emphasizes structural visual communication tailored directly to modern AI-assisted coding and documentation workflows, establishing a refined standard for technical illustrations generated within developer interfaces.

Ayghri Introduces i-have-adhd on GitHub to Prevent Coding Agents from Burying Critical Answers for Neurodivergent Developers
Open Source

Ayghri Introduces i-have-adhd on GitHub to Prevent Coding Agents from Burying Critical Answers for Neurodivergent Developers

Open-source developer ayghri has released 'i-have-adhd', a dedicated skill for programming agents published on GitHub that reached the trending charts on September 11, 2026. The project directly addresses a major challenge encountered by developers using autonomous coding agents: the tendency of AI models to drown crucial solutions and instructions under extraneous conversational filler and verbose text. By enforcing an ADHD-friendly output paradigm, the skill optimizes how coding agents present responses, ensuring that primary answers and actionable technical steps remain front and center. Designed to minimize cognitive overload and support neurodivergent software engineers who struggle with excessive conversational padding, 'i-have-adhd' establishes a focused approach to AI-assisted development. This report provides an analytical overview of the project's purpose, design philosophy, industry relevance, and immediate developer utility.