Cal.com vs YouCanBookMe vs Microsoft Bookings: Which One Fits What You Already Own in 2026?

Updated August 2026

Cal.com, YouCanBookMe, and Microsoft Bookings all do the same basic job: put a link or a page in front of someone so they can grab a slot on your calendar without an email back-and-forth. Past that, they stop being comparable, because none of them started from the same idea about who should own the software, who should pay for it, or what "free" means. The tool that fits you depends less on what it can do and more on what you already have: infrastructure you're willing to run yourself, a brand you want the booking page to reflect, or a Microsoft 365 subscription you're already paying for.

Here's the short version of why these three are different, and why one part of that story genuinely changed in 2026. Cal.com built its reputation as the open-source, self-hostable answer to Calendly, the tool you could run on your own servers if a vendor holding your scheduling data ever bothered you. YouCanBookMe never chased that pitch; it built the deepest brandable, configurable booking page of the three and left self-hosting alone entirely. Microsoft Bookings never tried to be a standalone product at all, it rides inside a Microsoft 365 subscription, and its whole argument is that you shouldn't need a fourth login just to book a meeting. What changed is Cal.com's half of that story, enough that this comparison covers it before it covers price.

This guide prices all three at 5, 25, and 100 people using each vendor's own current pricing page, and it's honest about where a "free" plan stops being free. It also covers Cal.com's license directly, because "open source" does less work in that sentence than it did a year ago, and a reader picking Cal.com to self-host deserves to know that before signing up, not after.

TL;DR

Key Facts

• Cal.com moved its production codebase from a public AGPLv3 repository to a private one in April 2026, citing AI-driven security threats, and now runs its hosted product as closed-source software, according to Cal.com's own announcement.
• Cal.diy, the MIT-licensed fork that survived the split, is described in its own repository as "strictly recommended for personal, non-production use" and is missing Teams and Organizations management, Routing Forms, Workflows, Instant Booking, and SSO.
• YouCanBookMe's own pricing page doesn't display working dollar figures for its paid tiers as of August 2026 (they render as $0 placeholders), and its help center pricing article returns an HTTP 403 error; the figures used here come from Koalendar's pricing guide, checked June 2026, not vendor-confirmed.
• Microsoft Bookings has never been sold as a standalone product. It ships inside Microsoft 365 Business Basic, Business Standard, Business Premium, and specific Enterprise and Frontline plans, per Microsoft's own product comparison page.
• Microsoft 365 Business Basic, Standard, and Premium share a combined cap of 300 users per tenant; organizations past that point move to Enterprise plans like E3 or E5 instead, according to Microsoft's own service description.
• The global appointment scheduling software market was valued at $546.1 million in 2025 and is projected to reach $1,905.90 million by 2034, a 14.70% CAGR, according to Fortune Business Insights.

What Each Tool Is Actually Built For

Before comparing features, it helps to know what each of these three was trying to be when it launched, since that origin still shapes what each is good at today.

Cal.com started as open infrastructure: a self-hostable, API-first alternative to Calendly for developers and technical teams who wanted to run scheduling on their own servers or embed it into their own product. That origin still shows up: unlimited event types and calendars on the free plan, 100-plus integrations, an open API, and Routing Forms for real conditional assignment logic. What's changed is the "self-hostable" half of that pitch, covered in full below.

YouCanBookMe never tried to be infrastructure. It picked one job, a booking page that looks and behaves like it belongs to your business rather than a vendor's template, and went deep on that instead of chasing routing logic or payment processing. Custom branding, conditional workflows, ad-pixel tracking, and a HubSpot handoff are all built around that single job.

Microsoft Bookings isn't a company or even a standalone product. It's an app inside Microsoft 365, and its entire pitch is that a business already paying for Outlook and Teams shouldn't need to evaluate, purchase, and onboard a fourth tool just to let someone book a 30-minute call.

All three also appear in the SimplyBook.me alternatives guide, covered from a different angle alongside other client-booking tools.

Cal.com's License, and What Self-Hosting Actually Means Now

This is worth its own section because most existing coverage of Cal.com describes a company that no longer exists in the same form, and a reader picking Cal.com to self-host needs the current version of the story, not last year's.

For most of its life, Cal.com's production codebase lived in a public GitHub repository under the AGPLv3 license, letting anyone read, fork, and self-host the same code the hosted product ran on. That was the entire differentiator against Calendly: run it yourself, keep the data, skip the vendor relationship if you wanted to.

That changed in April 2026, when Cal.com moved its production codebase from a public repository to a private one, citing AI-driven security threats. The trigger, per the company's own announcement, was watching AI models demonstrate they could systematically scan open-source code for exploitable vulnerabilities, the same transparency that made open source auditable by defenders also made it scannable by attackers faster than any human security team could match. CEO Bailey Pumfleet put it plainly: "Cal.com handles sensitive booking data for our users. We won't risk that for our love of open source." Co-founder Peer Richelsen framed it as open source security having always relied on people finding and fixing problems, now that AI attackers exploit that same transparency instead. Reaction in the developer community was mixed, with some security researchers questioning whether closing the source actually reduces risk or just removes visibility into it.

