A Calendly alternative you own

Booking pages that read your calendars from your own servers, with every booking kept in your database and no fee per person.

Starter from CHF 449EUR 479USD 559 a month for one app in Pilae Cloud; Business from CHF 1,590EUR 1,690USD 1,990 for up to three on your own servers.

  • Scheduling
  • Business
  • On-prem or your region

Replace CalendlyStep-by-step guide

FromCalendlyCalendly LLC

  1. Inventory
  2. Parallel run
  3. Cutover
To

Cal.com, operated by Pilae

The step-by-step guide

Why teams leave Calendly

Your calendar says a lot

A scheduling tool reads every free and busy slot of everyone who uses it, and keeps the name and email of everyone who books. With Cal.com on your machines, that stays with you.

Booking pages on your domain

Booking links live under your own domain, and every booking is written to your Postgres in the country you chose.

No licence fee per person

Cal.diy is MIT-licensed, with no fee per user. Giving a colleague a booking page means creating an account, not changing a plan.

Calendly vs Cal.com operated by Pilae

Checked against calendly.com.

What is being comparedCalendlyPilae
Where bookings are storedIn Calendly infrastructure, operated by Calendly.In your Postgres, on your premises or on dedicated machines in any of 10+ Pilae Cloud regions, six of them in Switzerland and the EU.
Event typesOne-on-one, group, round-robin and collective events, routing forms and workflows.Personal event types with buffers, questions and availability rules. Round-robin, collective events, routing forms and workflows are not in Cal.diy.
CalendarsGoogle, Microsoft 365 and Outlook, and iCloud calendars.Google, Microsoft 365 and Outlook, and any CalDAV server, including Nextcloud.
Video and integrationsZoom, Google Meet, Teams and Webex links, a wide set of CRM and marketing integrations.Zoom, Google Meet, Microsoft Teams, Daily or Webex links, webhooks and an API, plus n8n beside it for CRM updates and follow-ups.
Sign-onSAML single sign-on on the higher plans.Local staff accounts, with the admin side reachable only on your private network. SAML sign-in is in the commercial Cal.com product, not in Cal.diy.
Pricing modelA free tier, then per seat, per month, by plan.A monthly price per app, published for Starter and Business. Cal.diy itself has no licence fee.
OperationFully run by Calendly as a SaaS product.Daily encrypted backups, planned upgrades by the Pilae Agent, 60-second probes, and on Enterprise a restore test every month.

Self-hosted scheduling

Calendly is simple and it works, which is why it spreads through an organisation one seat at a time. Each of those seats connects a calendar to a service outside your perimeter, and each booking leaves a name and an email there.

Cal.com does the core of the job: personal booking pages connected to Google, Microsoft or CalDAV calendars, with a video link and a confirmation email for each booking. What we deploy is Cal.diy, the MIT-licensed edition Cal.com, Inc. publishes. It covers individual scheduling well; team rotations and routing forms are in the commercial product only. Pilae deploys it on your premises or on dedicated machines in any of 10+ Pilae Cloud regions, six of them in Switzerland and the EU. Booking pages are public by design; the admin side is reachable only through the private network.

Moving off Calendly

The work is in the inventory: who books meetings, which event types they use and where the links are published. We check team scheduling first, connect the calendars, replace the links and keep Calendly open until new bookings have stopped arriving there. The move is part of our fixed-price migration.

After the switch, the Pilae Agent plans each Cal.diy upgrade, waits for your approval and applies it in your window. Pricing is per app and published for Starter and Business. Tell us how your teams book meetings and we come back with a plan.

Moving from Calendly to Cal.com

  1. List people, event types and links

    Who books through Calendly, which event types they use, and where their links are published: signatures, the website, templates, forms.

  2. Check team scheduling first

    Round-robin, collective events and routing forms are not in Cal.diy. If a team depends on them, we settle how it will book before anyone moves, and say so before you sign.

  3. Set up event types and calendars

    Each person connects their calendar and recreates their event types and availability, with us on hand for the first ones.

  4. Swap the links, then close the account

    New links replace the old ones in signatures, the website and templates. Meetings already booked stay in everyone's calendar, and Calendly stays open until no new bookings arrive there for a full cycle.

Migration guide

How to migrate from Calendly to Cal.com

Move booking pages from Calendly to self-hosted Cal.com: list event types and links, connect calendars, rebuild each page, swap every link, close Calendly last.

Questions

Is Cal.com open source?

The commercial Cal.com product has been closed source since April 2026. Cal.com, Inc. republished the open code as Cal.diy under the MIT licence, and that is what we operate. Upstream recommends Cal.diy for non-production use; we run it with pinned versions, backups, monitoring and tested upgrades.

Our sales team uses round-robin. Does that work?

Not in Cal.diy. Round-robin, collective events, routing forms and SMS workflows are in the commercial Cal.com product only. We check this in the first conversation and tell you plainly if your scheduling needs something else.

Can we import our Calendly event types?

Not in Cal.diy, the edition we run: the Calendly importer is in the commercial Cal.com product only. Little needs importing anyway. Each person recreates a few event types in minutes, and the bookings already live in your calendars. We help with the first ones as part of the fixed-price migration.

Do people who book need an account?

No. Anyone with the link books a slot, as with Calendly. Only your staff sign in.

What happens to our bookings if we leave Pilae?

They are in your Postgres, and the compose files and runbook are in your repository. The events themselves are also in each person's calendar.

Leave Calendly with a plan, not a weekend.

An inventory of what you actually use, the app that replaces it, and a fixed price for the move.

Replace Calendly