> Source: https://meetrix.io/store/cal-diy/
> Markdown copy of that page. Cite the URL above, not this file.

[Store](https://meetrix.io/store/)  Cal.diy

Open-source scheduling platform

# Self-hosted Cal.diy scheduling on AWS and Google Cloud

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.

 [Launch on AWS](https://aws.amazon.com/marketplace/pp/prodview-sagdu4kf6znn2)[ Launch on Google Cloud](https://console.cloud.google.com/marketplace/product/meetrix-public/cal-diy-scheduling-platform)

-   Ready in 5-10 minutes
-   MIT licensed
-   No per-seat fees

![Cal.diy scheduling platform deployed on Google Cloud by Meetrix](https://meetrix.io/assets/store/cal-diy/cal-diy.webp)

## What is Cal.diy?

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.

-   ### Booking pages

    Share links where people pick a time that suits both of you.

-   ### Calendar sync

    Checks Google Calendar, Office 365 and other calendars before offering slots.

-   ### Availability rules

    Set working hours and event types the way you want them.

-   ### REST API

    Built on the Cal.com codebase, with an API for custom integrations.

-   ### Customisable

    Change booking logic and event behaviour, which hosted tools do not allow.

-   ### Your own data

    Bookings and calendar data stay in your own cloud account.

## What's in the Meetrix Cal.diy image

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.

-   Cal.diy with PostgreSQL configured and connected
-   A Let's Encrypt certificate for your domain
-   SMTP and "from" address set at launch on AWS
-   PostgreSQL backups to your S3 bucket on AWS
-   A deployment template for your own AWS account or GCP project
-   Deployment support from Meetrix at support@meetrix.io

## How to set up a self-hosted Cal.diy server

1.  ### Launch the server

    Subscribe on AWS Marketplace or Google Cloud Marketplace, enter your domain, and deploy. On AWS, also add SMTP details and a backup bucket.

2.  ### Point your domain at it

    Create a DNS A record for your booking domain with the server's public IP, so the certificate can be issued.

3.  ### Create the admin user

    Open your domain and follow the setup wizard to create the administrator account. The password needs at least 15 characters.

4.  ### Connect your calendar

    Link Google Calendar or Office 365 from the admin panel, set your availability and share your first booking link.

## Choose your cloud

### Cal.diy on AWS

An AMI on AWS Marketplace, launched into your own AWS account with a CloudFormation stack.

Deploys with

CloudFormation

Recommended size

t3.small or larger

Backups

PostgreSQL backups to S3

#### Setup guides

-   [**Developer guide** Launch, DNS, SSL, troubleshoot](https://meetrix.io/blogs/cal-diy-developer-guide/)
-   [**Self-host Cal.diy on AWS** Features and Calendly comparison](https://meetrix.io/blogs/self-host-cal-diy-aws/)
-   [**Video walkthrough** Watch the deployment on YouTube](https://www.youtube.com/watch?v=CDpyXvNmi1M)

 [Launch on AWS](https://aws.amazon.com/marketplace/pp/prodview-sagdu4kf6znn2)

### Cal.diy on Google Cloud

The same scheduling platform as a Google Cloud Marketplace image, deployed into your own GCP project.

Deploys with

Marketplace deployment form

Recommended size

e2-standard-2

Free trial

5 days, up to USD 50 licence credit

#### Setup guides

-   [**Developer guide** Configure, DNS, admin setup, logs](https://meetrix.io/blogs/caldiy-gcp-developer-guide/)
-   [**Cal.diy on Google Cloud Marketplace** Who it suits and how it compares](https://meetrix.io/blogs/caldiy-scheduling-platform-gcp/)

 [Launch on Google Cloud](https://console.cloud.google.com/marketplace/product/meetrix-public/cal-diy-scheduling-platform)

## Cal.diy by Meetrix vs Calendly vs Cal.com

|  | 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 →](https://meetrix.io/blogs/calendly-alternatives-2026/)

## Video: deploy Cal.diy on AWS

## Cal.diy FAQ

What is Cal.diy?

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.

Is Cal.diy the same as Cal.com?

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.

Is Cal.diy meant for production use?

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.

Will calendar sync work like Calendly?

Yes. Cal.diy connects to Google Calendar, Office 365 and other standard providers and checks existing events before offering open slots.

How do I create the admin account?

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.

Is Cal.diy free?

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.

Which machine size should I choose?

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.

How do I upgrade?

Launch a new instance with the newer image and migrate your data. Back up your server data before removing the old instance.

## Cal.diy guides and articles

### [Best Calendly Alternatives 2026: Free, Open Source, Self-Hosted](https://meetrix.io/blogs/calendly-alternatives-2026/)

Cal.diy and seven other scheduling tools, compared honestly.

### [How to Self-Host Cal.diy in AWS with a Pre-Configured AMI](https://meetrix.io/blogs/self-host-cal-diy-aws/)

What Cal.diy is, how it relates to Cal.com, and how to deploy it.

### [Cal.diy Scheduling Platform on GCP Marketplace](https://meetrix.io/blogs/caldiy-scheduling-platform-gcp/)

Booking links on Google Cloud without handing Calendly your calendar data.

## Need a hand with your Cal.diy server?

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](https://meetrix.io/contact-us/)