Comparison

Tymeslot vs Cal.com

Cal.com announced in 2026 that it is going closed-source: new versions are proprietary, and the only free self-hostable option is now cal.diy, a separate MIT fork scoped to personal use. Tymeslot is open source and self-hostable, with the complete product in every install.

Cal.com went closed-source in 2026
Tymeslot is open source
Flat pricing, not per-seat
Luka Breitig, Software Engineer & AI Developer
Luka Breitig

Updated September 15, 2026

The short version

Tymeslot or Cal.com?

Until 2026, Cal.com was the best-known open-source scheduler - AGPLv3 open core and self-hostable, with a deep API. That changed: Cal.com moved its production code closed-source (v6.2, from March 2026, was the last AGPL release), so new versions are proprietary. The free self-hostable option is now cal.diy, a separate MIT community fork scoped to personal, non-production use that drops teams, organisations, SSO, workflows and routing forms. Tymeslot is the open-source alternative that keeps what people came to Cal.com for: self-hostable end to end, CalDAV-first, EU-based, one Elixir app plus Postgres, flat pricing, and the complete product free to self-host.

Side by side

Tymeslot vs Cal.com, feature by feature

The differences that tend to matter when you're choosing between them.

Starting paid price
Tymeslot: Pro €9/mo flat (free plan available)
Cal.com: Teams $12/user/mo (billed annually)
Free plan
Tymeslot: Unlimited event types & calendars
Cal.com: 1 user - unlimited event types & calendars
Licence
Tymeslot: Open source (GNU AGPLv3), free to self-host
Cal.com: Closed-source from 2026 (v6.2 was the last AGPL); free self-host only via cal.diy (MIT, personal use)
Self-hosting
Tymeslot: Yes - full product, one container + Postgres, ~5-min setup
Cal.com: cal.diy only (MIT, hobbyist/non-production); production Cal.com self-host is proprietary
Generic CalDAV sync
Tymeslot: Yes - first-class
Cal.com: Yes - a CalDAV app, still in beta
EU data residency
Tymeslot: Yes - hosted in the EU (Germany), or self-host
Cal.com: cal.eu closes on 1 November 2026; after that, self-host cal.diy
Pay-to-book (Stripe)
Tymeslot: Pro, or free when self-hosted
Cal.com: Yes (free plan and up)
Booking themes
Tymeslot: Quill & Rhythm, two distinct designs - no code
Cal.com: Highly customisable, more developer-oriented
Interface languages
Tymeslot: 6 - English, German, French, Italian, Ukrainian, Czech
Cal.com: Many (community translations)
Best fit
Tymeslot: People who want it to just work
Cal.com: Developers building on a scheduling API
Trackers on the booking page
Tymeslot: Our own self-hosted, cookieless analytics (Umami); one session cookie
Cal.com: Sentry error tracking only, no analytics; 3 cookies

Tested on September 15, 2026: we loaded Cal.com's own demo booking page and a Tymeslot booking page in a fresh browser, without accepting any cookies, and recorded every host contacted. The Cal.com demo page

Sources: Cal.com pricing Cal.com is going closed source What was removed from cal.diy The cal.diy repository Cal.com CalDAV app (beta) cal.eu closing on 1 November 2026

Where Tymeslot pulls ahead

What you gain by switching

⚙️

Simpler to run

Tymeslot is a single Elixir/Phoenix app plus Postgres: one container, a five-minute setup, sensible defaults. Self-hosting Cal.com means running its full Next.js stack and infrastructure.

Simpler to use

Tymeslot is built for non-technical users: set up event types and a booking page without touching code. Cal.com is developer-first, with a steeper learning curve.

⚖️

Flat pricing, not per-seat

Tymeslot Pro is a flat €9/month, and self-hosting is free with full feature parity. Cal.com's managed plans are billed per user, so cost grows with your team.

💻

The full product when you self-host

Tymeslot's self-hosted build ships the complete product: payments, automation, themes, embeds and i18n, with nothing gated. Cal.com's own production code is now closed-source, so the only free self-host route is cal.diy.

⚖️

The free fork is missing what teams need

cal.diy, the MIT community fork, is scoped to personal, non-production use and drops teams, organisations, SSO/SCIM, workflows, routing forms and analytics. Tymeslot self-hosts the whole product for free.

👥

Profession-tuned out of the box

Tymeslot ships ready-made booking flows and guidance for specific professions - coaches, therapists, photographers and more - rather than a blank, build-it-yourself platform.

🔐

No third-party trackers

Tymeslot booking pages load no advertising pixels or third-party analytics: visits are counted by our own self-hosted, cookieless analytics, and connected calendars only ever expose busy/free - never event details.

Our take

Tymeslot or Cal.com - the real differences