What survived is Cal.diy, a community-maintained fork under the MIT license, essentially the repository Cal.com used to publish, frozen close to where it stood before the split. Cal.com's own account describes the production codebase as having significantly diverged since, including rewrites of core systems like authentication that never made it into the open fork. Cal.diy's own repository is direct about what that means: it's "strictly recommended for personal, non-production use," requires "advanced knowledge of server administration, database management, and securing sensitive data," and is missing Organizations and Teams management, Routing Forms, Workflows, Instant Booking, SAML and SSO, analytics dashboards, and admin tools, in short, most of what makes Cal.com useful for a team rather than one person's own calendar.

None of this changes Cal.com's hosted pricing, covered below. What it changes is the answer to "can we self-host Cal.com for compliance reasons," once a straightforward yes, now a trade-off: a hosted, closed-source SaaS relationship like the other two tools here, or Cal.diy yourself, an older fork missing the team features, with your own engineers carrying the maintenance load the vendor used to share.

Decision by Business Goal

Feature lists answer "what can it do." This section answers a narrower question: given what you're actually trying to accomplish, which of these three gets you there fastest.

Team and Role Fit

The same tool can be a strong pick for one team and a wasted subscription for the next. If routing speed matters more than the booking link itself, our lead response time guide covers why assigning a prospect to the right person quickly compounds into real pipeline impact, exactly the gap between Cal.com's Routing Forms and the other two tools here.

For teams whose real problem is qualification and routing before the meeting books, rather than the link itself, the OnceHub alternatives roundup covers Cal.com's Routing Forms against dedicated routing-first tools in more depth than fits here.

Pricing at 5, 25, and 100 Users

These three don't just charge different amounts, they charge for different units. Cal.com and YouCanBookMe both bill per person on a team plan; Microsoft Bookings never bills for itself, it inherits whatever your organization already pays per Microsoft 365 seat. That makes a straight comparison misleading unless framed carefully, so here's the honest version.

The tier each price is drawn from

Cal.com's free tier is genuinely free, unlimited event types, unlimited calendars, 100-plus integrations, but capped at exactly one user; the moment a second person needs to share availability or show up in a round-robin, that's Teams pricing. YouCanBookMe's free tier is similarly thin for a team: one calendar, one booking page, enough for a true solo operator and nothing past that. Microsoft Bookings has no separate free tier, because it was never sold separately to have one. For how these thin free tiers compare against a payments-first tool, see the Acuity Scheduling alternatives roundup; for a genuinely free multi-user option below any of these three, see the Setmore alternatives roundup.

Which Microsoft 365 plans actually include Bookings

Annual cost at 5, 25, and 100 people

Read the Microsoft column carefully: that's the cost of buying Business Basic from scratch, seat by seat, purely for Bookings. If your organization already holds a Bookings-eligible Microsoft 365 seat for everyone on this list, the real incremental cost is $0 at every row. That's the entire Microsoft Bookings pitch, and it's genuinely true, for people who already own the seat.

Where it stops being true is just as specific. Microsoft 365 Apps for business, at $10.00 per user per month, doesn't include Bookings, since that plan is desktop Office apps only: no Exchange email, no Teams meetings, no cloud collaboration layer. That's a real trap worth flagging: a business on Apps for business might assume adding Bookings costs more, when moving the same seat to Business Basic is actually cheaper per user, $7.00 versus $10.00 monthly billed annually, because the two plans serve different jobs rather than stack as a simple ladder. And if your organization has no Microsoft 365 subscription at all, "free" becomes "buy Business Basic first," the $420 to $8,400 range above, before anyone books a single meeting.

Billed month to month, no annual commitment

Cal.com doesn't publish a flat month-to-month rate next to its annual figures; the $12 and $28 per-user numbers carry a 25% savings badge against monthly billing, but the underlying monthly price isn't shown, so budget on the annual number unless you contact sales. YouCanBookMe and Microsoft both publish both numbers cleanly.

One more figure worth having before committing to Cal.com at 100 seats: Teams doesn't include SSO, SCIM, or the SOC 2, HIPAA, and ISO 27001 claims on the Organizations tier, at $28 per user per month billed annually, $33,600 a year at 100 seats, more than double the Teams number above. If a security review is part of your buying process at that headcount, price Organizations, not Teams.

None of these three flips rank as headcount grows: Microsoft's buy-in price stays cheapest, Cal.com stays in the middle, YouCanBookMe stays priciest, at 5 seats and at 100. What changes is how much that ordering costs you for guessing wrong: the gap between cheapest and priciest is about $550 a year at 5 people, and just over $11,000 a year at 100, on annual billing. Pick on capability fit first at small scale, since the price gap barely matters yet; pick deliberately once you're pricing 100 seats, since the wrong fit stops being a rounding error.

