The open-source Calendly alternative meet (formerly Calendso)

The open-source Calendly alternative meet (formerly Calendso)

The open-source Calendly alternative meet (formerly Calendso)


front end: react.js, next.js, Day.js, Tailwind css

back end: Node.js


Database: postgres

API: | Open Scheduling Infrastructure
Open Source Scheduling: Send a link and meet or build an entire marketplace for humans to connect.
GitHub - calendso/calendso: Scheduling infrastructure for absolutely everyone.
Scheduling infrastructure for absolutely everyone. - GitHub - calendso/calendso: Scheduling infrastructure for absolutely everyone.
Home | Documentation | Documentation
Explore advice and explanations for all of our features, and discover new tips and tricks to get the most out of your subscription.
Home | Developer Documentation | Developer Documentation
Explore information and guides about building on top of and extending Calendso.

integrating with Google calendar

integrating with outlook calendar

integrating zoom

100% privacy is a HIPAA, DSGVO, GDPR and CCPA compliant calendly alternative that also runs on AWS GovCloud or Google Cloud for Goverment.

About The Project


Scheduling infrastructure for absolutely everyone.

The open source Calendly alternative. 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 customisations.

That's where 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.

Product of the Month: April

Support us on Product Hunt - The open source Calendly alternative | Product Hunt - The open source Calendly alternative | Product Hunt - The open source Calendly alternative | Product Hunt

Built With

Stay Up-to-Date

Cal officially launched as v.1.0 on 15th of September, however a lot of new features are coming. Watch releases of this repository to be notified for future updates:


Getting Started

To get a local copy up and running, please follow these simple steps.


Here is what you need to be able to run Cal.

  • Node.js
  • PostgreSQL
  • Yarn (recommended)

You will also need Google API credentials. You can get this from the Google API Console. More details on this can be found below under the Obtaining the Google API Credentials section.



Quick start with yarn dx

  • Requires Docker to be installed
  • Will start a local Postgres instance with a few test users - the credentials will be logged in the console
git clone
cd calendso
yarn dx


  1. Clone the repo

    git clone
  2. Install packages with yarn

    yarn install
  3. Copy .env.example to .env

  4. Configure environment variables in the .env file. Replace <user>, <pass>, <db-host>, <db-port> with their applicable values

    If you don't know how to configure the DATABASE_URL, then follow the steps here
    1. Create a free account with Heroku.

    2. Create a new app.
      Create an App

    3. In your new app, go to Overview and next to Installed add-ons, click Configure Add-ons. We need this to set up our database.

    4. Once you clicked on Configure Add-ons, click on Find more add-ons and search for postgres. One of the options will be Heroku Postgres - click on that option.

    5. Once the pop-up appears, click Submit Order Form - plan name should be Hobby Dev - Free.
      Submit Order Form

    6. Once you completed the above steps, click on your newly created Heroku Postgres and go to its Settings.

    7. In Settings, copy your URI to your .env file and replace the postgresql://<user>:<pass>@<db-host>:<db-port> with it.

    8. To view your DB, once you add new data in Prisma, you can use Heroku Data Explorer.

  5. Set up the database using the Prisma schema (found in prisma/schema.prisma)

    npx prisma migrate deploy
  6. Run (in development mode)

    yarn dev
  7. Open Prisma Studio to look at or modify the database content:

    npx prisma studio
  8. Click on the User model to add a new user record.

  9. Fill out the fields (remembering to encrypt your password with BCrypt) and click Save 1 Record to create your first user.

  10. Open a browser to http://localhost:3000 and login with your just created, first user.

  11. Set a 32 character random string in your .env file for the CALENDSO_ENCRYPTION_KEY.


# In first terminal
yarn dx
# In second terminal
yarn test-playwright

Upgrading from earlier versions

  1. Pull the current version:

    git pull
  2. Apply database migrations by running one of the following commands:

    In a development environment, run:

    npx prisma migrate dev

    (this can clear your development database in some cases)

    In a production environment, run:

    npx prisma migrate deploy
  3. Check the .env.example and compare it to your current .env file. In case there are any fields not present
    in your current .env, add them there.

    For the current version, especially check if the variable BASE_URL is present and properly set in your environment, for example:

  4. Start the server. In a development environment, just do:

    yarn dev

    For a production build, run for example:

    yarn build
    yarn start
  5. Enjoy the new version.