For a long time this was the comparison where the headline differentiators cancelled out: both open source, both self-hostable, both CalDAV, both EU. That stopped being true in 2026. Cal.com moved its production code closed-source, so new versions are proprietary, and the only free self-hostable option is now cal.diy - a separate MIT fork scoped to personal use that drops teams, organisations, SSO, workflows and routing forms. Cal.com is also closing cal.eu, its EU-hosted cloud, on 1 November 2026.

So the four things people came to Cal.com for no longer all hold. Tymeslot keeps every one of them: open source under the GNU AGPLv3 - the same licence Cal.com left behind - self-hostable end to end with the full product included, CalDAV as a first-class provider, and EU hosting or self-host anywhere. On top of that it is the smaller stack (one Elixir app and Postgres), a five-minute setup, and flat pricing instead of per-seat.

Choose Cal.com, or its paid cloud, if you want its developer platform and large API and don't mind a proprietary production codebase. Choose Tymeslot if you want scheduling you can still self-host in full, for free, with your data and the source in your hands.

The verdict

Which one is right for you?

No tool wins for everyone. Here's how they split.

Choose Tymeslot if…

  • You want open-source scheduling that's simple to run and simple to use
  • You prefer flat pricing over per-seat billing
  • You want every feature included when self-hosting - nothing behind a separate licence
  • You're not a developer and don't want to build on an API to get going

Choose Cal.com if…

  • You're an engineering-led team that wants a deep scheduling API to build on
  • You need Cal.com's extensive app store and routing/workflow ecosystem
  • You want Cal.com's large ecosystem and are fine with a proprietary production codebase (or the personal-use cal.diy fork)
Pricing

What each one costs

Tymeslot

  • Self-hosted Free - full feature parity
  • Cloud Free €0 - unlimited event types & calendars
  • Cloud Pro €9/mo (€90/yr) - automation & payments

Cal.com

  • Free $0 1 user, unlimited event types & calendars
  • Teams $12 per user / mo, billed annually ($16 monthly)
  • Organizations $28 per user / mo, billed annually ($37 monthly)
  • Enterprise Custom annual contract
  • cal.diy (self-host) $0 MIT community fork, personal use; missing teams, SSO and workflows

Cal.com pricing in USD. Per-user tiers shown at the annual rate; month-to-month is higher. Cal.com moved to closed source in April 2026; v6.2 was its last AGPL release. Prices checked on September 15, 2026. Tymeslot prices in EUR; VAT may apply. See Cal.com's current pricing

Migration

Switching from Cal.com to Tymeslot

1 Recreate your event types in Tymeslot - same concepts (durations, availability, buffers), set up in minutes.
2 Connect your Google, Outlook or CalDAV calendar for two-way sync.
3 Point your booking links at Tymeslot wherever you share them.
4 Self-host via Docker, Cloudron or Railway for a lighter stack, or use the managed cloud.
FAQ

Tymeslot vs Cal.com - common questions

Is Tymeslot or Cal.com easier to self-host?

Tymeslot is the lighter option: a single Elixir/Phoenix app plus PostgreSQL, deployable via Docker, Cloudron or Railway in roughly five minutes, with the full product included. Cal.com's production code is now closed-source, so the free self-host route is cal.diy (MIT, personal use), which runs the full Next.js stack and leaves out teams, SSO and workflows.

Is Cal.com still open source?

Not for its production product. In April 2026 Cal.com moved its production codebase closed-source; v6.2 was the last AGPL release, and newer versions are proprietary. The remaining free, self-hostable option is cal.diy, a separate MIT community fork scoped to personal, non-production use that drops teams, organisations, SSO, workflows and routing forms. Tymeslot's core is open source under the GNU AGPLv3 - the same licence Cal.com just left - free to use, self-host, modify and redistribute, with share-alike the only obligation, and its self-hosted build ships the whole product with nothing gated.

How does pricing compare?

Tymeslot Pro is a flat €9/month (€90/year) regardless of team size, with a free plan and free self-hosting. Cal.com's managed plans are billed per user ($12/user/mo Teams and up, billed annually), so cost scales with headcount.

Do both support CalDAV calendars?

Yes, though not to the same degree. Cal.com offers a CalDAV app, still marked beta, verified with servers such as Nextcloud, Radicale and Baïkal. Tymeslot treats CalDAV as a first-class provider alongside Google and Outlook, with guided setup for Nextcloud, Radicale, Baïkal, Zimbra, mailbox.org and Apple iCloud.

Which should a non-technical user pick?

Tymeslot. It's built so anyone can set up event types and a booking page without code, and ships profession-tuned booking flows out of the box. Cal.com is developer-first, with a steeper learning curve.

From the blog

All posts
Read Why I built Tymeslot
Why I built Tymeslot
product open-source

Why I built Tymeslot

I put out the first version of Tymeslot two days ago. I built it because the scheduling tools I tried were either dated or too heavy to run myself.

Luka Breitig January 04, 2026 · 3 min read

Ready to switch?

Free plan available. No credit card required. Setup in 5 minutes.

No credit card required
Open source & self-hostable
Privacy-first