AltFreeStack
Productivitydocker-ready1-click-deployOpen-Core🟑 Standard · ~1GB

Cal.com: Open-Core alternative to Calendly in 2026

Cal.com is open source scheduling infrastructure: booking pages, event types, calendar integrations and video calls, fully customizable and self-hostable.

Core is open source, but advanced features or enterprise support may be behind a paid tier β€” check the license.

License AGPL-3.049k starsWebsite GitHub Repository

Audit Snapshot

View notes β†’
  • License β€” Discrepancy with GitHub

  • GitHub β€” Active

  • Latest release β€” v6.2.0 Β· 7 months ago

  • Docker Compose β€” Verified

  • Production β€” Not production-tested by AltFreeStack

Cal.com vs. Calendly

Pros

  • Fully white-label, your own domain and brand

Things to consider

  • Initial setup is more technical than signing up for Calendly

Quick Docker installation guide

Copy this docker-compose.yml, adjust the example passwords and run docker compose up -d on your server. See the full step-by-step guide β†’

πŸ’‘ Official SaaS or self-hosted with AltFreeStack?

  • On the official cloud: $12/mo per user on Calendly.
  • On your own VPS: the core is free to self-host on your own server β€” no more monthly SaaS fee, though some advanced features stay behind a paid plan.
docker-compose.yml
version: "3.9"
services:
  calcom:
    image: calcom/cal.com:v6.2.0
    restart: unless-stopped
    ports:
      - "3000:3000"
    environment:
      - DATABASE_URL=postgresql://calcom:change-me-db-password@calcom-db:5432/calcom
      - NEXTAUTH_URL=https://cal.yourdomain.com # CHANGE THIS TO YOUR DOMAIN
      - NEXTAUTH_SECRET=change-me-super-secret # REQUIRED: generate a random secret before first run
      - CALENDSO_ENCRYPTION_KEY=change-me-32-char-key # REQUIRED: generate a random secret before first run
    depends_on:
      - calcom-db
  calcom-db:
    image: postgres:15-alpine
    restart: unless-stopped
    environment:
      - POSTGRES_USER=calcom
      - POSTGRES_PASSWORD=change-me-db-password # must match DATABASE_URL above
      - POSTGRES_DB=calcom
    volumes:
      - calcom_pg_data:/var/lib/postgresql/data
volumes:
  calcom_pg_data:

πŸš€ Deploy in 1 command

Recommended for beginners

Copy this single command and paste it into your freshly created VPS's console (Vultr, DigitalOcean...). It downloads the script, prints it to your screen so you can see exactly what it's about to do (never a blind direct pipe), and only then installs Docker if needed, writes the files with secrets already generated, and starts everything β€” no nano, no pasting code blocks.

curl -sSL ".../api/deploy?stack=cal-com" -o deploy.sh && cat deploy.sh && bash deploy.sh

This docker-compose corresponds to an actively maintained project β€” last commit 17 days ago.

This docker-compose not working for you? Report it on GitHub β†’

Technical profile

License
AGPL-3.0
Category
Productivity
Replaces
Calendly
Tech stack
Next.jsPostgreSQLPrisma

Under the hood

Database

PostgreSQL

Language

TypeScript (Node.js)

Platforms

Web

Key features

  • Custom booking pages
  • Google/Outlook Calendar sync
  • Built-in video calls (Cal Video)
  • Team meeting routing

Preview

Cal.com interface preview

Public image provided by Cal.com on its own website.

πŸ’Ύ Backups in 3 steps (Day 2)

As long as the ./data folder (the "volume" mapped into the container) exists on your server, your data survives any restart or container update β€” that's the only thing you need to back up.

1. Create a compressed backup on the server

tar -czvf backup-$(date +%F).tar.gz ./data

2. Download it to your computer

From your computer's terminal (not your server's):

scp root@YOUR_IP:~/app/backup-*.tar.gz ./

3. Restore in case of emergency

tar -xzvf backup-file.tar.gz
🌐 Connect your domain with free SSL

Step 1 β€” Set up the DNS

In your domain registrar's dashboard (Cloudflare, Namecheap, GoDaddy...), create a record:

Type
A
Name/Host
@ (root domain) or a subdomain, e.g. app
Content/Value
Your server's public IP

Wait 5 to 15 minutes for the record to propagate across the internet.

Step 2 β€” Automatic reverse proxy with Caddy

One single file, no Nginx config or manual certificates β€” Caddy issues and renews Let's Encrypt HTTPS on its own.

Create a file called Caddyfile:

yourdomain.com {
    reverse_proxy localhost:3000
}

Start Caddy with this command (pulls the image and runs it in the background):

docker run -d -p 80:80 -p 443:443 --name caddy --restart always -v $PWD/Caddyfile:/etc/caddy/Caddyfile -v caddy_data:/data caddy