---
title: "Deploy Cal.com"
description: "Open-source scheduling: booking pages, calendar sync, Calendly alternative"
category: "Automation"
url: https://railway.com/deploy/calcom-2
---

# Deploy Cal.com

Open-source scheduling: booking pages, calendar sync, Calendly alternative

**[Deploy Cal.com on Railway](https://railway.com/template/calcom-2)**

Machine-readable deploy manifest (JSON, validated by TemplateCI): https://railway.com/deploy/calcom-2/manifest.json

- **Creator:** Agaz Self-Host
- **Category:** Automation
- **Total deploys:** 2

## Template content

### Cal.com https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons/png/cal-com.png

- **Source:** https://github.com/aalfath/cal-com-railway-template
- **Health check:** /api/version
- **Public domain:** Yes

### Postgres https://devicons.railway.app/i/postgresql.svg

- **Image:** ghcr.io/railwayapp-templates/postgres-ssl:18

## Documentation

# Deploy and Host Cal.com on Railway

Cal.com is an open-source scheduling platform and a self-hosted alternative to Calendly. You share a booking link, people pick a free slot from your calendar, and Cal.com creates the event, sends the invites and handles reschedules and cancellations. It supports event types, availability rules, booking questions and a large app store of calendar and video integrations.

## About Hosting Cal.com

Cal.com is a Next.js application backed by PostgreSQL. On every start it updates its built-in public URL, runs its Prisma database migrations, seeds the app store and starts the web server, so the first boot takes a minute or two. This template builds Cal.com v6.2.0 from a small GitHub wrapper around the official Docker image, pinned by digest, and connects it to a Railway Postgres database on a persistent volume over the private network. The session secret and the encryption key for stored app credentials are generated at deploy time, the public URL comes from the Railway domain, and a health check on `/api/version` keeps the service in rotation only once it answers.

## Common Use Cases

* Personal booking pages for meetings, consultations or office hours, on your own domain
* Separate booking pages for a small group of colleagues, each with their own account and calendars
* Embedding a booking widget in a website, with bookings kept in your own database

## Dependencies for Cal.com Hosting

* PostgreSQL (Railway Postgres, included in this template)
* Optional: an SMTP server for booking emails, and Google or Microsoft API credentials for calendar sync

### Deployment Dependencies

* Cal.com source and self-hosting docs: https://github.com/calcom/cal.com
* Cal.com v6.2.0 release: https://github.com/calcom/cal.com/releases/tag/v6.2.0
* Official Docker image: https://hub.docker.com/r/calcom/cal.com
* Template wrapper repo: https://github.com/aalfath/cal-com-railway-template

### Implementation Details

**First run.** Open the public URL as soon as the deploy is green. Cal.com shows its setup wizard, and the first visitor creates the admin account, so do this right away. Cal.com treats an admin as inactive until two-factor authentication is on: turn it on under Settings, Security to reach the admin pages, where you can also add more users.

**Sign-up is off by default.** Only the admin adds users. To let anyone register, set `NEXT_PUBLIC_DISABLE_SIGNUP=false` on the Cal.com service and redeploy.

**Optional settings** (add them to the Cal.com service when you need them):

* Email: `EMAIL_FROM`, `EMAIL_SERVER_HOST`, `EMAIL_SERVER_PORT`, `EMAIL_SERVER_USER`, `EMAIL_SERVER_PASSWORD`. Without them Cal.com sends no booking emails.
* Google Calendar: `GOOGLE_API_CREDENTIALS`. Other apps use the keys listed in Cal.com's `.env.appStore.example`.
* Custom domain: add it in Railway, then set `NEXT_PUBLIC_WEBAPP_URL=https://YOUR-DOMAIN` and redeploy.

Keep `CALENDSO_ENCRYPTION_KEY` unchanged after the first deploy: it encrypts the credentials of connected apps.

**Version and updates.** v6.2.0 is the latest official Cal.com release and Docker image. The upstream open-source project now continues as Cal.diy, which publishes no Docker images yet. When a newer official image appears, the wrapper repo is updated and Railway offers you the update. Back up Postgres before applying one, because Cal.com migrates its database on start.

## Why Deploy Cal.com on Railway?


Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.

By deploying Cal.com on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.



## Similar templates

- [N8N Main + Worker](https://railway.com/deploy/n8n-main-worker) — Deploy and Host N8N with Inactive worker.
- [Evolution API with n8n](https://railway.com/deploy/evolution-api-with-n8n) — Automate WhatsApp workflows with Evolution API, n8n, and Postgres.
- [Postgres Backup](https://railway.com/deploy/postgres-s3-backups) — Cron-based PostgreSQL backup to bucket storage

Open this page in a browser: https://railway.com/deploy/calcom-2
