Self-Host Cal.com: Calendly Alternative Scheduling 2026

TL;DR verdict

Cal.diy is useful for personal, non-production use, learning, and tightly bounded evaluation. Its current README explicitly recommends that boundary. For revenue, recruiting, support, SLA, compliance, or other commercial production scheduling, evaluate hosted Cal.com or Cal.com's on-premise Enterprise product instead. Calendly remains the simpler hosted choice when its workflow and plan boundaries fit.

The public Cal.diy repository is MIT-licensed and does not require a self-host license key. That does not make it equivalent to hosted or Enterprise Cal.com: the community repository says Teams, Organizations, Insights, Workflows, and SSO/SAML are not included.

Key takeaways

Use boundary: Cal.diy is recommended by its maintainer for personal, non-production use.
License boundary: The community repository is MIT-licensed, but commercial and enterprise code has been removed.
Current hosted pricing: As checked on 2026-08-20, Cal.com lists Teams at $12 per user/month billed annually and Organizations at $28 per user/month billed annually; Enterprise is custom.
Calendly pricing: Calendly lists Standard at $10 per seat/month billed annually. Its current pricing page does not support the former fixed $15,000 Enterprise floor, so treat Enterprise as custom/contact sales.
Operations still matter: A Cal.diy lab needs Docker, database and secret configuration, email, calendar OAuth, backups, updates, and monitoring.

At-a-glance decision table

Situation	Path to evaluate	Reason	Boundary
Personal booking page, learning, or a non-production lab	Cal.diy	MIT-licensed code and a Docker path	Do not infer hosted or enterprise feature parity
Team scheduling in production	Hosted Cal.com Teams or Organizations	Vendor-operated service and published team plans	Confirm current plan features and annual billing
SSO, compliance, SLA, procurement, or on-premise requirements	Cal.com Enterprise or Calendly Enterprise	Contract and support surface	Pricing and commitments are custom
Simple hosted booking links	Calendly Free or Standard, or hosted Cal.com	No application operations	Plan gates and vendor roadmap apply

License and open-source status box

Surface	Current evidence	Practical implication
Cal.diy repository	MIT license; no license key; personal, non-production recommendation	Suitable for study and bounded evaluation; not vendor-endorsed commercial production
Removed community features	Teams, Organizations, Insights, Workflows, and SSO/SAML	Test nothing by assumption; these are explicit product-boundary gaps
Hosted Cal.com	Free, Teams, Organizations, and Enterprise plan surfaces	Vendor operates the service; plan gates apply
Cal.com Enterprise	Commercial/on-premise offering	Use this surface for production requirements that exceed the community boundary

MIT answers a licensing question. It does not answer whether a deployment has the support, features, security review, or operating ownership needed for a business-critical booking flow.

Hosted vs self-hosted table

Capability	Hosted Cal.com	Cal.diy evaluation instance	Calendly
Service operation	Vendor-managed	You operate the application and dependencies	Vendor-managed
Source/license	Commercial service with public OSS roots	MIT community code	Closed-source service
Team and organization features	Available by plan	Named features removed from the community repository	Available by plan
OAuth and email	Vendor-managed integrations	You configure and test providers	Vendor-managed integrations
Support and SLA	Plan or contract surface	Community documentation; no implied production support	Plan or contract surface
Custom pricing	Enterprise contact sales	Infrastructure and labor are yours to model	Enterprise contact sales

Deployment model table

Model	Appropriate use	What you own	Note
Local Docker Compose	Learning and evaluation	Containers, data, secrets, and local access	The repository documents Docker; this does not change its non-production recommendation
Isolated internal lab	Feature and integration testing	Access controls, test data, callbacks, and teardown	Do not use production customer data without a separate review
Hosted Cal.com	Production team scheduling	Account, users, integrations, and governance	Teams and Organizations have published annual prices
Cal.com on-premise Enterprise	Commercial self-managed requirements	Contract plus infrastructure responsibilities	Confirm support, licensing, and exact feature scope with sales

Evidence cards

Repository boundary. The current Cal.diy repository says it is intended for personal, non-production use and directs commercial or enterprise scheduling to hosted Cal.com or the Enterprise offering. The same README identifies the features removed from the community code.

License boundary. The repository publishes an MIT license and states that no license key is needed. Check the exact commit, included paths, third-party dependencies, and deployed image during a compliance review.

Pricing boundary. Cal.com pricing lists Teams at $12 per user/month annually and Organizations at $28 per user/month annually. Calendly pricing lists Standard at $10 per seat/month annually. Both were checked on 2026-08-20; re-check before procurement.

