Cal.com adopts restrictive licensing model

This shift shows Cal.com is turning open source from a top of funnel growth engine into a controlled upsell path for larger customers. The old model let developers self host and customize scheduling for free, then convert some teams into paid SaaS. Moving the main repo private while keeping cal.diy public preserves community distribution, but makes the most commercially useful code and roadmap harder for enterprise free riders to copy into production products.

• The closest pattern is HashiCorp in August 2023, Elastic in January 2021, and Redis in March 2024. In each case, the company kept source access in some form, but changed terms so cloud hosts and large commercial users could not package the product into competing services without paying.
  2 hashicorp 3 elastic 4 redis
• For Cal.com, the business logic is especially direct because self hosted scheduling is not just a hobby use case. Marketplaces, telehealth platforms, and other embedded booking products can run large booking volumes on top of the codebase, which makes unpaid commercial usage more costly than a typical developer tool fork.
  1 sacra 5 cal
• The tradeoff is familiar too. License tightening usually reduces goodwill with part of the developer community, but it can improve monetization if the company is already winning more deals through enterprise controls, hosted APIs, and usage based pricing than through pure open source adoption alone.
  1 sacra 2 hashicorp 3 elastic 4 redis 5 cal

From here, Cal.com is likely to look more like an infrastructure vendor than a community software project. The center of gravity moves toward proprietary API features, enterprise packaging, and AI powered booking workflows, where the company can charge on volume and usage instead of hoping open source users eventually convert.