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

NixOS Support for NVIDIA DGX Spark: Enhancing AI Infrastructure with Reproducible Nix Configurations
Open Source

NixOS Support for NVIDIA DGX Spark: Enhancing AI Infrastructure with Reproducible Nix Configurations

A new open-source project, NixOS-DGX-Spark, has introduced support for Nix and NixOS on NVIDIA DGX Spark and Asus Ascent GX10 systems. This development allows AI researchers and system administrators to leverage the Nix ecosystem for managing high-performance hardware. Users can choose between running Nix on top of the standard DGX OS (Ubuntu) or performing a full NixOS installation. The project provides specialized USB images and a NixOS module tailored for these systems, including a custom kernel that ensures full GPU and Ethernet functionality. By integrating Nix, the project addresses common challenges in AI development, such as environment reproducibility and driver management for CUDA applications, while providing a declarative approach to system configuration on specialized NVIDIA hardware.

New Agent Skill Forces LLMs to Use ASD-STE100 Simplified Technical English for Clearer Documentation
Open Source

New Agent Skill Forces LLMs to Use ASD-STE100 Simplified Technical English for Clearer Documentation

A new open-source agent skill titled "SimpleEnglish" has been introduced to eliminate "AI slop" by enforcing the ASD-STE100 Simplified Technical English (STE) standard. Originally developed for the aerospace industry in 1983 to prevent maintenance errors, this controlled language ensures that technical instructions are direct and unambiguous. The tool is compatible with a wide range of AI environments, including Claude Code, Cursor, and VS Code Copilot. By applying this skill, developers can transform verbose, marketing-heavy AI outputs into precise, manual-style documentation. Empirical testing across multiple Claude models shows a significant 72.9% reduction in STE violations, marking a major step forward in standardized AI-generated technical communication.

Alibaba Open-Sources 'open-code-review': A Hybrid AI Tool for Large-Scale Code Analysis and Security
Open Source

Alibaba Open-Sources 'open-code-review': A Hybrid AI Tool for Large-Scale Code Analysis and Security

Alibaba has officially released 'open-code-review,' an open-source and free tool designed for high-precision code analysis. This tool stands out by employing a hybrid architecture that combines deterministic pipelines with LLM (Large Language Model) agents, ensuring both reliability and intelligent context-awareness. Having undergone extensive testing at Alibaba's massive internal scale, the tool provides precise line-level annotations and features built-in, fine-tuned rule sets targeting critical issues such as Null Pointer Exceptions (NPE), thread safety, and security vulnerabilities like XSS and SQL injection. Compatible with leading AI providers including OpenAI and Anthropic, 'open-code-review' represents a significant contribution to the developer community, offering enterprise-grade code quality assurance for projects of any size.