Cal.diy (self-hosted Cal.com) vs Calendly
Run Cal.diy — the MIT-licensed, community-maintained open-source edition of Cal.com — on your own EU server, and booking data stays on infrastructure you control. Compared with Calendly (Calendly, Inc., USA). Note: the hosted Cal.com service is run by Cal.com, Inc., a US company in San Francisco, and is not an EU alternative.
Your Own Booking Page vs a US Scheduling Cloud
This page compares running Cal.diy yourself — the open-source edition of Cal.com, on your own server or a VPS at an EU host such as Hetzner, OVHcloud or Scaleway — with Calendly, the scheduling service operated by Calendly, Inc. in the United States.
An important warning first. Cal.com is not a European company. Its privacy policy names Cal.com, Inc., San Francisco, as data controller and says plainly: “We’re a US company and data is processed in the United States.” Cal.com’s cloud plans offer US and EU hosting, but the service is still run by a US company and falls within CLOUD Act reach. The hosted Cal.com service is therefore not an EU alternative, and an earlier version of this page was wrong to call it German.
And a second one: open-source Cal.com, as it used to exist, is gone. In April 2026 Cal.com moved its production code to a private repository. The public repository became Cal.diy: MIT-licensed (previously AGPL 3.0), community-maintained, with all commercial and enterprise features removed. Its own README says it is “strictly recommended for personal, non-production use.”
So the honest comparison is: a self-hosted Cal.diy instance, where no vendor holds your booking data but you get an individual-scale tool with no team features, versus Calendly.
Jurisdiction Comparison
| Cal.diy (self-hosted) | Calendly | |
|---|---|---|
| Who holds your booking data | You — on your own server | Calendly, Inc. (USA) |
| Licence | MIT | Proprietary |
| Maintainers | Community team (former Cal.com interns) | Calendly, Inc. |
| CLOUD Act exposure | None from the tool — no vendor holds your data | Yes — US company |
| Hosted Cal.com service | Cal.com, Inc., San Francisco — not an EU option | — |
Feature Comparison
| Feature | Cal.diy (self-hosted) | Calendly |
|---|---|---|
| Individual booking pages & event types | ✅ | ✅ |
| Calendar & video integrations | ✅ Via app-store config | ✅ |
| Team scheduling / round-robin | ❌ Removed | ✅ Teams plan |
| Routing forms | ❌ Removed | ✅ Teams plan |
| Workflows | ❌ Removed | ✅ |
| SAML/SSO, audit logs | ❌ Removed | ✅ Enterprise |
| Recommended for production use | ⚠️ No, per the project | ✅ |
| Operating effort | ⚠️ You run it | ✅ None |
Pricing (as of October 2026)
- Cal.diy: free, MIT — your only costs are the server and your time
- Hosted Cal.com (Cal.com, Inc., US): Free; Teams $12/user/month and Organizations $28/user/month on yearly billing; Enterprise custom
- Calendly Free: one event type, one calendar connection
- Calendly Standard: $10/seat/month billed yearly
- Calendly Teams: $16/seat/month billed yearly
- Calendly Enterprise: from $15,000/year, minimum 50 seats
What Self-Hosting Really Costs
- Operations: a Node.js application plus PostgreSQL, with database upgrades before each production build, cron jobs, TLS and backups.
- Security: booking data contains names, e-mail addresses and meeting context; securing it is entirely your responsibility.
- Feature gaps: no teams, routing, workflows, insights or SSO.
- Support: a community project — the README explicitly does not recommend it for production.
Who Should Self-Host It?
Typical scenarios (generic, not named customers):
- A freelancer or consultant with technical skills who wants a personal booking page without a US service
- A developer experimenting with scheduling infrastructure or integrating booking into an internal tool
- A privacy-minded individual who already runs a home server or VPS
Calendly — or a supported scheduling service — remains the better fit for sales teams, round-robin scheduling, routing and any business-critical booking flow.
The Bottom Line
Neither Cal.com nor Calendly is European: both are US companies. The open-source escape hatch that made Cal.com attractive now lives on as Cal.diy — free, MIT-licensed and fully self-hostable on EU infrastructure, but stripped of team features and explicitly recommended only for personal, non-production use.
For individuals and technical users who want a sovereign personal booking page, self-hosted Cal.diy works. For teams and businesses, it is not a like-for-like replacement for Calendly, and the hosted Cal.com service does not solve the jurisdiction problem.
Looking for more European productivity tools? See also: n8n vs Zapier and Proton Calendar vs Google Calendar.
Frequently Asked Questions
Is Cal.com a European company?
No. Cal.com's privacy policy names Cal.com, Inc., 2261 Market Street, San Francisco, as data controller and states: 'We're a US company and data is processed in the United States.' Cal.com offers US and EU hosting for its cloud plans and has appointed an EU representative under GDPR Article 27, but the hosted service is run by a US company and is within CLOUD Act reach. Earlier versions of this page wrongly described Cal.com as German. That is why this page recommends only the self-hosted open-source edition.
What happened to open-source Cal.com?
In April 2026 Cal.com moved its production codebase to a private repository. The public repository was renamed calcom/cal.diy and became Cal.diy, a community-driven, self-hostable edition. Its licence changed from AGPL 3.0 to MIT, and commercial and enterprise features were removed. Cal.com said the move was about protecting customer data in the age of AI-driven security threats. Cal.diy is maintained by former Cal.com interns.
What is missing from Cal.diy compared with Cal.com or Calendly?
According to Cal.com's announcement, Cal.diy no longer includes Organizations/Teams, Routing Forms, Workflows, Instant Booking, AI Phone, Attributes/Segments, SAML/SSO, Insights, API v1, booking audit and impersonation. What remains is the scheduling engine, booking infrastructure and app-store framework — enough for individual booking pages, not for team round-robin or routing.
Is Cal.diy suitable for my business?
Be careful. The Cal.diy README says it is 'strictly recommended for personal, non-production use' and that self-hosting requires advanced knowledge of server administration, database management and securing sensitive data. For commercial use, the README points to the hosted Cal.com service or invitation-only on-premise enterprise access — both contracted with the US company.
What do I need to run it?
Cal.diy's installation docs list Node.js, yarn, Git and PostgreSQL; it is effectively a Next.js application. Docker deployment is documented, Linux is preferred for production, and cron jobs need to be set up separately. Integrations such as Google, Microsoft or Zoom are configured in the .env.appStore file.
Who operates Calendly and what does it cost?
Calendly is operated by Calendly, Inc., a US company whose privacy notice gives an address in Buford, Georgia. As of October 2026, Calendly's pricing page lists a Free plan, Standard at $10/seat/month and Teams at $16/seat/month when billed yearly (higher on monthly billing), and Enterprise from $15,000 per year with a 50-seat minimum.
Was this helpful?
Explore More European Alternatives
252 privacy-first, GDPR-compliant alternatives to US tech services.