The challenge
What the system needed to solve
Offer a polished public booking experience while keeping management workflows and integration credentials protected.
The build
Engineering decisions
Deployed the Cal.com application and database through GitOps with health checks, persistent storage, and automated TLS.
Preserved public booking and availability routes while applying stronger controls to administration paths.
Connected calendar and mail delivery through scoped credentials stored outside Git.
Added application-specific Grafana coverage and contract tests across Homepage, Dashy, and observability.
Architecture
How the pieces connect
- 1Public booking visitor or authenticated owner
- 2TLS edge and path policy
- 3Cal.com application
- 4PostgreSQL, calendar, and mail integrations
Results
What changed
- Visitors can book through a branded, self-hosted domain.
- Availability, email delivery, database health, and route status are independently observable.
- Deployment and integration configuration can be recreated from versioned desired state.
