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

Colibri Enables Frontier MoE Model Execution on Existing Hardware with Pure C and Zero Dependencies
Open Source

Colibri Enables Frontier MoE Model Execution on Existing Hardware with Pure C and Zero Dependencies

Colibri, an open-source project authored by developer JustVugg, has surged onto GitHub Trending by offering a radically lightweight solution for running state-of-the-art Mixture-of-Experts (MoE) artificial intelligence architectures. Engineered entirely in pure C with zero external software dependencies, Colibri functions as a minimal inference engine capable of executing massive models on standard, existing consumer hardware. Instead of requiring massive allocations of high-bandwidth memory or video RAM to hold entire parameter weights simultaneously, the system streams sparse MoE expert weights directly from disk storage during inference. This paradigm drastically lowers the technical and economic barriers required to deploy frontier AI systems, demonstrating how high-performance low-level engineering can bring massive foundation models to accessible environments.

Agent Skills Launches as a Secure and Verified Skill Registry for Professional AI Coding Agents
Open Source

Agent Skills Launches as a Secure and Verified Skill Registry for Professional AI Coding Agents

As autonomous coding assistants become central to modern software engineering, security and validation have emerged as vital requirements for extending agentic workflows. The open-source project agent-skills, developed by tech-leads-club and trending on GitHub, introduces a dedicated, verified skill registry built specifically for professional AI coding agents. Designed to mitigate risks associated with untrusted extensions, the repository offers developers a safe mechanism to augment platforms such as Antigravity, Claude Code, Cursor, Copilot, and related environments. By establishing rigorous verification standards, the project enables engineering teams to deploy advanced capabilities with confidence, preventing malicious injections and system instability. This release highlights an industry-wide transition toward hardened, enterprise-ready tooling for next-generation developer environments.

PentAGI Surfaces on GitHub as an Autonomous AI Agent System for Complex Penetration Testing
Open Source

PentAGI Surfaces on GitHub as an Autonomous AI Agent System for Complex Penetration Testing

A new open-source repository titled PentAGI, developed by vxcontrol, has gained visibility on GitHub Trending as a fully automated artificial intelligence agent system designed to execute complex penetration testing tasks. The project highlights an ongoing shift toward autonomous offensive security tooling, positioning AI agents as end-to-end operators capable of handling multi-stage assessment challenges. While the initial release metadata provides concise descriptive information, the emergence of PentAGI underscores expanding industry curiosity regarding autonomous workflows in cybersecurity. This overview analyzes the stated focus of PentAGI, the broader significance of autonomous agents in security testing, and the implications of automated offensive assessment systems.