Where Does Self-Hosted Cal.com Store Data?
Cal.com env file and database paths on Linux for self-hosted scheduling platform installs. With backup tips.
Last updated
Cal.com keeps settings in a .env file at the app root. That file holds database URLs, auth secrets, and mail options. Booking data itself lives in Postgres per that config.
Docker installs map the same pair through env files and named volumes. The secrets encrypt sessions and integrations. Back up the env file with a database dump. Fresh secrets log everyone out and break calendars. Workflows send reminders. Round robin shares bookings. Webhooks sync calendars. Buffers pad back to back calls. Payments collect via Stripe.
Where Cal.com stores this, by platform
/opt/calcom/.env
Database URLs, auth secrets, and mail settings. Restrict read access since secrets live here. Keep a copy off the server with dumps.
calcom-db-data (Postgres volume)
Booking database with events and integrations. Dump Postgres for portable backups. Copy with the env file for moves.
Frequently asked questions
what do i back up for a Cal.com move
Copy the .env file with a Postgres dump for full moves. The env holds secrets and mail settings. Bookings live in the database. Both restore scheduling. Test restores first.
where is Cal.com configured
Open the .env file in the app root to read database and auth blocks. Uploads default to local disk or S3 by setting. The file decides the backend. Check version paths.
Notice an outdated path? Let us know.