Calendly → Cal.diy
What it saves, what actually moves, what you rebuild — and the thing that catches people.
What it costs, and what it saves
Calendly Standard is about $12/user/month. Cal.com self-hosted is free — a container and a database.
Moves cleanly
Nothing automatically. Event types are quick to recreate.
You rebuild
Event types, availability rules and integrations.
What Calendly costs you today
Free tier covers one event type and basic scheduling. Paid plans run Standard $10/seat/mo, Teams $16/seat/mo, and Enterprise custom pricing (billed annually); most integrations, workflows, and team routing sit behind paid tiers.
What actually holds you in
Booking history, availability rules, and integration configs live in Calendly's cloud; there's no first-party bulk export of scheduled-meeting data, and event-type setups don't port to another platform, so switching means rebuilding your booking pages elsewhere.
What you are moving to
Cal.diy is the free, permissively-licensed fork Cal.com released in April 2026 after taking its commercial product closed-source. It carries over Cal.com's core booking engine — event types, buffer/booking-limit rules, Stripe/PayPal payments, and calendar/video integrations — under the MIT license, but the maintainers themselves describe it as community-maintained and recommend it for personal, non-production use rather than as a supported business tool.
Free, self-hosted. No official managed hosting or support channel; Cal.com's paid hosted product is a separate, now closed-source, offering.
Cal.diy strengths
- Fully MIT-licensed — no open-core split, no feature paywall, free to modify or redistribute
- Inherits a feature-rich booking engine: recurring events, seated events, payments, wide calendar/video integration list
- REST API and embeddable booking widgets for building your own booking flow
- Active repo (46k+ stars, commits within days) even post-fork
What you give up
- Its own docs recommend it for personal use only and disclaim production readiness — 'use at your own risk'
- No official support; the parent company no longer backs this codebase
- Missing team/organization features, SSO/SAML, workflows, and routing forms that stayed in Cal.com's closed-source enterprise edition
- Requires running Postgres + Redis + a Node.js host yourself — more moving parts than a single-binary app
- Young as an independent project (forked April 2026); long-term maintenance commitment is unproven
The migration, step by step
- 1Deploy Cal.com with docker compose and Postgres
- 2Connect calendars via Google or Microsoft OAuth — this needs your own OAuth app, which is the fiddly part
- 3Recreate event types and availability
- 4Set up a video integration; Cal.com supports Zoom, Meet and Jitsi
- 5Redirect your Calendly link to the new one rather than deleting it, since it is in email signatures everywhere
The gotcha
Self-hosted Cal.com requires you to create and maintain your own OAuth credentials for every calendar provider. That is the step that stalls most installs, and it is not obvious from the quickstart.
When to stay on Calendly
You want zero setup and the seat cost is not painful — this is a migration where the saving is small and the fiddle is real.
More Layer 5 migrations
Figures verified 2026-07-09 against vendor pricing pages. Prices change and migrations differ by estate — treat the cost delta as a starting model, not a quote. Rankings and recommendations here are merit-only; affiliate income never changes a verdict. See our methodology.