Cal.diy keeps Cal.com fork open

Cal.diy is less a clean open-source victory than a compromise: Cal.com gets to harden its commercial moat while leaving hobbyists a real, but explicitly non-production, self-hosted path.

• –The MIT relicensing is generous, but the project is positioned as personal-use infrastructure with “use at your own risk” warnings, not a drop-in enterprise alternative.
• –The removed features are exactly the ones larger teams tend to need, which makes Cal.diy useful for individuals and small deployments but strategically limited.
• –The AI-security rationale will stay controversial; if AI can scan for bugs, defenders can use the same tooling, so this reads partly like security posture and partly like business model cleanup.
• –For open-source developers, the interesting part is the governance test: can a community-maintained fork keep pace once the commercial roadmap goes private?