{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifkew4uiawocfgymlls5bhhtrhjj4ur4kxye7htaajsn5dbzohcay",
    "uri": "at://did:plc:yaz3p6kpjacwypalo2scppxc/app.bsky.feed.post/3mmgjaskvyqt2"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreibpttwflu5plirkla6zep2fya3ybxdcqiuvl7e7qeijxmsx764tz4"
    },
    "mimeType": "image/png",
    "size": 209398
  },
  "description": "Cal.com is the open source alternative to Calendly — self-hostable, API-first, and built for teams. In April 2026 it went partially closed-source. Here's what changed, what it means, and whether it's still worth using.",
  "path": "/calcom-open-source-scheduling-calendly-alternative/",
  "publishedAt": "2026-05-22T08:27:41.000Z",
  "site": "https://devopspack.com",
  "tags": [
    "Pipoline",
    "Get in touch"
  ],
  "textContent": "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.\n\nCal.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.\n\n## What Cal.com is\n\nCal.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.\n\nIt 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.\n\n## The April 2026 license change — Cal.diy\n\nThis 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.\n\nWhat 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.\n\nWhat 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.\n\nThe 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.\n\nThis 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.\n\n## Core features\n\n  * **Event types** — define meeting types with duration, buffer time, availability windows, and custom questions. One-off meetings, recurring meetings, group events.\n  * **Calendar integrations** — Google Calendar, Outlook/Microsoft 365, iCloud, CalDAV. Reads your availability and blocks time automatically.\n  * **Video conferencing** — Zoom, Google Meet, Microsoft Teams, Huddle, Cal Video (native). Auto-generates meeting links on booking.\n  * **Team scheduling** — collective availability (everyone must be free), round-robin (distribute bookings across team), fixed hosts.\n  * **Routing forms** — ask bookers questions, route them to the right team member based on their answers. The key feature for sales and support teams.\n  * **Availability** — set working hours, date overrides, minimum notice periods, buffer between meetings, and daily booking limits.\n  * **Payments** — Stripe integration for paid consultations and bookings\n  * **Workflows/automations** — send confirmation emails, SMS reminders, and follow-ups at configurable intervals before and after meetings\n  * **Embeds** — embed the booking widget inline, as a popup, or as a floating button on any website\n  * **API + webhooks** — REST API for full programmatic control, webhooks for event notifications\n  * **App store** — 100+ integrations including CRMs, payment processors, video tools, and automation platforms\n  * **Cal.ai** — AI scheduling assistant that can handle booking via natural language\n\n\n\n## Self-hosting Cal.diy\n\nCal.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.\n\nThe broad requirements:\n\n  * Node.js 18+\n  * PostgreSQL 13+\n  * A reverse proxy (Nginx/Caddy) with SSL\n  * SMTP for email notifications\n  * API keys for whichever calendar integrations you want\n\n\n\nFor 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.\n\n## Cal.com cloud vs self-hosted\n\nCal.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.\n\nSelf-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.\n\n## Cal.com vs Calendly\n\nCalendly 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.\n\nCal.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.\n\nCalendly'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.\n\n## Who it's for\n\n**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.\n\n**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.\n\n## My take\n\nCal.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.\n\nFor 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.\n\n## Need help setting up Cal.diy?\n\nGetting 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.",
  "title": "Cal.com: Open Source Scheduling Infrastructure and What Changed in 2026",
  "updatedAt": "2026-05-22T08:27:41.864Z"
}