The Docker configuration for Cal is an effort powered by people within the community., Inc. does not provide official support for Docker, but we will accept fixes and documentation. Use at your own risk.

If you want to contribute to the Docker repository, reply here.

The Docker configuration can be found in our docker repository.


Deploy on Railway

You can deploy Cal on Railway using the button above. The team at Railway also have a detailed blog post on deploying Cal on their platform.


See the open issues for a list of proposed features (and known issues).


Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

  1. Fork the project
  2. Create your feature branch (git checkout -b feature/AmazingFeature)
  3. Make your changes
  4. Commit your changes (git commit -m 'Add some AmazingFeature')
  5. Push to the branch (git push origin feature/AmazingFeature)
  6. Open a pull request

Obtaining the Google API Credentials

  1. Open Google API Console. If you don't have a project in your Google Cloud subscription, you'll need to create one before proceeding further. Under Dashboard pane, select Enable APIS and Services.
  2. In the search box, type calendar and select the Google Calendar API search result.
  3. Enable the selected API.
  4. Next, go to the OAuth consent screen from the side pane. Select the app type (Internal or External) and enter the basic app details on the first page.
  5. In the second page on Scopes, select Add or Remove Scopes. Search for Calendar.event and select the scope with scope value .../auth/, .../auth/calendar.readonly and select Update.
  6. In the third page (Test Users), add the Google account(s) you'll using. Make sure the details are correct on the last page of the wizard and your consent screen will be configured.
  7. Now select Credentials from the side pane and then select Create Credentials. Select the OAuth Client ID option.
  8. Select Web Application as the Application Type.
  9. Under Authorized redirect URI's, select Add URI and then add the URI < URL>/api/integrations/googlecalendar/callback replacing URL with the URI at which your application runs.
  10. The key will be created and you will be redirected back to the Credentials page. Select the newly generated client ID under OAuth 2.0 Client IDs.
  11. Select Download JSON. Copy the contents of this file and paste the entire JSON string in the .env file as the value for GOOGLE_API_CREDENTIALS key.

Obtaining Microsoft Graph Client ID and Secret

  1. Open Azure App Registration and select New registration
  2. Name your application
  3. Set Who can use this application or access this API? to Accounts in any organizational directory (Any Azure AD directory - Multitenant)
  4. Set the Web redirect URI to < URL>/api/integrations/office365calendar/callback replacing URL with the URI at which your application runs.
  5. Use Application (client) ID as the MS_GRAPH_CLIENT_ID attribute value in .env
  6. Click Certificates & secrets create a new client secret and use the value as the MS_GRAPH_CLIENT_SECRET attriubte

Obtaining Zoom Client ID and Secret

  1. Open Zoom Marketplace and sign in with your Zoom account.
  2. On the upper right, click "Develop" => "Build App".
  3. On "OAuth", select "Create".
  4. Name your App.
  5. Choose "User-managed app" as the app type.
  6. De-select the option to publish the app on the Zoom App Marketplace.
  7. Click "Create".
  8. Now copy the Client ID and Client Secret to your .env file into the ZOOM_CLIENT_ID and ZOOM_CLIENT_SECRET fields.
  9. Set the Redirect URL for OAuth < URL>/api/integrations/zoomvideo/callback replacing URL with the URI at which your application runs.
  10. Also add the redirect URL given above as a allow list URL and enable "Subdomain check". Make sure, it says "saved" below the form.
  11. You don't need to provide basic information about your app. Instead click at "Scopes" and then at "+ Add Scopes". On the left, click the category "Meeting" and check the scope meeting:write.
  12. Click "Done".
  13. You're good to go. Now you can easily add your Zoom integration in the settings.

Obtaining Daily API Credentials

  1. Open Daily and sign into your account.
  2. From within your dashboard, go to the developers tab.
  3. Copy your API key.
  4. Now paste the API key to your .env file into the DAILY_API_KEY field in your .env file.


Distributed under the AGPLv3 License. See LICENSE for more information.


Special thanks to these amazing projects which help power