Run Cal.diy, the MIT-licensed community edition of Cal.com, from a pre-configured image in your own cloud account. Booking pages, calendar sync and availability, with your calendar data on your own server and no per-seat fees.
Cal.diy is the open-source, self-hostable scheduling platform that came out of Cal.com's original codebase. Since April 2026 Cal.com's hosted product has been closed-source, and the self-hosting code continues as Cal.diy under the MIT licence. It is officially recommended for personal and non-production use.
Share links where people pick a time that suits both of you.
Checks Google Calendar, Office 365 and other calendars before offering slots.
Set working hours and event types the way you want them.
Built on the Cal.com codebase, with an API for custom integrations.
Change booking logic and event behaviour, which hosted tools do not allow.
Bookings and calendar data stay in your own cloud account.
Self-hosting Cal.diy means a database, email settings, a reverse proxy and SSL before the first booking page goes live. The marketplace image sets those up.
Subscribe on AWS Marketplace or Google Cloud Marketplace, enter your domain, and deploy. On AWS, also add SMTP details and a backup bucket.
Create a DNS A record for your booking domain with the server's public IP, so the certificate can be issued.
Open your domain and follow the setup wizard to create the administrator account. The password needs at least 15 characters.
Link Google Calendar or Office 365 from the admin panel, set your availability and share your first booking link.
An AMI on AWS Marketplace, launched into your own AWS account with a CloudFormation stack.
Launch on AWS 
The same scheduling platform as a Google Cloud Marketplace image, deployed into your own GCP project.
Launch on Google Cloud | Cal.diy by Meetrix | Calendly | Cal.com (hosted) | |
|---|---|---|---|
| Hosting | Your AWS account or GCP project | Calendly's cloud | Cal.com's cloud |
| Scheduling data | Bookings never leave your account | Held by Calendly | Held by Cal.com |
| Pricing model | Cloud compute only, no per-seat fee | Capped free tier, paid tiers per seat | Per-seat subscription |
| Intended use | Personal and non-production | Production cloud service | Production cloud service |
Cal.diy has no official commercial SLA; Meetrix supports the deployment. Read the best Calendly alternatives for 2026 →
Cal.diy is the open-source, MIT-licensed scheduling platform that came out of Cal.com's original codebase. It covers booking pages, calendar sync and availability management, self-hosted on your own infrastructure.
No. Cal.com is now a closed-source hosted SaaS product. Cal.diy continues as the free, self-hostable open-source edition with the same core booking and calendar features.
Cal.diy is officially recommended for personal and non-production use and has no commercial SLA. It suits a personal booking link or an internal tool; for a business-critical booking flow, the managed Cal.com product is the better fit.
Yes. Cal.diy connects to Google Calendar, Office 365 and other standard providers and checks existing events before offering open slots.
No admin account is preset. Open your domain once DNS and SSL are ready and the setup wizard asks for a username, full name, email and a password of at least 15 characters.
Cal.diy is MIT-licensed and free. On AWS or Google Cloud you pay for the server, plus any Meetrix software fee shown on the marketplace listing.
t3.small or larger on AWS, and e2-standard-2 (2 vCPU, 8 GB memory) on Google Cloud. Choose a larger machine for heavier booking traffic.
Launch a new instance with the newer image and migrate your data. Back up your server data before removing the old instance.
Cal.diy and seven other scheduling tools, compared honestly.
What Cal.diy is, how it relates to Cal.com, and how to deploy it.
Booking links on Google Cloud without handing Calendly your calendar data.
We build and run self-hosted tools for teams every day, from calendar integrations to custom booking flows. Tell us what you need.
Contact us