Self-host Cal.com with Levelrail
Open-source scheduling infrastructure for booking meetings without the back-and-forth.
- Memory1 GiB
- Services2
How to self-host Cal.com
-
Pull the images
2 images are pulled on your server.
Show images
calcom/cal.com:v5.0.9postgres:16-alpine
-
Create the app
2 services start in a single Compose app, with 1 named volume mount for your data, on port 3000.
-
Fill in the secrets
4 secrets are generated and stored encrypted, 5 settings are preset, you do not have to fill in anything.
-
Open it
Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.
Cal.com requirements
- Memory
- About 1 GiB
- Architectures
- amd64 image published, arm64 not available
- Ports
- 3000
- Domain
- Optional, an sslip.io address is used without one
- Settings
- none to fill in
- License
- not yet recorded
- Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.
- Host ports. It publishes port 3000 on the host, so open them in the VPS firewall only if you want that.
Install Levelrail first
On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Cal.com. New to Levelrail? Install it on a fresh VPS first.
docker pull ghcr.io/glincker/levelrail:latest Then levelrail-cli login --device. See Getting started and the Cal.com docs page.
Deploy Cal.com your way
Every format below deploys the same pinned images. Pick the one that fits how you work.
Deploy Cal.com from the CLI
levelrail-cli templates deploy calcom --name my-calcom Deploy Cal.com with the API
curl -X POST -H "Authorization: Bearer $TOKEN" \
https://levelrail.example.com/api/v1/service-templates/calcom/deploy Cal.com configuration
Cal.com services
| Service | Image | Ports | Volumes |
|---|---|---|---|
| calcom | calcom/cal.com:v5.0.9 | 3000 | none |
| db | postgres:16-alpine | none | calcom_db_data -> /var/lib/postgresql/data |
Cal.com environment variables
| Variable | Service | Value |
|---|---|---|
| CALCOM_TELEMETRY_DISABLED | calcom | Preset by the template |
| CALENDSO_ENCRYPTION_KEY | calcom | Generated at deploy |
| DATABASE_URL | calcom | Generated at deploy |
| NEXTAUTH_SECRET | calcom | Generated at deploy |
| NEXTAUTH_URL | calcom | Preset by the template |
| NEXT_PUBLIC_WEBAPP_URL | calcom | Preset by the template |
| POSTGRES_DB | db | Preset by the template |
| POSTGRES_PASSWORD | db | Generated at deploy |
Show all 9 variables
- POSTGRES_USERdbPreset by the template
Ports and volumes
- Ports
- 3000
- Volumes
- 1 named mount: calcom_db_data -> /var/lib/postgresql/data
Cal.com FAQ
How much memory does Cal.com need?
The catalog lists about 1 GiB of memory for Cal.com across its 2 services.
Does Cal.com run on arm64?
For Cal.com, amd64 only, no arm64 image; amd64 is image published.
Does Cal.com need configuration before it starts?
No. The template fills in its own defaults and generates secrets at deploy time.
Which database does Cal.com bundle?
The template includes Postgres, running as its own service.
Which ports does Cal.com use?
Cal.com listens on port 3000 inside the stack.
Where does Cal.com keep its data?
In a named volume: calcom_db_data mounted at /var/lib/postgresql/data.
Can I deploy Cal.com on Dokploy or Dokku?
The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list has an entry with the id calcom for this app, so check that entry as well. Dokku deploys container images with its own commands, so the pinned image calcom/cal.com:v5.0.9, postgres:16-alpine is what you deploy there.