White-label customization removes a provider’s logo, colors, and name so another organization can present the underlying product as its own. section 5.4
Cal.com’s trade
Cal.com supports white-label branding through a hideBranding switch, an embeds package, and third-party login infrastructure. A healthcare startup or recruiting firm can embed its scheduling engine inside its own product. Cal.com gives up branded viral growth, but embedding creates switching costs across login, styling, and user flows. section 5.4
Distinguish white-label customization from neighboring product choices:
- White-label removes the provider’s visible identity; API-first access controls the product through code; embedding places it inside another user experience. section 5.4
- The strategy exchanges provider-side brand exposure for customer integration and potentially costly replacement. section 5.4
|
Product
|
Open Source
|
White-Label
|
API-First
|
Consumer
Brand
|
|
Cal.com
|
Yes — full
codebase on GitHub, runnable with Docker.
|
Yes — hideBranding switch and
a packages/embeds/
folder.
|
Yes —
developer API plus an embedding SDK.
|
No — no
"Powered by Cal.com" footer anywhere.
|
|
Calendly
|
No —
proprietary, closed-source.
|
No — every
booking page shows the Calendly logo.
|
No — small
API, mostly for one-way integrations.
|
Yes — the
"Powered by Calendly" footer is the main marketing channel.
|
|
SavvyCal
|
No — proprietary,
closed-source.
|
No — no way
to hide the SavvyCal brand.
|
Yes —
developer API plus webhooks.
|
Yes — sells
a nicer booking page than Calendly.
|
|
Acuity
|
No —
proprietary, owned by Squarespace.
|
No — no
white-label option.
|
Yes — small
API, mainly for payment and email tools.
|
Yes —
markets to salons, coaches, and tutors.
|
Compare white-label availability with open-source status, API-first design, and consumer branding across scheduling products. section 5.4
