Cal.com vs Calendly: Real Cost for a Growing Team

A 20-person team on Calendly Teams pays $3,840 a year. The same team on Cal.com Teams pays $2,880. And the third option every comparison used to recommend, self-hosting Cal.com for free, changed in April 2026: the open-source repository no longer ships team features at all. Here is the full math, what self-hosting actually gets you today, and the costs both vendors leave off the pricing page.

The short version

• Solo user, simple booking page: Cal.com's free tier is the strongest free plan of the two. It includes unlimited event types, calendar connections, Stripe and PayPal payments, and even some SMS notifications, all for one user. Calendly's free plan limits you to one event type and one connected calendar.
• Team that needs round robin and shared booking: Cal.com Teams at $12 per user per month beats Calendly Teams at $16 per seat per month, both on annual billing. That is a 25% difference, every month, per seat.
• Team that needs Salesforce or form-based routing: Calendly includes Salesforce and HubSpot, Marketo, or Pardot form routing in its Teams plan. Cal.com gates advanced routing behind Organizations at $28 per user per month.
• Team that needs SSO: Calendly sells single sign-on as an add-on to Teams, or bundles it into Enterprise, which starts at $15,000 a year with a 50-seat minimum. Cal.com includes SAML SSO in Organizations.
• Self-hosting for free: what is left is Cal.diy, the MIT-licensed community edition, recommended by its own maintainers for personal, non-production use. No teams, no round robin, no workflows. Details below.
• Self-hosting with team features: that is now Cal.com's commercial Enterprise product, priced through their sales team.

What each plan costs at 5, 20 and 50 seats

Both vendors quote per-month prices that require annual payment. Calendly advertises saving up to 20% for paying yearly, which means monthly billing runs up to roughly 25% above the figures below. All numbers come from the official pricing pages: Cal.com pricing and Calendly pricing, checked in September 2026.

Five seats, annual billing:

• Calendly Standard ($10 per seat): $600 a year
• Calendly Teams ($16 per seat): $960 a year
• Cal.com Teams ($12 per user): $720 a year
• Cal.com Organizations ($28 per user): $1,680 a year

Twenty seats, annual billing:

• Calendly Standard: $2,400 a year
• Calendly Teams: $3,840 a year
• Cal.com Teams: $2,880 a year
• Cal.com Organizations: $6,720 a year

Fifty seats, annual billing:

• Calendly Standard: $6,000 a year
• Calendly Teams: $9,600 a year
• Cal.com Teams: $7,200 a year
• Cal.com Organizations: $16,800 a year
• Calendly Enterprise: from $15,000 a year, and you pay for 50 seats even if you have 35 people

A worked example: a 20-person recruiting and operations team

Say you run a 20-person team. You need round robin so candidates land on whichever interviewer is free, collective events for panel interviews, automated reminders to cut no-shows, and routing from your HubSpot forms.

• On Calendly, round robin and form routing sit in Teams: 20 x $16 = $3,840 a year.
• On Cal.com, round robin and team event types sit in Teams: 20 x $12 = $2,880 a year. If your routing needs are basic, Teams covers you.
• Difference: $960 a year in Cal.com's favor, every year, for the same headcount.

Now add a compliance requirement: your IT team wants SAML SSO.

• On Cal.com, SSO means Organizations: 20 x $28 = $6,720 a year.
• On Calendly, SSO is an add-on to Teams at an unlisted price, or part of Enterprise at $15,000 a year minimum. With only 20 seats you cannot even buy Enterprise; the add-on is your only path, and you have to talk to sales to learn what it costs.

The pattern to notice: the "cheapest" vendor flips depending on which single feature gates you. Price your actual feature list, not the logo.

The April 2026 change most comparisons have not priced in

Almost every "Cal.com vs Calendly" article ranking today makes the same argument: Calendly charges per seat, but Cal.com is open source, so a technical team can self-host it and pay nothing. That argument was built on the old AGPL-licensed repository, and it died in April 2026.

On April 14, 2026, Cal.com announced it was going closed source, citing AI-driven security threats: AI coding assistants have made it far easier to find vulnerabilities in publicly available code. A day later, their engineering team published the technical details, and the v6.4 changelog formalized the new structure:

