How is Meetingpad different from Cal.com?

Cal.com is an open-source scheduling platform designed to be configurable. You set the destination calendar per event type, wire up webhooks, and host it yourself if you want. Meetingpad is opinionated: it's the calendaring workflow for people running multiple Google Workspace accounts, no configuration required. Every connected Google account is automatically a first-class identity with its own booking link, its own Gmail send address, and its own place in unified availability.

Can Cal.com do what Meetingpad does?

You can approximate it. Cal.com's free individual tier lets you connect multiple calendars and set the 'add to' calendar per event type. So with careful configuration you can route each event type to a different calendar. You still don't get per-identity booking links out of the box, native macOS workflow, or automatic titleless cross-account Busy placeholders. Meetingpad ships that as the default, not the destination of configuration work.

Is Meetingpad open-source?

No, Meetingpad is a proprietary Mac app. If open-source and self-hosting matter to you, that's what Cal.com is for. Meetingpad optimizes for people who want the multi-account calendaring workflow to just work, not for people who want to run their own scheduling infrastructure.

Meetingpad vs Cal.com: the calendaring tool for multi-Google-account operators

The one-line summary

Cal.com is an open-source scheduling platform built to be configurable, pick your destination calendar per event type, wire webhooks, host it yourself. The multi-account use case is possible if you set it up correctly.

Meetingpad is a comprehensive calendaring workflow where the multi-account case is the default. Connect a Google account. It's a first-class identity with its own link, its own Gmail send, its own working hours, and its own place in unified availability. No routing rules to write. Native Mac menubar app.

Head-to-head

	Cal.com	Meetingpad
What it is	Open-source configurable scheduling platform	Opinionated calendaring workflow for multi-Google-account operators
Multi-account setup	Per-event-type calendar routing. You configure each event type manually	Automatic, every connected account is an identity from the moment OAuth completes
Per-account Gmail send	Configurable per event type	Automatic per identity. No configuration
Cross-account Busy placeholders	Not a built-in primitive; you'd wire it via webhooks	Automatic titleless placeholders on every other connected calendar
Native Mac workflow	Web app (self-hosted or cal.com hosted)	Native macOS menubar
Open-source / self-hostable	Yes	No, proprietary Mac app
Free tier (individual)	Yes, most features on the free hosted tier	Free forever, 2 accounts
Paid tier	$15/mo Teams, $37/mo Organizations (per user)	$5/mo Pro, unlimited accounts

Verified against Cal.com's public pricing as of 2026-08-17.

Configuration tool vs opinionated tool

Cal.com's superpower is that you can make it do almost anything if you put in the configuration work. Different calendar per event type, custom webhooks on booking events, self-hosted on your own infrastructure with your own DB, all supported.

Meetingpad's superpower is that you don't have to. The correct defaults for someone running 2+ Google Workspace accounts are the defaults. Every account becomes an identity; every identity has its own booking link; every booking sends from the right Gmail; every other calendar gets a titleless placeholder. It's the tool for people who want the multi-account workflow to be the outcome, not the project.

Where Cal.com wins

If open-source and self-hosting matter to you, Cal.com is the only real answer in this category. If you want to build custom scheduling workflows on top of a platform, routing forms, custom webhooks, embedded booking inside your own product, Cal.com is the right substrate. Meetingpad is a finished workflow, not a platform.

Try it

Download Meetingpad: free plan covers 2 accounts See what it saves you