Self-host Cal.com
Open-source scheduling. It needs Postgres, a couple of generated secrets, its own address in its environment, and its migrations run before the web process starts. All four are things Bay can do without asking you anything.
Paste it into Claude Code, Codex, Cursor or anything else that runs commands. It clones the source, deploys it, and signs you in on the way past. There is no dashboard step.
What Bay provisions
- Postgres
Secrets it generates for you
- NEXTAUTH_SECRET, generated rather than asked for
- CALENDSO_ENCRYPTION_KEY, generated rather than asked for
What you may be asked for
- Google OAuth client (optional). Only if you want to connect Google Calendar. Cal.com runs without it; the calendar integrations are what stay switched off.
Also handled
- Its own address, injected as NEXT_PUBLIC_WEBAPP_URL / NEXTAUTH_URL
- Migrations, run before the app starts
- Private until you say otherwise
Before you start
- This is a monorepo and the Docker build is long. On the free plan you get 30 builds a month and one at a time, so a couple of failed attempts is a real dent.
- Its migrations must run before the web process starts. That is what the release step is for, and skipping it gives you an app that serves its homepage and fails everything else.