• The production codebase is private. Hosted Cal.com customers see no change.
• The old public repository became Cal.diy, an MIT-licensed community edition at github.com/calcom/cal.diy, maintained by former Cal.com interns and described by the maintainers themselves as "strictly recommended for personal, non-production use" and "use at your own risk".
• Companies that self-host the enterprise edition receive invites to the private repository.

What matters for your budget is what Cal.diy no longer contains. Removed from the open-source edition: Organizations and Teams (including round robin, collective events, and team booking flows), Routing Forms, the Workflows engine (reminders, follow-ups, triggers), SAML and SSO, Insights dashboards, Instant Booking, the AI phone agent, booking audit logs, and API v1.

Read that list again. Everything a growing team actually buys Cal.com for is on it. The core scheduling engine, booking flows, the app store, and API v2 remain, which is plenty for one person's booking page and not enough for a team's.

What self-hosting Cal.diy actually costs

If you are a solo founder or consultant, self-hosting Cal.diy is still the cheapest serious scheduling setup that exists. The official Docker quickstart is genuinely short:

1. Rent a small VPS. Cal.diy needs a Next.js runtime and PostgreSQL 13 or newer. A Hetzner CX33 (4 vCPU, 8 GB RAM, 80 GB disk, 20 TB traffic) costs EUR 8.99 a month; a 4 GB CX23 at EUR 5.99 works if you are careful.
2. Clone the repository, copy .env.example to .env, and generate the two required secrets (openssl rand -base64 32 for NEXTAUTH_SECRET, openssl rand -base64 24 for CALENDSO_ENCRYPTION_KEY).
3. docker compose up -d starts the app, PostgreSQL, and Prisma Studio. The setup wizard creates your first user on first run.
4. Updates are docker compose pull followed by docker compose up -d.

The honest bill for a single-user instance:

• Infrastructure: about EUR 108 a year on Hetzner, plus a domain and an SMTP service for booking emails.
• Time: budget an hour or two a month for updates, backups, and certificate renewals. There is no managed upgrade path and no support contract.
• What you get: your booking page, your data on your hardware, unlimited event types, payments, and API v2.
• What you do not get: round robin, team pages, routing forms, automated reminder sequences, SSO, audit logs, or anyone to call when it breaks.

We deploy and manage open-source tools for clients as part of our managed open-source stack work, and we have done the same build-versus-buy math for the whole stack in the real cost of replacing SaaS with an open-source stack and for individual tools, for example Formbricks vs Typeform at 5,000 responses a month. The pattern repeats: self-hosting wins on cash cost for small, single-purpose deployments, and loses as soon as you need the collaboration features the vendor holds back.

When self-hosting is the wrong choice

• You need anything multi-person. Round robin, collective events, and team scheduling were removed from the open codebase. Self-hosting no longer gets you team features, full stop.
• You cannot own security updates. The maintainers say plainly that Cal.diy is use-at-your-own-risk. If nobody on your team will apply patches within days of a release, you are running internet-facing scheduling software with known-lagging fixes.
• You considered forking the old AGPL code. The pre-April-2026 repository is no longer maintained upstream. Keeping a team-capable fork patched against a codebase whose maintainers have moved on is a part-time engineering job, and it costs far more than the $2,880 a year a 20-seat Teams plan does.
• You have compliance obligations. No audit log, no SSO, no access controls beyond a single user. Banks, insurers, and law firms should not put client-facing scheduling on Cal.diy.
• Email deliverability matters. Hosted vendors warm and monitor their sending infrastructure. On your own VPS, booking confirmations landing in spam is your problem to diagnose.

The costs both vendors leave off the pricing page

• Annual lock-in. Both headline prices assume you pay for a year upfront. Calendly's own page frames it as "save up to 20%" for annual billing, so month-to-month costs meaningfully more.
• Seat creep. Every contractor, temp interviewer, or part-time SDR who needs a bookable link needs a paid seat on both platforms. Audit seats quarterly.
• SMS credits on Cal.com. Hosted Cal.com draws SMS reminders from credits. Light usage is covered even on the free plan, but heavy SMS volume across a team becomes a real line item.
• Calendly's AI add-ons. Calendly sells its notetaker and phone agent as bundles: Standard Plus at $16 per seat and Teams Plus at $21 per seat on annual billing. If you want Teams plus the notetaker, your real per-seat price is $21, which puts 20 seats at $5,040 a year, above Cal.com Organizations pricing territory for some teams.
• Enterprise floors. Calendly Enterprise starts at $15,000 a year with a 50-seat minimum. A 35-seat company pays for 50 seats. Cal.com's Enterprise is custom-priced through sales.
• Integration gating. Salesforce routing is Teams-and-up on Calendly and Organizations-and-up on Cal.com. One integration requirement can double your per-seat price, so map integrations before you compare stickers.
• Migration labor. Event types, routing forms, embeds, and reminder sequences do not export between platforms. Rebuilding them is a project. If your follow-up sequences are complex, this is a good moment to move them into a general automation layer instead; we do that kind of work under our business automation service, and it survives the next scheduling-tool switch.

