Cal.com: Open Source Scheduling Infrastructure and What Changed in 2026

If you've ever sent someone a Calendly link, you already understand the problem Cal.com solves. Scheduling meetings manually — the back-and-forth emails, the timezone confusion, the "does Tuesday work for you?" threads — is a solved problem. The question is which tool you use to solve it and what trade-offs you're accepting.

Cal.com is the open source answer. Self-hostable, API-first, and built for teams that want control over their scheduling infrastructure. In April 2026 it went partially closed-source, which makes it worth understanding exactly what you're getting in 2026.

What Cal.com is

Cal.com is an open scheduling infrastructure platform. At its core it's a booking system: you share a link, people pick a time that works for both of you, it shows up in both calendars. But it goes significantly further than that — routing forms, team scheduling, round-robin booking, recurring meetings, payments, API access, embeds, webhooks, and an app store with 100+ integrations.

It was founded by Peer Richelsen and Bailey Pumfleet, and its stated mission is to connect a billion people through calendar scheduling by 2031. With 33,000+ GitHub stars it's one of the larger open source projects in the productivity space.

The April 2026 license change — Cal.diy

This is worth understanding before anything else. In April 2026, Cal.com moved its main production codebase from a public repository to a private one. The public repository is now calcom/cal.diy, known as Cal.diy — the open-source, self-hostable, community-driven version under MIT License.

What Cal.diy includes: the full scheduling engine, the app store framework, and the booking infrastructure. Everything that makes Cal.com functional as a self-hosted solution for individuals and small teams.

What was removed from the open-source version: commercial and enterprise features that only apply to Cal.com as a managed service — things like advanced team management, enterprise SSO, and features built specifically for the hosted product's scale.

The stated reason: the rise of AI-powered development and the industry-wide impact on open source economics. Cal.com cited AI tools that can clone and productize open-source software faster than ever, making it harder to sustain commercial development while keeping everything public.

This is the same pattern as HashiCorp/Terraform and MinIO — the commercial entity moves the production code private while open-sourcing a community edition. The difference here is Cal.diy uses MIT License, which is genuinely liberal — more so than BSL or AGPL. If you self-host Cal.diy, you're running fully open-source software with no commercial restrictions.

Core features

• Event types — define meeting types with duration, buffer time, availability windows, and custom questions. One-off meetings, recurring meetings, group events.
• Calendar integrations — Google Calendar, Outlook/Microsoft 365, iCloud, CalDAV. Reads your availability and blocks time automatically.
• Video conferencing — Zoom, Google Meet, Microsoft Teams, Huddle, Cal Video (native). Auto-generates meeting links on booking.
• Team scheduling — collective availability (everyone must be free), round-robin (distribute bookings across team), fixed hosts.
• Routing forms — ask bookers questions, route them to the right team member based on their answers. The key feature for sales and support teams.
• Availability — set working hours, date overrides, minimum notice periods, buffer between meetings, and daily booking limits.
• Payments — Stripe integration for paid consultations and bookings
• Workflows/automations — send confirmation emails, SMS reminders, and follow-ups at configurable intervals before and after meetings
• Embeds — embed the booking widget inline, as a popup, or as a floating button on any website
• API + webhooks — REST API for full programmatic control, webhooks for event notifications
• App store — 100+ integrations including CRMs, payment processors, video tools, and automation platforms
• Cal.ai — AI scheduling assistant that can handle booking via natural language

Self-hosting Cal.diy

Cal.diy runs on Node.js and requires PostgreSQL. Docker is the recommended deployment path. The setup is more involved than single-binary tools like Uptime Kuma — you're deploying a Next.js application with a database, and depending on which features you want (email, SMS, video), there are additional environment variables to configure.

The broad requirements:

• Node.js 18+
• PostgreSQL 13+
• A reverse proxy (Nginx/Caddy) with SSL
• SMTP for email notifications
• API keys for whichever calendar integrations you want

For a solo developer or small team, a $6-12/month VPS handles it without issue. For teams at scale, you'll want to think about database connection pooling and ensuring the booking system stays available — a self-hosted scheduler going down at the wrong moment is a real problem.

Cal.com cloud vs self-hosted

Cal.com cloud (the managed service) starts with a free tier and scales to team and enterprise plans. If you don't want to manage a server, the free tier covers individual scheduling needs well — unlimited event types, calendar connections, and basic team features.

Self-hosting Cal.diy makes sense if: you have privacy or compliance requirements, you want to customize the booking experience beyond what the hosted product allows, or you're building scheduling into a larger application via the API.

Cal.com vs Calendly

Calendly is the established player. It's polished, widely recognized (sending a Calendly link is a normalized behavior), and the free tier is genuinely useful. The limitations become apparent at the team level — round-robin booking, routing forms, and team scheduling require paid Calendly plans that get expensive quickly.

Cal.com's advantages over Calendly: open source and self-hostable, more generous free tier for teams, routing forms available without enterprise pricing, API-first architecture for custom integrations, and better economics if you're building scheduling into a product.

Calendly's advantages over Cal.com: more polished onboarding experience, better mobile apps, wider name recognition (your clients know what a Calendly link is), and more mature enterprise controls.

Who it's for

Good fit: developers building scheduling into applications, teams that need round-robin or routing-based booking, anyone with privacy requirements that make hosted SaaS a non-starter, technical founders who want to self-host rather than pay per seat.

Not the right fit: non-technical users who want a no-setup scheduling tool, anyone who needs clients to immediately recognize and trust the booking interface, teams that rely heavily on mobile for scheduling management.

My take

Cal.com is the most complete open-source scheduling infrastructure available. The April 2026 license change is worth noting — and worth watching — but Cal.diy under MIT is genuinely open, and the feature set for self-hosting hasn't been meaningfully reduced from what was publicly available before.

For anyone building scheduling into a product or needing a self-hosted Calendly alternative, Cal.diy is the answer. For teams who want a managed service with better economics than Calendly at the team tier, Cal.com cloud competes well. The routing forms feature alone, available without enterprise pricing, is a differentiator for sales and support teams.

Need help setting up Cal.diy?

Getting Cal.diy into production — PostgreSQL, Node.js, reverse proxy, calendar OAuth connections, email configuration — involves more moving parts than most self-hosted tools. If you'd rather skip the setup, Pipoline can handle it. Get in touch and we'll figure out what makes sense for your setup.