Cal.com: A Self-Hosted Calendly Alternative
Calendly's Standard plan is $10/seat/month — fine for one person, real money for a team where everyone needs their own booking page. Cal.com is the same product, open source, running on the same $12/month tier as most of this stack.
Calendly's Standard plan is $10 per seat per month (annual billing). For one person that's a small line item. For a team where everyone — sales, support, whoever takes meetings — needs their own booking page, it adds up the same way every per-seat tool on this site does.
The actual numbers
| Calendly Standard | Self-hosted Cal.com | |
|---|---|---|
| 5-person team | $50.00/month (5 × $10) | $12.00/month (shared VPS) |
That's a 76% reduction, and it stays flat as you add people who need their own booking link — unlike Calendly's bill, which grows by $10 for every seat.
What it takes to run
Cal.com is the open-source scheduling tool Calendly gets compared to constantly, and for good reason — it's largely feature-equivalent: booking pages, availability rules, calendar sync, round-robin routing. Using the official prebuilt Docker image (not building from source, which has much heavier requirements), it runs comfortably on 2GB RAM — the same $12/month Vultr tier that covers most of the lighter tools on this site, not the $24/month tier I've needed for the heavier ones like Chatwoot or Rocket.Chat.
What you're taking on
- Calendar sync is now your integration to maintain. Calendly's Google/Outlook/Apple Calendar sync is polished and battle-tested. Cal.com's works, but test it thoroughly with your actual calendar setup before you rely on it for real bookings — a missed sync means a real, embarrassing double-booking.
- Email confirmations need your own SMTP setup. Same as anything else on this site that sends transactional email — booking confirmations and reminders won't send themselves without a configured mail relay.
If your team is small enough that Calendly's cost doesn't register, there's no urgency here. This is worth doing once you're paying for enough seats that the per-person fee is a real number, not a rounding error.
I run mine on the same kind of small Vultr instance as most of the rest of the stack — see the full cost roll-up for how it all fits together.
Disclosure: this post contains an affiliate link to Vultr. If you sign up through it, I may earn a commission at no extra cost to you. I only link to providers I actually use.