Calendly works until you realize every booked call, every guest email, and every cancellation policy clause lives in someone else's database. You want a booking page on your domain that talks to Google Calendar without sending half your client list to a US SaaS dashboard.
Cal.diy (calcom/cal.diy) is the community fork aimed at self-hosters. MIT license, TypeScript and Next.js under the hood, PostgreSQL via Prisma, and the same “pick a time” UX people know from Cal.com. Homepage: cal.diy. The upstream README is blunt: it removed Cal.com’s enterprise-only code paths so you are not chasing license keys for features that only exist on paper.
What Cal.diy actually is
Cal.diy strips the commercial “open core” split. No Teams, Organizations, Insights, Workflows, or SSO/SAML stack that Cal.com sells to enterprises. What remains is personal and small-team scheduling you run yourself: event types, availability rules, calendar connections, booking pages, and the integrations the community still ships.
The project itself warns that self-hosting is for people comfortable with servers, databases, and securing booking data. They call it a fit for personal, non-production use unless you know what you are doing. That honesty is worth repeating before you point your sales team at it.
Stack: Node 18+, PostgreSQL 13+, Yarn install, NEXTAUTH_SECRET and CALENDSO_ENCRYPTION_KEY in .env, then migrations. It is a modern JS monorepo (tRPC, Tailwind), not a single PHP file. Plan memory and build time on the VPS.
Why self-host?
Booking pages leak metadata: who met whom, when, and with what email. For Canadian consultants, clinics-adjacent schedulers, or agencies under client NDAs, “our scheduler runs in Postgres on infrastructure we control” beats “we use a US calendar startup.” You still connect Google or Microsoft calendars; you choose what stays on your box.
Cal.com’s hosted product is the path if you want support and enterprise features. Cal.diy is the path if you want MIT code, no license server, and accept that you are the ops team.
Running it for real
Treat it like any Next.js app: reverse proxy with TLS, process manager or Docker, Postgres backups, and OAuth app credentials for each calendar integration you enable. Updates are yarn pulls and migrations, not apt upgrade.
Do not underestimate webhook URLs, email delivery for confirmations, and timezone math when daylight saving hits Edmonton and Toronto differently. Test cancellations and reschedule flows before you replace the Calendly link in your email signature.
Good fit / skip it
Good fit: solo consultants, indie hackers, internal “book a support slot” pages, dev teams that already run Node and Postgres and read README warnings.
Skip it: large orgs needing SAML and org-wide analytics (use Cal.com commercial), anyone expecting cPanel one-click simplicity, or teams without appetite for JS app maintenance.
Hosting in Canada
Give Cal.diy a CloudBox VPS with at least 2 GB RAM for Node builds and Prisma. Run PostgreSQL locally or on a small managed instance. Keep the database and uploaded assets in Canada if residency matters to your privacy policy.
Bottom line
Cal.diy is self-hosted Cal.com for the community edition: MIT, no enterprise upsell, Postgres, and booking pages you own. Read the project’s own risk disclaimer, then deploy like a production app if your business depends on it.
Talk with Swift Host if you want Node, Postgres, and TLS on Canadian VPS hosting. We are in St. Albert and actually answer the phone.