Cal.com Production Readiness Report
Open-source scheduling infrastructure — a self-hostable Calendly alternative with deep calendar integrations.
- Category
- Scheduling
- Language
- Next.js / TypeScript
- License
- AGPLv3 + commercial
- Deployment
- Docker / Vercel / K8s
- Datastore
- PostgreSQL
- Integrations
- Google, Microsoft, CalDAV, Zoom
Cal.com is polished, self-hostable scheduling infrastructure. Teams choose it to control booking data, customize workflows, and embed scheduling into their own products.
The app itself is a Next.js + Postgres deployment that is approachable to run. The real work is configuration: OAuth apps for Google/Microsoft calendars, transactional email, and the environment variables that wire up integrations. Note AGPL licensing implications if you modify and distribute it.
Production readiness score
Best for
- Embedding scheduling into your own product
- Owning booking data for privacy or compliance
- Teams needing custom event types and workflows
- Replacing Calendly seats at scale
Not ideal for
- Individuals who just want a quick hosted link
- Teams unwilling to configure OAuth and SMTP
- Use cases blocked by AGPL distribution terms
Standing up the app is easy; the friction is in external credentials and email. Most issues are configuration, not infrastructure.
Create Google and Microsoft apps for calendar sync.
Configure an SMTP provider for confirmations and reminders.
Many environment variables must be set correctly to boot.
Public URL needed for calendar and payment callbacks.
- Compute
- 1–2 vCPU / 2–4 GB
- Database
- Managed PostgreSQL 13+
- SMTP / transactional email provider
- Ingress
- HTTPS with stable public domain
- Secrets
- OAuth client IDs/secrets per provider
Security considerations
- Store OAuth secrets and the app encryption key in a secrets manager.
- Force HTTPS and set the correct WEBAPP_URL to avoid callback issues.
- Enable 2FA and restrict admin access.
- Review AGPL obligations before shipping a modified, distributed build.
Backup & recovery
- Back up PostgreSQL — it holds bookings, users, and integration tokens.
- Securely back up the encryption key and OAuth credentials.
- Export event-type and workflow config as documentation.
- Verify restored OAuth tokens still refresh after recovery.
Monitoring
- Alert on failed calendar-sync jobs and OAuth token refresh errors.
- Monitor email delivery success rates.
- Track booking webhook failures.
- Watch app error rate and Postgres connection pool usage.
Single container + managed Postgres + SMTP
HA app + managed Postgres + email volume
SSO, white-label, support, SLA
Reference stack
Containers + Managed Postgres + SMTP + OAuth credentials
- 01IngressReverse proxy + TLS
Public booking pages and API
- 02AppCal.com (Next.js)
Web app and API routes
- 03EmailSMTP provider
Confirmations and reminders
- 04IdentityGoogle / Microsoft OAuth
Calendar sync
- 05DatabaseManaged PostgreSQL
Bookings and tokens
We deploy Cal.com on infrastructure you control.
Skip the trial-and-error. Our team handles architecture, security hardening, backups, monitoring, and upgrades — then hands you a production-ready, documented deployment.
Request Cal.com deployment