Common mistakes when comparing Cal.com and Calendly

1. Comparing Calendly Teams to Cal.com Free. Cal.com's free tier is one user. The moment you need two bookable team members, you are on a paid plan on both platforms.
2. Quoting pre-2026 articles that call Cal.com "free and open source." The open-source edition lost its team features in April 2026. Any comparison that does not mention Cal.diy by name is stale.
3. Comparing annual prices to monthly budgets. Both vendors bill the quoted price annually. A "$12 per month" plan is a $144 charge per user, once a year.
4. Buying a higher tier for one feature you use twice a year. If one person needs routing forms, a form tool feeding a shared booking link may be cheaper than upgrading all 20 seats.
5. Underestimating self-host operations. Updates, backups, SMTP deliverability, and monitoring are yours. An unmaintained scheduling instance is a security incident with a calendar attached.
6. Ignoring the pilot. Both platforms have free tiers. Run your real booking flows with real invitees for two weeks before signing an annual contract.

A decision checklist

• Write down the features you use weekly: round robin, collective events, routing forms, reminder sequences, payments, SSO. Map each to the cheapest plan on each platform that includes all of them.
• Price both platforms at your current headcount and at 50% growth, on the billing cycle you will actually choose.
• If SSO or audit logging is a hard requirement, get the real add-on or Enterprise quote from Calendly sales before assuming Cal.com Organizations is expensive.
• If you are considering self-hosting, name the person who applies security updates and how quickly. If you cannot, stop considering it.
• Check your SMS reminder volume against Cal.com's credit pricing if reminders by text matter to you.
• Pilot with the free tiers before any annual commitment.

Frequently asked questions

Is Cal.com still open source? The commercial Cal.com product went closed source in April 2026. The open-source remnant is Cal.diy, an MIT-licensed community edition for self-hosting that no longer includes teams, workflows, routing forms, or SSO.

Which is cheaper for a team, Cal.com or Calendly? For most team use cases, Cal.com. Teams costs $12 per user per month versus Calendly Teams at $16 per seat per month, both billed annually. At 20 seats that is $2,880 versus $3,840 a year. The answer flips if a specific feature, like Salesforce routing, gates you into a higher tier on one platform but not the other.

Can I still self-host Cal.com with team features for free? No. Teams, Organizations, round robin, workflows, and routing forms were removed from the open-source codebase in April 2026. Self-hosting with team features now means a commercial Cal.com Enterprise license, priced through their sales team.

What does Calendly Enterprise actually cost? Calendly's pricing page states Enterprise starts at $15,000 a year with a minimum of 50 seats. It includes SSO, SCIM, domain control, audit logging, and a DPA.

Do Cal.com and Calendly charge for SMS reminders? Hosted Cal.com uses a credits system for SMS, with light usage included even on the free plan and additional credits purchasable. If text reminders are central to your no-show strategy, model the credit cost at your real volume before committing.

Can I migrate from Calendly to Cal.com? There is no one-click export. Event types, routing forms, and reminder sequences need rebuilding, and calendar connections need reauthorizing through Google or Outlook. For a 20-seat team, treat it as a one-week project, not an afternoon.

Where to go from here

If this math says a hosted plan is right for you, take the free tiers for a real two-week pilot and then sign annually with the winner. If it pushed you toward owning your stack instead, scheduling is usually one piece of a bigger decision: CRM, support inbox, email, analytics. We run exactly that stack (Twenty, Chatwoot, Cal.com, Plausible, Listmonk, Formbricks) as a managed service, and we have published the same cost breakdowns for support tools, CRM, and email. If you want an engineer to walk through your numbers, book a call.

Related reading

• Self-Hosting Your Business Stack: Server Sizes and Real Costs