Implementation and Change Management

Setup effort tracks closely with how each product is sold. A per-seat SaaS signup is fast by design. A feature buried inside a much bigger platform depends on whether the platform is already properly licensed.

Cal.com and YouCanBookMe both get a single user to a working booking link within minutes on their free tiers. Real setup work shows up once a team gets involved: Cal.com's Routing Forms need someone to design the conditional logic and standardize event types across reps, and YouCanBookMe's branding and workflow depth take real time to configure well, confirmation messages, conditional intake questions, no-show rules. Microsoft Bookings' setup work happens earlier and elsewhere: IT has to confirm the right people hold Bookings-eligible licenses before anyone opens the app, a licensing exercise more than a product one.

Risk and Governance

Governance questions split along the same lines as everything else here: who holds the code, who publishes a compliance story, and who controls where the data physically sits.

Cal.com's Organizations tier is the only one of the three that names specific compliance certifications on its own pricing page (SOC 2, HIPAA, ISO 27001), real value for a buyer who needs paperwork for a security team. Cal.diy hands data control back to you completely, and the security responsibility along with it; its own maintainers don't claim it's hardened for that job.

YouCanBookMe doesn't surface an equivalent compliance list on its own pricing or marketing pages, which means that conversation likely happens directly with their team rather than pointing a buyer at a public certifications page the way Cal.com's Organizations tier or Microsoft can.

Microsoft Bookings inherits Microsoft 365's much larger, already-audited compliance portfolio, the same one that already covers Exchange and Teams. That's a genuine strength for a regulated buyer, with no separate security review needed for the booking piece specifically, since it isn't its own vendor relationship.

Vendor lock-in runs in the opposite direction from what "open source" might suggest. Cal.com carries an imperfect exit hatch in Cal.diy, imperfect because it lacks the team features you'd actually use. YouCanBookMe carries no self-host exit at all, standard SaaS lock-in. Microsoft Bookings is hardest to unwind, precisely because it isn't its own subscription: leaving means renegotiating your whole Microsoft 365 relationship, not canceling a scheduling tool.

When Cal.com Is the Right Call

• The deepest team-scheduling logic of the three (Routing Forms, shared availability, round-robin) at the lowest per-seat price, if a normal closed-source SaaS relationship doesn't bother you.
• You're a solo user or a true one-person team and want unlimited event types and calendars without a card on file.
• You want an open API to embed booking into your own product, even with the core repository now private.
• You have engineers who can own Cal.diy's security and maintenance for a personal or internal, non-production use, not a client-facing team flow.

When YouCanBookMe Is the Right Call

• The booking page has to look and feel like your brand, not a template with a logo dropped in, down to the confirmation email and intake questions.
• You run a coaching, consulting, or agency practice that wants ad-pixel tracking and a HubSpot handoff without adding a separate tool.
• Routing, packages, and deposits aren't the job. You just need the cleanest, most configurable single booking page.
• Paying the highest per-seat price of the three is worth it for that focus, if your team stays small enough that the dollar gap stays manageable.

When Microsoft Bookings Is the Right Call

• Your organization already holds Bookings-eligible Microsoft 365 seats (Business Basic, Standard, Premium, or an eligible Enterprise plan) for the people who need to take bookings, so the incremental cost is genuinely zero.
• IT and procurement would rather avoid a new vendor entirely than save money on a scheduling line item.
• Staff already live in Outlook and Teams, so there's no new login, no new app, and close to no training.
• You don't need routing logic, packages, deposits, or a deeply branded page. Bookings doesn't offer any of those, on any Microsoft 365 tier.

Decision Framework

What to Do Next

1. Check what you already own before pricing anything else. If your organization already holds Bookings-eligible Microsoft 365 seats, price Microsoft Bookings at $0 first and make the other two justify beating free.
2. If self-hosting is the actual requirement, test Cal.diy against that requirement honestly, on its current feature set, not on what "Cal.com is open source" used to mean before April 2026.
3. Run the 5/25/100 math above against your real headcount, not the entry price you saw first, since the gap between these three widens fast past 25 people.
4. If a branded booking page is what's actually driving the search, trial YouCanBookMe's free tier against your real booking flow before price enters the conversation at all.
5. Still unsure which of these three fits, or whether the category is right at all? The buyer's guide to choosing scheduling software covers the wider field and the criteria that matter most.

One gap worth naming honestly: none of these three ties a booking to a CRM contact record on its own. A meeting gets booked, and someone has to carry that information into wherever the sales or client record actually lives. If that handoff, not license terms or branding depth, is the real problem you're solving, that's a different category of tool. Rework's booking module is built around exactly that link, a booked appointment landing on the same contact record as the rest of the relationship, sized for teams of roughly 10 to 200 people rather than a solo booking page, and quoted per organization rather than published as a per-seat rate.