Docker boundary. Docker is a documented way to run Cal.diy for evaluation. It is not evidence that the community build is supported for a production commercial workflow.

Evaluation Docker path

Use an isolated lab, test identities, and non-production calendar data.

Clone the current repository and pin the commit you are evaluating.
Copy the environment example and create strong local secrets.
Configure the database, email, and calendar OAuth callbacks for the lab domain.
Start the Docker stack and inspect logs before creating test event types.
Test booking, cancellation, rescheduling, conflict detection, and email delivery.
Record which required hosted features are missing.
Tear down the lab or retain it under an explicit owner and patch schedule.

git clone https://github.com/calcom/cal.diy.git cal-diy
cd cal-diy
cp .env.example .env
# edit the lab-only values before first boot
docker compose up -d

Calendar, email, and OAuth caveats

Use test calendars and accounts until the data path and access model are approved.
Verify Google and Microsoft login separately from calendar synchronization.
Send confirmations to an external test mailbox; a successful booking page does not prove deliverability.
Treat video, payment, webhook, and marketplace integrations as separate tests.
Do not assume a hosted Cal.com workflow exists in Cal.diy simply because the names or concepts are familiar.

Maintenance burden

Area	Lab owner action	Risk if skipped
Updates	Review upstream changes before refreshing the pinned commit	Tests may describe a stale build
Data	Use disposable or backed-up test data	Evaluation state can be lost or leak into later tests
Email/OAuth	Monitor callbacks and provider credentials	Booking tests can appear to pass while integrations fail
Security	Restrict exposure and keep secrets outside Git	A lab can become an unintended public service
Product boundary	Re-read the repository warning and removed-feature list	Evaluation findings may be mistaken for production approval

Migration checklist

Before moving any production Calendly workflow, evaluate a supported production product rather than promoting the Cal.diy lab.

Inventory event types, routing rules, calendars, reminders, payments, webhooks, embeds, and owners.
Mark requirements that depend on Teams, Organizations, Insights, Workflows, or SSO/SAML.
Compare those requirements with hosted Cal.com, Cal.com Enterprise, and Calendly plan documentation.
Test the supported target with non-production users and calendars.
Verify conflict checks, cancellation, rescheduling, email, and time-zone behavior.
Keep old links available during a staged cutover.
Name the owner for rollback, vendor support, and incident response.

For a workflow-focused companion, use How to Migrate from Calendly to Cal.com.

Cal.com vs Calendly cost model

Fill this model with your own seat count, contract quote, infrastructure, and labor. Do not equate a no-key community build with zero total cost.

Cost category	Calendly	Hosted or Enterprise Cal.com	Cal.diy lab
Published self-serve price	Standard: $10/seat/month annually	Teams: $12/user/month annually; Organizations: $28/user/month annually	No self-host license key
Enterprise price	Custom/contact sales	Custom/contact sales	Not the supported commercial production surface
Infrastructure	Included	Included for hosted; clarify on-premise contract	Your lab compute, storage, email, and monitoring
Operations	Account administration	Account or on-premise administration	Your engineering time
Missing-feature cost	Plan-dependent	Contract-dependent	Explicit community feature removals must be accounted for

Methodology

This revision uses current first-party material checked on 2026-08-20. The Cal.diy repository controls the community-use and feature-removal boundary. Official Cal.com and Calendly pages control current pricing. We did not infer production readiness from license, Docker support, repository activity, or a successful local boot.

Pricing should be checked within 30 days. Re-check the repository README, license, and product boundary before each material evaluation.

Source-backed FAQ

Is Cal.diy open source?

The current community repository is MIT-licensed and does not require a license key. That does not include the removed commercial and enterprise code or features.

Can I use Cal.diy for a production company scheduling system?

The repository strictly recommends personal, non-production use. Evaluate hosted Cal.com or Cal.com Enterprise for a commercial production deployment.

Does Docker support prove production readiness?

No. Docker describes a deployment mechanism. It does not supply an SLA, support contract, security review, or the removed team and enterprise features.

Does self-hosting eliminate scheduling costs?

No. Even a no-key evaluation build requires infrastructure and operator time. A production decision must also price missing features, support, incident response, and compliance work.

When should I choose Rallly instead?

Use Rallly when the primary job is polling a group for a time. See Rallly vs Cal.com and Migrate Doodle to Rallly or Cal.com.

Sources

Cal.diy repository, accessed 2026-08-20.
Cal.com pricing, accessed 2026-08-20.
Calendly pricing, accessed 2026-08-20.

The SaaS-to-Self-Hosted Migration Guide (Free PDF)