Self-hosted Calendly alternatives: which one fit work?
Compare Cal.com, Easy!Appointments, Rallly and DayOtter for VPS hosting, calendar sync both ways, public booking pages and outbound email delivery.
Di short answer
A self-hosted Calendly alternative gots to do one thing wey internal tools for your VPS never dey do: answer the public. The booking page na the product. E need real domain name and TLS (transport layer security) from day one, and e gots to deliver mail to people wey never hear about your server before.
Four projects cover the realistic options. Cal.com, wey self-hostable code don now release as MIT-licensed Cal.diy, na the closest match to Calendly, but Cal.diy README recommend personal, non-production use. Easy!Appointments na the lighter one, PHP and MySQL, and e dey okay for 1 GB VPS. Rallly na group poll tool and e no get booking page at all. DayOtter na the newest option, an AGPLv3 scheduling platform wey get confirm-first assistant in front of am.
Two questions go decide which one you fit actually run. E fit sync both ways with the calendar wey you already dey use? And e fit send mail? Na the second question dey make most self-hosted booking setups fail quietly, so e go come first.
Outbound email na the part wey dey fail
Booking confirmation fit enter stranger inbox. Na transactional mail wey dey land for Gmail or Microsoft 365 be this, and those receivers dey judge you by the sending IP address and your DNS records.
Sending directly from the VPS dey run into provider restrictions. Providers including Hetzner and DigitalOcean dey block outbound TCP port 25 by default. Even when port 25 dey open, fresh VPS address no get sending history, and big receivers dey treat unknown hosting-range addresses as suspicious. The booking go enter database, page go show confirmed, but nobody go receive email. From the server side, nothing go look broken. Na why client wey never show up often discover the problem weeks later.
Use a relay. Choose transactional mail provider wey support SMTP, and the app go need its hostname, port and authentication settings. Check whether the port dey reachable before you touch application config:
nc -vz -w 5 "$SMTP_HOST" 587A succeeded line mean say the path dey open. If the connection hang or show Connection refused, na network level block dey cause am, and editing .env no go fix am. Relays dey listen on 587 or 465, but those ports no dey open everywhere: DigitalOcean dey block both by default, while Hetzner dey block 465 but allow 587. If SMTP dey blocked, use provider HTTP API where the app support am, or arrange SMTP route wey dem allow.
Each project dey handle the relay differently. Cal.com dey read EMAIL_FROM, EMAIL_SERVER_HOST, EMAIL_SERVER_PORT, EMAIL_SERVER_USER and EMAIL_SERVER_PASSWORD, and e also accept RESEND_API_KEY instead. Watch that one well: the shipped .env.example dey point EMAIL_SERVER_HOST to localhost for port 1025, and na local development mailbox be that. If you leave the default, real recipients no go receive the mail. Rallly dey take SMTP_HOST, SMTP_PORT, SMTP_USER and SMTP_PWD. DayOtter dey take SMTP settings or Resend key. Easy!Appointments dey send its notifications from the application, and its Docker image dey take MAIL_SMTP_HOST, MAIL_SMTP_PORT, MAIL_SMTP_USER and MAIL_SMTP_PASS, so point dem to the same relay before you accept real booking. Set MAIL_PROTOCOL=smtp, enable MAIL_SMTP_AUTH=1 for authenticated relay, and set MAIL_SMTP_CRYPTO to match the relay TLS settings.
Then publish the DNS records wey your relay give you. SPF (sender policy framework) record dey state which servers fit send for your domain, while DKIM (domainkeys identified mail) key dey sign each message so receiver fit prove say nobody alter am. Add DMARC (domain-based message authentication, reporting and conformance) policy after both checks pass. Send test booking to real address for a big provider, open the message headers, and confirm say the authentication lines read pass. Booking page wey no fit send mail worse than no booking page, because e fit fail without showing any sign.
Calendar backend wey really sync both ways
Sync get two directions, and dem fit fail separately. Read direction na availability: app must see the busy blocks wey already dey your calendar, or e fit give person time wey you don already book. Write direction na the booking itself: confirmed event must show for the calendar wey you actually dey check, no be only inside booking tool.
Google Calendar and Microsoft 365 fit do both directions, but one condition dey for self-hosted install. You must create the OAuth (open authorization) client yourself, because hosted product client ID no dey inside source code. For Cal.com, Google dey use GOOGLE_API_CREDENTIALS inside .env and .env.appStore, where you go keep the JSON wey you download from Google Cloud console; Microsoft dey use MS_GRAPH_CLIENT_ID and MS_GRAPH_CLIENT_SECRET inside .env. DayOtter dey use GOOGLE_CLIENT_ID and GOOGLE_CLIENT_SECRET for Google, and MICROSOFT_CLIENT_ID and MICROSOFT_CLIENT_SECRET for Microsoft.
Two things fit break this setup, and e good make you know dem before you start. First, redirect URI wey you register must match your public URL exactly, including scheme and any trailing path. If e no match, Google go stop the connection with redirect_uri_mismatch for consent screen. Second, Google project wey remain for Testing publishing status go issue refresh tokens wey expire after seven days. Sync go work throughout the week, then stop, and app logs go show invalid_grant for the next refresh. Move consent screen to In production, or accept say you go reconnect am manually every Monday.
CalDAV (calendaring extensions to WebDAV) na the open option, but support no broad. Cal.com dey ship CalDAV app wey still get beta marking. Dem don verify am against servers including Baikal, Radicale, Nextcloud and Kerio Connect. Apple iCloud get its own Apple Calendar app. E dey use CalDAV to talk to iCloud, and e need app-specific password instead of your Apple ID password. DayOtter list Apple through CalDAV together with Google and Microsoft 365.
ICS feed no be sync. Subscribed .ics URL na read-only by design, so e fit block time for your booking page, but e no fit ever receive the booking. If tool only offer ICS for your calendar, half of the setup dey available, and you go still copy events manually.
Easy!Appointments dey sync Google Calendar and, since version 1.5, any CalDAV server for both directions. Rallly no dey read availability at all. E dey collect votes for a set of candidate dates. Na the correct tool for "when can the six of us meet" and the wrong tool for "book 30 minutes with me".
Booking page public, so TLS na first priority
Most things wey people self-host dey private. Wiki, board, dashboard — all of dem fit sit behind VPN or SSO login and never show for open internet. Booking link no fit work like that. Anybody wey you send am to must load am, and this change the setup for 3 clear ways.
You need domain name wey get A record pointing to the VPS for the domain-based setup below and Google's public OAuth redirects. You need certificate from day one, because browsers mark plain HTTP form as not secure, and your client dey type name and email inside am. You also need set the app's public URL correctly for the config, because that value dey inside links for outgoing email and OAuth redirect URIs. Set NEXT_PUBLIC_WEBAPP_URL for Cal.com, DOMAIN for Rallly, BASE_URL for Easy!Appointments, or DAYOTTER_DOMAIN during installation, then set am to the https:// address wey you go really use.
Rallly and DayOtter handle TLS for you. Rallly's bundled stack include Traefik and issue Let's Encrypt certificates with the address for ACME_EMAIL. DayOtter's installer start Caddy with automatic HTTPS. Cal.com and Easy!Appointments no do this, so you go put nginx in front and issue the certificate yourself, the same way you go do for Let's Encrypt certificate for nginx with Certbot. Bind the app container to 127.0.0.1 so the only way to enter na through the proxy wey you control. If the same box already dey run self-hosted Trello alternative for your internal boards, keep am behind your existing auth and give only the booking host public server block.
Cal.com for your VPS
The Docker configuration dey inside the Cal.diy repository, but the official calcom/cal.diy Docker Hub repository no get any tagged images as of 8 November 2026. Build the app image from the repository before you start am:
git clone --recursive https://github.com/calcom/cal.diy.git
cd cal.diy
cp .env.example .env
openssl rand -base64 32
openssl rand -base64 24
docker compose build calcom
docker compose up -d database calcomThe first random value go inside NEXTAUTH_SECRET and the second one go inside CALENDSO_ENCRYPTION_KEY. Both of dem dey necessary. Set DATABASE_URL and point NEXT_PUBLIC_WEBAPP_URL to your public address before you build. Set POSTGRES_USER, POSTGRES_PASSWORD, POSTGRES_DB and DATABASE_HOST to match your database service, because the compose file dey use dem to build the app database URL. The docs talk say the bundled stack na the web app, PostgreSQL and Prisma Studio, but the current docker-compose.yml define the database, Redis, calcom and calcom-api, without any Prisma Studio service. The command wey dey up so go start only the database and the app. The docs give docker compose up -d calcom for running the app alone against a database wey you host for another place, but the current compose file still need one override to remove the bundled database dependency and put the external database URL.
The README NODE_OPTIONS="--max-old-space-size=16384" example na tip for development, e no be mandatory 16 GB build requirement. The current Dockerfile default its MAX_OLD_SPACE_SIZE build argument to 6144 MiB; that one na Node heap limit, e no be minimum RAM specification. Build am for another machine if your VPS no fit handle the build. The docs -arm image-tag advice no go work for pull since Docker Hub no get tagged images. The installation docs no give any minimum runtime memory figure, so make you use 2 GB for the app plus PostgreSQL as my working figure instead of official one, and watch the memory during the first week.
Check whether e don start:
docker compose ps
docker compose logs -f calcom
curl -sI https://cal.example.com | head -n 1The curl suppose return 307 Temporary Redirect to /auth/login for request wey no get authentication; the command go print only the status line and e no go follow the redirect. A 502 Bad Gateway from nginx while the container dey show say e dey run usually mean say the first boot still dey apply database migrations. Give am some minutes and read the logs before you conclude say e don spoil. Cal.com webhooks dey fire for every confirmed booking, so one booking fit trigger any automation wey you already dey run, for example one n8n instance wey you fit reach over HTTPS for your VPS.
The licence change on 15 April 2026. Cal.com relaunch their free and open-source code as Cal.diy under the MIT License, and the code for their commercial edition no dey public again. No more AGPLv3 core or public enterprise directory. The Cal.diy README talk say Teams, Organizations, Insights, Workflows, SSO/SAML and other enterprise-only features don commot, so round-robin and collective event types, wey belong to teams, no dey the edition wey you fit self-host. Plan am as one-person booking tool.
Easy!Appointments for 1 GB box
Requirements na Apache or Nginx, PHP 8.2 or newer, and MySQL. Official image dey for alextselegidis/easyappointments.
Make we warn you about one thing first. The docker-compose.yml wey dey repository na development environment. E expect make you open shell inside the container and run npm install && composer install && npm start. E no be deployment. Use the published image instead:
services:
easyappointments:
image: alextselegidis/easyappointments # pin the current tag from Docker Hub
environment:
- BASE_URL=https://book.example.com
- DB_HOST=mysql
- DB_NAME=easyappointments
- DB_USERNAME=easyapp
- DB_PASSWORD=change-me
ports:
- '127.0.0.1:8080:80'
depends_on:
- mysql
mysql:
image: mysql:8.0
environment:
- MYSQL_ROOT_PASSWORD=change-me-too
- MYSQL_DATABASE=easyappointments
- MYSQL_USER=easyapp
- MYSQL_PASSWORD=change-me
volumes:
- ./mysql:/var/lib/mysqlBASE_URL must be the public HTTPS address. If you set am wrong, booking links inside confirmation emails go point to host wey your client no fit reach. The image dey serve plain HTTP for port 80 without its own certificate. Na why dem bind the port to 127.0.0.1 and nginx terminate TLS for front. If compose syntax still new to you, start with Docker Compose basics for VPS and come back.
This na the lightest option here by far. Two containers, one PHP application and MySQL, fit run comfortably for 1 GB VPS. The trade-off na reach: Google Calendar and CalDAV na the only calendar backends, and the interface na traditional admin panel instead of modern booking flow. Nextcloud and Fastmail both support CalDAV, so either one go work. If your calendar na Microsoft 365, Easy!Appointments no get documented native connector for am. Since version 1.6.0, CalDAV safety check dey enabled by default. E stops the connection from reaching internal services for the server network. Since version 1.6.1, administrators fit allow private calendar server through Settings → Integrations → CalDAV → Allowed Connection URLs, or use the connection dialog Allow and connect button.
Rallly for group polls
Rallly dey answer different kain question. E no dey publish your availability. E dey show set of candidate times give group make dem vote, wey be wetin you need for board meeting, but e no go work for client booking link.
curl -fsSL https://get.rallly.co | bashRead any script before you pipe am enter shell. Swap bash with less, read wetin e dey do, then run am. The manual path dey do the same work for steps wey you fit see:
git clone https://github.com/lukevella/rallly-selfhosted.git
cd rallly-selfhosted
./rallly.sh setup
./rallly.sh startThe requirements wey dem document na at least 2 GB of RAM, Docker 19.03 or newer with Compose v2, ports 80 and 443 must dey free, and domain must point go the server. The bundled stack get Traefik for HTTPS, the web application, PostgreSQL, and Garage for S3-compatible object storage. Set DOMAIN, SECRET_PASSWORD wey reach at least 32 characters, SUPPORT_EMAIL and INITIAL_ADMIN_EMAIL. If you don dey run reverse proxy already, set PROXY_MODE=external and WEB_PORT, so Traefik go comot for road. If you don dey run self-hosted S3-compatible object store with MinIO, point the S3_* variables go there and comot the Garage container.
SMTP dey deliver the default sign-in code emails and notifications. If relay no work, those sign-in emails no go arrive, including the one for the admin account wey you just create. Rallly also support SSO, and EMAIL_LOGIN_ENABLED=false go disable email sign-in when you don configure SSO provider.
Rallly self-hosting licence page get free Personal tier for one registered user and e dey ask make multi-user installations buy licence. Guest voters no dey count for that user limit.
DayOtter, di latest arrival
DayOtter na AGPLv3 scheduling platform wey get assistant join am. Di production install na just one command:
curl -fsSL https://raw.githubusercontent.com/Dayotter/dayotter/main/deploy/install.sh \
| sudo DAYOTTER_DOMAIN=cal.example.com bashRead am well before you run am, as we talk before. Di installer go setup Docker, generate secrets, and start di full stack: di Next.js web app, one background worker wey dey handle reminders, calendar sync, and webhooks, PostgreSQL, Redis, and Caddy wey get automatic HTTPS. One-shot migration service go update di database before di web app and worker start.
Calendar support cover Google, Microsoft 365, Apple through CalDAV, and ICS feeds, with di ICS caveat wey we mention before. Optional integrations dey use environment variables, including SMTP or Resend for mail, ANTHROPIC_API_KEY for di assistant, Twilio for SMS, and Stripe for payments. Di assistant dey use "confirm-first" style: e go propose, you go approve, and nothing go enter your calendar without your direct yes. If you no configure di AI provider, dat part of di product no go run at all. Di default provider na Anthropic; AI_PROVIDER=openai go select OpenAI or any OpenAI-compatible endpoint instead.
Licensing dey clear for self-hosters. Di core na AGPLv3, and one ee/ directory get commercial cloud-only licence wey no dey active unless you set DAYOTTER_CLOUD=1. Dis mean say di team features wey dem dey bill $9 per seat every month for di hosted plan, as of October 2026, dey available for your own server.
Dis one na di heaviest stack for here and e be di youngest project. Run am side-by-side with your existing booking link for two weeks, take real bookings through both, and read di worker logs before you move your clients over.
Wetin each stack really dey cost you
The number of containers na the honest way to estimate how much resources stack go need for small VPS, because every service get its own minimum memory need. These na the number of long-running services for each project own published Docker stack, as checked on 8 November 2026. DayOtter also define one one-shot migration service, but e no dey inside the running count.
Di data wey dey behind dis chart
[
{
"tool": "Easy!Appointments",
"containers": 2,
"database": "MySQL"
},
{
"tool": "Cal.com",
"containers": 4,
"database": "PostgreSQL and Redis"
},
{
"tool": "Rallly",
"containers": 4,
"database": "PostgreSQL"
},
{
"tool": "DayOtter",
"containers": 5,
"database": "PostgreSQL and Redis"
}
]Easy!Appointments need 2 containers and e fit run for 1 GB. Rallly bundled stack na 4, and its documentation ask for 2 GB. DayOtter installer start 5 long-running services, na why e need the biggest server among the 4 here. Cal.com and DayOtter installation docs no give minimum memory figure, so 2 GB na my starting point for both, not a supported number.
Two of these counts go reduce if you already dey run the infrastructure. Rallly Traefik and Garage containers go comot when you point am to your own proxy and object storage. Cal.com current compose file no get Prisma Studio service, and its Redis and calcom-api services go remain off as long as you start only database and calcom.
Which self-hosted Calendly alternative you suppose pick
Solo consultant suppose check Cal.diy well. E combine booking page wey people know and CalDAV path for people like us wey no dey keep calendar for Google or Microsoft. But the README recommend am for personal, non-production use, and official Docker Hub repository no get tagged images to pull. One PostgreSQL database and one application container na maintenance load wey you fit carry for years. Keep time for image build, OAuth client, and mail relay. Also remember say CalDAV app still dey beta, so test one real booking from beginning reach end before you publish the link.
Small team suppose look DayOtter. Weighted round robin and collective booking dey inside the AGPLv3 core. So when you self-host am, you get features wey hosted seat dey charge for. Cal.com's self-hostable Cal.diy don remove team scheduling completely. The worker process dey built for reminders and webhooks wey team really depend on. The trade-off na maturity: na the newest project for this list, so run am alongside the old one first. Keep the old link active until you don monitor one full month of bookings.
Two narrower cases. If na only poll you need to find time wey group fit meet, install Rallly and stop there. If you get 1 GB VPS, you dey use Google Calendar or CalDAV server like Nextcloud, and you want the smallest thing wey fit receive booking, Easy!Appointments go last pass every more complex option wey you fit put for that box. For the wider question of wetin else deserve space for the same server, see wetin worth self-hosting for 2026.
FAQ
I fit run a self-hosted booking page without domain name?
Yes, but calendar integrations get their own requirements. DayOtter's installer dey serve plain HTTP for the server public IP when DAYOTTER_DOMAIN no set. Let's Encrypt now dey issue IP address certificates wey valid for 160 hours, so HTTPS itself no longer need domain. Google's web OAuth redirect rules still dey reject public IP addresses. Buy the domain first, point one A record to the VPS, then install if you want the Google Calendar setup wey we describe here.
Why my booking confirmation emails no dey ever arrive?
First check the app mail configuration and the server outbound mail policy. Providers including Hetzner and DigitalOcean dey block outbound port 25 by default, and even where e dey open, new address no get sending reputation. Point the app to transactional mail relay for allowed port, confirm say the port dey reachable with nc -vz -w 5 "$SMTP_HOST" 587, then publish the SPF and DKIM records wey the relay give you. DigitalOcean also dey block ports 587 and 465 by default, so use HTTP mail API where e dey supported or arrange allowed SMTP route. If you dey run Cal.com, check say you replace the shipped EMAIL_SERVER_HOST=localhost and EMAIL_SERVER_PORT=1025 defaults, wey dey point to local development mailbox.
Self-hosted Cal.com dey sync with CalDAV, or na only Google?
Both, but their maturity no be the same. The CalDAV app get beta label and dem don verify am against servers including Baikal, Radicale, Nextcloud and Kerio Connect. Apple iCloud dey connect through separate Apple Calendar app wey use app-specific password. Google Calendar and Microsoft 365 both dey sync in both directions, but for self-hosted install you must create your own OAuth clients: Google dey use GOOGLE_API_CREDENTIALS for .env and .env.appStore, while Microsoft dey use MS_GRAPH_CLIENT_ID and MS_GRAPH_CLIENT_SECRET for .env.
Why my Google Calendar sync stop working after one week?
Na because the Google Cloud project still dey for Testing publishing status. Google dey issue refresh tokens to apps for that state, but dem expire after seven days. So the connection go work, then e go fail for the next token refresh, and the application log go show invalid_grant. Move the OAuth consent screen to In production and reconnect the calendar once. If you reconnect without changing the status, you go get another seven days only.
Which of these go run for 1 GB VPS?
Easy!Appointments go run, because na PHP application plus MySQL. Rallly document 2 GB minimum, and its bundled stack dey run four services. Cal.com and DayOtter's installation docs no give minimum memory figure, but Next.js application with PostgreSQL, plus Redis and worker process for DayOtter, mean say you suppose plan for 2 GB or more. Cal.diy's README present the 16 GB Node heap setting as adjustable development tip, no be build requirement. Its Dockerfile set build heap limit to 6144 MiB by default, and the official Docker Hub repository no get tagged images to pull. Build for another machine if the VPS no fit handle am.