The open-source Calendly successor.
Learn more »
Discussions
·
Website
·
Issues
·
Roadmap
The open source Calendly successor. You are in charge
of your own data, workflow, and appearance.
Calendly and other scheduling tools are awesome. It made our lives massively easier. We're using it for business meetings, seminars, yoga classes, and even calls with our families. However, most tools are very limited in terms of control and customization.
That's where Cal.com comes in. Self-hosted or hosted by us. White-label by design. API-driven and ready to be deployed on your own domain. Full control of your events and data.
This project is tested with browserstack
Meet our sales team for any commercial inquiries.
Cal.com officially launched as v.1.0 on the 15th of September 2021 and we've come a long way so far. Watch releases of this repository to be notified of future updates:

To get a local copy up and running, please follow these simple steps.
Here is what you need to be able to run Cal.com.
If you want to enable any of the available integrations, you may want to obtain additional credentials for each one. More details on this can be found below under the integrations section.
Clone the repo (or fork https://github.com/calcom/cal.com/fork). The code is licensed under AGPLv3, which requires you to provide source code to users who interact with the software over a network. For commercial use without these requirements, acquire a commercial license
git clone https://github.com/calcom/cal.com.git
If you are on Windows, run the following command on
gitbashwith admin privileges:
>git clone -c core.symlinks=true https://github.com/calcom/cal.com.git
See docs for more details.
Go to the project folder
cd cal.com
Install packages with yarn
yarn
Set up your .env file
.env.example to .envopenssl rand -base64 32 to generate a key and add it under NEXTAUTH_SECRET in the .env file.openssl rand -base64 24 to generate a key and add it under CALENDSO_ENCRYPTION_KEY in the .env file.Windows users: Replace the
packages/prisma/.envsymlink with a real copy to avoid a Prisma error (unexpected character / in variable name):# Git Bash / WSL rm packages/prisma/.env && cp .env packages/prisma/.env
Setup Node
If your Node version does not meet the project's requirements as instructed by the docs, "nvm" (Node Version Manager) allows using Node at the version required by the project:
nvm use
You first might need to install the specific version and then use it:
nvm install && nvm use
You can install nvm from here.
yarn dx
- Requires Docker and Docker Compose to be installed
- Will start a local Postgres instance with a few test users - the credentials will be logged in the console
yarn dx
Default credentials created:
| Password | Role | |
|---|---|---|
[email protected] |
free |
Free user |
[email protected] |
pro |
Pro user |
[email protected] |
trial |
Trial user |
[email protected] |
ADMINadmin2022! |
Admin user |
[email protected] |
onboarding |
Onboarding incomplete |
You can use any of these credentials to sign in at http://localhost:3000
Tip: To view the full list of seeded users and their details, run
yarn db-studioand visit http://localhost:5555
Add export NODE_OPTIONS=“--max-old-space-size=16384” to your shell script to increase the memory limit for the node process. Alternatively, you can run this in your terminal before running the app. Replace 16384 with the amount of RAM you want to allocate to the node process.
Add NEXT_PUBLIC_LOGGER_LEVEL={level} to your .env file to control the logging verbosity for all tRPC queries and mutations.
Where {level} can be one of the following:
0 for silly 1 for trace 2 for debug 3 for info 4 for warn 5 for error 6 for fatal
When you set NEXT_PUBLIC_LOGGER_LEVEL={level} in your .env file, it enables logging at that level and higher. Here's how it works:
The logger will include all logs that are at the specified level or higher. For example: \
NEXT_PUBLIC_LOGGER_LEVEL=2, it will log from level 2 (debug) upwards, meaning levels 2 (debug), 3 (info), 4 (warn), 5 (error), and 6 (fatal) will be logged. \NEXT_PUBLIC_LOGGER_LEVEL=3, it will log from level 3 (info) upwards, meaning levels 3 (info), 4 (warn), 5 (error), and 6 (fatal) will be logged, but level 2 (debug) and level 1 (trace) will be ignored. \echo 'NEXT_PUBLIC_LOGGER_LEVEL=3' >> .env
for Logger level to be set at info, for example.
Click the button below to open this project in Gitpod.
This will open a fully configured workspace in your browser with all the necessary dependencies already installed.
Configure environment variables in the .env file. Replace <user>, <pass>, <db-host>, and <db-port> with their applicable values
DATABASE_URL='postgresql://<user>:<pass>@<db-host>:<db-port>'
If you don't know how to configure the DATABASE_URL, then follow the steps here to create a quick local DB
Download and install postgres in your local (if you don't have it already).
Create your own local db by executing createDB <DB name>
Now open your psql shell with the DB you created: psql -h localhost -U postgres -d <DB name>
Inside the psql shell execute \conninfo. And you will get the following info.
Now extract all the info and add it to your DATABASE_URL. The url would look something like thispostgresql://postgres:postgres@localhost:5432/Your-DB-Name. The port is configurable and does not have to be 5432.
If you don't want to create a local DB. Then you can also consider using services like railway.app, Northflank or render.
Copy and paste your DATABASE_URL from .env to .env.appStore.
Set up the database using the Prisma schema (found in packages/prisma/schema.prisma)
In a development environment, run:
yarn workspace @calcom/prisma db-migrate
In a production environment, run:
yarn workspace @calcom/prisma db-deploy
Run mailhog to view emails sent during development
NOTE: Required when
E2E_TEST_MAILHOG_ENABLEDis "1"
docker pull mailhog/mailhog
docker run -d -p 8025:8025 -p 1025:1025 mailhog/mailhog
Run (in development mode)
yarn dev
Open Prisma Studio to look at or modify the database content:
yarn db-studio
Click on the User model to add a new user record.
Fill out the fields email, username, password, and set metadata to empty {} (remembering to encrypt your password with BCrypt) and click Save 1 Record to create your first user.
New users are set on a
TRIALplan by default. You might want to adjust this behavior to your needs in thepackages/prisma/schema.prismafile.
Open a browser to http://localhost:3000 and login with your just created, first user.
Seed the local db by running
cd packages/prisma
yarn db-seed
The above command will populate the local db with dummy users.
Be sure to set the environment variable NEXTAUTH_URL to the correct value. If you are running locally, as the documentation within .env.example mentions, the value should be http://localhost:3000.
# In a terminal just run:
yarn test-e2e
# To open the last HTML report run:
yarn playwright show-report test-results/reports/playwright-html-report
Run npx playwright install to download test browsers and resolve the error below when running yarn test-e2e:
Executable doesn't exist at /Users/alice/Library/Caches/ms-playwright/chromium-1048/chrome-mac/Chromium.app/Contents/MacOS/Chromium
Pull the current version:
git pull
Check if dependencies got added/updated/removed
yarn
Apply database migrations by running one of the following commands:
In a development environment, run:
yarn workspace @calcom/prisma db-migrate
(This can clear your development database in some cases)
In a production environment, run:
yarn workspace @calcom/prisma db-deploy
Check for .env variables changes
yarn predev
Start the server. In a development environment, just do:
yarn dev
For a production build, run for example:
yarn build
yarn start
Enjoy the new version.
This repository includes configuration for AI coding assistants. All AI configuration lives in the agents/ directory as a single source of truth.
agents/
├── rules/ # Modular engineering rules
├── skills/ # Reusable skills/prompts
├── commands.md # Command reference
└── knowledge-base.md # Domain knowledge
AGENTS.md # Main agent instructions
We use symlinks to share configuration across tools:
.claude/
├── rules -> ../agents/rules
└── skills -> ../agents/skills
.cursor/
├── rules -> ../agents/rules
└── skills -> ../agents/skills
If you prefer other AI tools (Windsurf, Goose, OpenCode, etc.), you can create your own dot folders and exclude them from git:
# Add to .git/info/exclude (local only, not committed)
.windsurf/
.goose/
.opencode/
This keeps the repository clean while allowing personal tool preferences.
Official support: Our team will begin to officially support the Dockerfile and docker-compose resources in this
repository.
Important: Cal.com will not be supporting installations that use these Docker resources. While we provide and maintain the Docker configurations, support for Docker-based installations is the responsibility of the user.
This image can be found on DockerHub at https://hub.docker.com/r/calcom/cal.com.
Note for ARM Users: Use the {version}-arm suffix for pulling images. Example: docker pull calcom/cal.com:v5.6.19-arm.
Make sure you have docker & docker compose installed on the server / system. Both are installed by most docker utilities, including Docker Desktop and Rancher Desktop.
Note: docker compose without the hyphen is now the primary method of using docker-compose, per the Docker documentation.
If you are evaluating Cal.com or running with minimal to no modifications, this option is for you.
Clone calcom/cal.com
git clone --recursive https://github.com/calcom/cal.com.git
Change into the directory
cd cal.com
Prepare your configuration: Rename .env.example to .env and then update .env
cp .env.example .env
Most configurations can be left as-is, but for configuration options see Important Run-time variables below.
Push Notifications (VAPID Keys)
If you see an error like:
Error: No key set vapidDetails.publicKey
This means your environment variables for Web Push are missing.
You must generate and set NEXT_PUBLIC_VAPID_PUBLIC_KEY and VAPID_PRIVATE_KEY.
Generate them with:
npx web-push generate-vapid-keys
Then update your .env file:
NEXT_PUBLIC_VAPID_PUBLIC_KEY=your_public_key_here
VAPID_PRIVATE_KEY=your_private_key_here
Do not commit real keys to .env.example — only placeholders.
Update the appropriate values in your .env file, then proceed.
(optional) Pre-Pull the images by running the following command:
docker compose pull
This will use the default image locations as specified by image: in the docker-compose.yaml file.
Note: To aid with support, by default Scarf.sh is used as registry proxy for download metrics.
Start Cal.com via docker compose
(Most basic users, and for First Run) To run the complete stack, which includes a local Postgres database, Cal.com web app, and Prisma Studio:
docker compose up -d
To run Cal.com web app and Prisma Studio against a remote database, ensure that DATABASE_URL is configured for an available database and run:
docker compose up -d calcom studio
To run only the Cal.com web app, ensure that DATABASE_URL is configured for an available database and run:
docker compose up -d calcom
Note: to run in attached mode for debugging, remove -d from your desired run command.
Open a browser to http://localhost:3000, or your defined NEXT_PUBLIC_WEBAPP_URL. The first time you run Cal.com, a setup wizard will initialize. Define your first user, and you're ready to go!
Stop the Cal.com stack
docker compose down
Pull the latest changes
docker compose pull
Update env vars as necessary.
Re-start the Cal.com stack
docker compose up -d
Clone calcom/docker.
git clone https://github.com/calcom/cal.com.git calcom-docker
Change into the directory
cd calcom-docker
Update the calcom submodule. This project depends on the Cal.com source code, which is included here as a Git submodule. To make sure you get everything you need, update the submodule with the command below.
git submodule update --remote --init
Note: DO NOT use recursive submodule update, otherwise you will receive a git authentication error.
Rename .env.example to .env and then update .env
For configuration options see Build-time variables below. Update the appropriate values in your .env file, then proceed.
Build the Cal.com docker image:
Note: Due to application configuration requirements, an available database is currently required during the build process.
a) If hosting elsewhere, configure the DATABASE_URL in the .env file, and skip the next step
b) If a local or temporary database is required, start a local database via docker compose.
docker compose up -d database
Build Cal.com via docker compose (DOCKER_BUILDKIT=0 must be provided to allow a network bridge to be used at build time. This requirement will be removed in the future)
DOCKER_BUILDKIT=0 docker compose build calcom
Start Cal.com via docker compose
(Most basic users, and for First Run) To run the complete stack, which includes a local Postgres database, Cal.com web app, and Prisma Studio:
docker compose up -d
To run Cal.com web app and Prisma Studio against a remote database, ensure that DATABASE_URL is configured for an available database and run:
docker compose up -d calcom studio
To run only the Cal.com web app, ensure that DATABASE_URL is configured for an available database and run:
docker compose up -d calcom
Note: to run in attached mode for debugging, remove -d from your desired run command.
Open a browser to http://localhost:3000, or your defined NEXT_PUBLIC_WEBAPP_URL. The first time you run Cal.com, a setup wizard will initialize. Define your first user, and you're ready to go!
These variables must also be provided at runtime
| Variable | Description | Required | Default |
|---|---|---|---|
| DATABASE_URL | database url with credentials - if using a connection pooler, this setting should point there | required | postgresql://unicorn_user:magical_password@database:5432/calendso |
| CALCOM_LICENSE_KEY | Enterprise License Key | optional | |
| NEXT_PUBLIC_WEBAPP_URL | Base URL of the site. NOTE: if this value differs from the value used at build-time, there will be a slight delay during container start (to update the statically built files). | optional | http://localhost:3000 |
| NEXTAUTH_URL | Location of the auth server. By default, this is the Cal.com docker instance itself. | optional | {NEXT_PUBLIC_WEBAPP_URL}/api/auth |
| NEXTAUTH_SECRET | must match build variable | required | secret |
| CALENDSO_ENCRYPTION_KEY | must match build variable | required | secret |
If building the image yourself, these variables must be provided at the time of the docker build, and can be provided by updating the .env file. Currently, if you require changes to these variables, you must follow the instructions to build and publish your own image.
Updating these variables is not required for evaluation, but is required for running in production. Instructions for generating variables can be found in the Cal.com instructions
| Variable | Description | Required | Default |
|---|---|---|---|
| DATABASE_URL | database url with credentials - if using a connection pooler, this setting should point there | required | postgresql://unicorn_user:magical_password@database:5432/calendso |
| MAX_OLD_SPACE_SIZE | Needed for Nodejs/NPM build options | required | 4096 |
| NEXT_PUBLIC_LICENSE_CONSENT | license consent - true/false | required | |
| NEXTAUTH_SECRET | Cookie encryption key | required | secret |
| CALENDSO_ENCRYPTION_KEY | Authentication encryption key | required | secret |
| NEXT_PUBLIC_WEBAPP_URL | Base URL injected into static files | optional | http://localhost:3000 |
| NEXT_PUBLIC_WEBSITE_TERMS_URL | custom URL for terms and conditions website | optional | https://cal.com/terms |
| NEXT_PUBLIC_WEBSITE_PRIVACY_POLICY_URL | custom URL for privacy policy website | optional | https://cal.com/privacy |
| NEXT_PUBLIC_API_V2_URL | URL for the v2 API, only required for custom integrations or custom booking experiences using Cal.com Platform | optional | |
| CALCOM_TELEMETRY_DISABLED | Allow Cal.com to collect anonymous usage data (set to 1 to disable) |
optional | |
| NEXT_PUBLIC_SINGLE_ORG_SLUG | Required if ORGANIZATIONS_ENABLED is true | optional | |
| ORGANIZATIONS_ENABLED | Used for Enterprise or Organizations plan | optional |
If running behind a load balancer which handles SSL certificates, you will need to add the environmental variable NODE_TLS_REJECT_UNAUTHORIZED=0 to prevent requests from being rejected. Only do this if you know what you are doing and trust the services/load-balancers directing traffic to your service.
Certain versions may have trouble creating a user if the field metadata is empty. Using an empty json object {} as the field value should resolve this issue. Also, the id field will autoincrement, so you may also try leaving the value of id as empty.
If you experience this error, it may be the way the default Auth callback in the server is using the WEBAPP_URL as a base url. The container does not necessarily have access to the same DNS as your local machine, and therefore needs to be configured to resolve to itself. You may be able to correct this by configuring NEXTAUTH_URL=http://localhost:3000/api/auth, to help the backend loop back to itself.
docker-calcom-1 | @calcom/web:start: [next-auth][error][CLIENT_FETCH_ERROR]
docker-calcom-1 | @calcom/web:start: https://next-auth.js.org/errors#client_fetch_error request to http://testing.localhost:3000/api/auth/session failed, reason: getaddrinfo ENOTFOUND testing.localhost {
docker-calcom-1 | @calcom/web:start: error: {
docker-calcom-1 | @calcom/web:start: message: 'request to http://testing.localhost:3000/api/auth/session failed, reason: getaddrinfo ENOTFOUND testing.localhost',
docker-calcom-1 | @calcom/web:start: stack: 'FetchError: request to http://testing.localhost:3000/api/auth/session failed, reason: getaddrinfo ENOTFOUND testing.localhost\n' +
docker-calcom-1 | @calcom/web:start: ' at ClientRequest.<anonymous> (/calcom/node_modules/next/dist/compiled/node-fetch/index.js:1:65756)\n' +
docker-calcom-1 | @calcom/web:start: ' at ClientRequest.emit (node:events:513:28)\n' +
docker-calcom-1 | @calcom/web:start: ' at ClientRequest.emit (node:domain:489:12)\n' +
docker-calcom-1 | @calcom/web:start: ' at Socket.socketErrorListener (node:_http_client:494:9)\n' +
docker-calcom-1 | @calcom/web:start: ' at Socket.emit (node:events:513:28)\n' +
docker-calcom-1 | @calcom/web:start: ' at Socket.emit (node:domain:489:12)\n' +
docker-calcom-1 | @calcom/web:start: ' at emitErrorNT (node:internal/streams/destroy:157:8)\n' +
docker-calcom-1 | @calcom/web:start: ' at emitErrorCloseNT (node:internal/streams/destroy:122:3)\n' +
docker-calcom-1 | @calcom/web:start: ' at processTicksAndRejections (node:internal/process/task_queues:83:21)',
docker-calcom-1 | @calcom/web:start: name: 'FetchError'
docker-calcom-1 | @calcom/web:start: },
docker-calcom-1 | @calcom/web:start: url: 'http://testing.localhost:3000/api/auth/session',
docker-calcom-1 | @calcom/web:start: message: 'request to http://testing.localhost:3000/api/auth/session failed, reason: getaddrinfo ENOTFOUND testing.localhost'
docker-calcom-1 | @calcom/web:start: }
You can deploy Cal.com on Railway using the button above. The team at Railway also have a detailed blog post on deploying Cal.com on their platform.
You can deploy Cal.com on Northflank using the button above. The team at Northflank also have a detailed blog post on deploying Cal.com on their platform.
Currently Vercel Pro Plan is required to be able to Deploy this application with Vercel, due to limitations on the number of serverless functions on the free plan.
See the roadmap project for a list of proposed features (and known issues). You can change the view to see planned tagged releases.
Cal.com, Inc. is a commercial open source company, which means some parts of this open source repository require a commercial license. The concept is called "Open Core" where the core technology (99%) is fully open source, licensed under AGPLv3 and the last 1% is covered under a commercial license ("/ee" Enterprise Edition) which we believe is entirely relevant for larger organisations that require enterprise features. Enterprise features are built by the core engineering team of Cal.com, Inc. which is hired in full-time. Find their compensation on https://cal.com/open.
[!NOTE]
Our philosophy is simple, all "Singleplayer APIs" are open-source under AGPLv3. All commercial "Multiplayer APIs" are under a commercial license.
| AGPLv3 | EE | |
|---|---|---|
| Self-host for commercial purposes | ✅ | ✅ |
| Clone privately | ✅ | ✅ |
| Fork publicly | ✅ | ✅ |
| Requires CLA | ✅ | ✅ |
| Official Support | ❌ | ✅ |
| Derivative work privately | ❌ | ✅ |
| SSO | ❌ | ✅ |
| Admin Panel | ❌ | ✅ |
| Impersonation | ❌ | ✅ |
| Managed Event Types | ❌ | ✅ |
| Organizations | ❌ | ✅ |
| Payments | ❌ | ✅ |
| Platform | ❌ | ✅ |
| Teams | ❌ | ✅ |
| Users | ❌ | ✅ |
| Video | ❌ | ✅ |
| Workflows | ❌ | ✅ |
[!TIP]
We work closely with the community and always invite feedback about what should be open and what is fine to be commercial. This list is not set and stone and we have moved things from commercial to open in the past. Please open a discussion if you feel like something is wrong.
We ❤️ contributions! Whether it’s fixing a typo, improving documentation, or building new features, your help makes Cal.com better.
Even small improvements matter — thank you for helping us grow!
We have a list of help wanted that contain small features and bugs which have a relatively limited scope. This is a great place to get started, gain experience, and get familiar with our contribution process.
Don't code but still want to contribute? Join our Discussions and join the #Translate channel and let us know what language you want to translate.
Refer to docs here for a detailed documentation with screenshots.
.../auth/calendar.events, .../auth/calendar.readonly and select Update.<Cal.com URL>/api/integrations/googlecalendar/callback and <Cal.com URL>/api/auth/callback/google replacing Cal.com URL with the URI at which your application runs..env file as the value for GOOGLE_API_CREDENTIALS key.After adding Google credentials, you can now Google Calendar App to the app store.
You can repopulate the App store by running
cd packages/prisma
yarn seed-app-store
You will need to complete a few more steps to activate Google Calendar App.
Make sure to complete section "Obtaining the Google API Credentials". After that do the
following
<Cal.com URL>/api/auth/callback/google<Cal.com URL>/api/integrations/office365calendar/callback replacing Cal.com URL with the URI at which your application runs..env file into the ZOOM_CLIENT_ID and ZOOM_CLIENT_SECRET fields.<Cal.com URL>/api/integrations/zoomvideo/callback replacing Cal.com URL with the URI at which your application runs.meeting:write:meeting.user:read:settings..env file into the DAILY_API_KEY field in your .env file.DAILY_SCALE_PLAN variable to true in order to use features like video recording.<Cal.com URL>/api/integrations/basecamp3/callback replacing Cal.com URL with the URI at which your application runs.BASECAMP3_CLIENT_ID and BASECAMP3_CLIENT_SECRET fields.BASECAMP3_CLIENT_SECRET env variable to {your_domain} ({support_email}).Cal.com ([email protected])..env file into the HUBSPOT_CLIENT_ID and HUBSPOT_CLIENT_SECRET fields.<Cal.com URL>/api/integrations/hubspot/callback replacing Cal.com URL with the URI at which your application runs.crm.objects.contacts and crm.lists..env file into the ZOHOCRM_CLIENT_ID and ZOHOCRM_CLIENT_SECRET fields.<Cal.com URL>/api/integrations/zohocrm/callback replacing Cal.com URL with the URI at which your application runs.Cal.com uses Unkey for rate limiting. This is an optional feature and is not required for testing or self-hosting.
If you want to enable rate limiting:
ratelimit.create_namespace and ratelimit.limit.env file into the UNKEY_ROOT_KEY fieldNote: If you don't configure Unkey, Cal.com will work normally without rate limiting enabled.
.env file into the SENDGRID_API_KEY field.env file into the SENDGRID_EMAIL field.env file into the NEXT_PUBLIC_SENDGRID_SENDER_NAME field (fallback is Cal.com).env file into the TWILIO_SID field.env file into the TWILIO_TOKEN field.env file into the TWILIO_PHONE_NUMBER field.env file into the NEXT_PUBLIC_SENDER_ID field (fallback is Cal.com).env file into the TWILIO_MESSAGING_SID field.env file into the TWILIO_VERIFY_SID fieldWe use changesets to generate changelogs and publish public packages (packages with private: true are ignored).
An example of good readme is atoms readme. Every public package must:
❗️Breaking changeSpecial thanks to these amazing projects which help power Cal.com:
Cal.com is an open startup and Jitsu (an open-source Segment alternative) helps us to track most of the usage metrics.