What you need
1 projectCommercial useMaintainedSetupCost
Cal.comCompareAppointment scheduling for solo operators and teams. Main commercial codebase moved closed-source; public MIT repo cal.diy is strictly recommended for personal use while Cal.com Cloud Teams lists at $12/user/mo.Commercial useSplit repoMaintainedActiveSetupModerateCost$0 solo
- Commercial use
- Split repo
- The public repository calcom/cal.diy carries an MIT License, allowing modification and deployment. However, its official README warns that cal.diy is “strictly recommended for personal, non-production use,” while commercial Teams, Organizations, Routing Forms, Workflows and SAML SSO sit in the closed-source Cal.com platform.
- Maintained
- Active
- Last push on 2026-11-13. The repository is not archived.
- Setup
- Moderate
- Self-hosting cal.diy requires Node.js >=18, PostgreSQL >=13, Yarn (or Docker for local database), random NEXTAUTH_SECRET and CALENDSO_ENCRYPTION_KEY secrets, plus manual OAuth app credentials for Google/Microsoft calendars, Zoom and Stripe.
- Cost
- $0 solo
- Self-hosting cal.diy has zero license fees beyond your Linux VPS and Postgres database. Cal.com Cloud pricing (checked November 15, 2026): Individuals $0/month (unlimited event types, multiple calendars, workflows, Stripe), Teams $12/user/month billed annually ($15 monthly), and Organizations $28/user/month billed annually ($37 monthly, adding SAML SSO and SCIM).
- What to watch out for
- Many older guides assume self-hosting Cal.com unlocks free team scheduling. Today cal.diy omits multi-team routing, enterprise SSO and managed workflows, and the README explicitly advises using hosted Cal.com or licensed on-prem access for commercial workloads.
Your industry is not here?
Tell me the industry and what you need solved. I will look at it next.