
Cal.com is going closed source with a major shift in its license strategy
The scheduling platform Cal.com has launched v6.4, introducing a major shift in its open source license model. Citing the growing impact of AI coding tools and the risks of exposing public code, the company is moving its commercial edition to a "closed source" model after previously offering it as "source-available". At the same time, all free and open source code is being relaunched as Cal.diy under the MIT License, creating a more permissive community edition for self hosting. Cal.com says Cal.diy will remain free for hobbyists and community users, along with setup instructions, although it notes that self hosted use is at the user’s own risk.
For enterprise customers who self host, access to the commercial edition will now be handled through a private GitHub repository. Cal says the licensing update does not change product or account access for existing users and is mainly a change to its open source license and code availability.
Beyond that, v6.4 also improves performance for large organizations, with the bookings page and event type configuration now loading much faster, in some cases by up to 20 times. The release also brings several workflow and security updates, including a new routing trace for round robin host selection, more advanced Salesforce ownership routing, support for OAuth secret rotation and multiple redirect URIs, and a fix for a double booking issue caused by concurrent confirmations. You can check all the other improvements and bug fixes in the official release notes here.



Comments
Since AI can find ancient bugs, going close source won't help much. Anyway, let's fork this and let's find and fix those bugs.
The ability of AI to find any bug is exaggerated, like any LLM hype. LLM is just a tool. Without an experienced debugger, it is not a solve-all solution.
AI can find buried bugs, but the vibe coding that is currently causing an avalanche of bad issues and code mergers outweighs that 10:1. Plus the AI code that does get merged into projects does more harm than good.
Damn, LET "sudo pop -rf AI-bubble" Happen Already!
Looking forward to the open source alternative
I guess LLM are really killing open source afterall...
From what I read, it would make maintaining OSS more difficult. OSS will need to be coded to prevent easy LLM copy/modify/paste (they call it "AI-resistant code").