calcom/cal.com

Choose this fork if branding, redirect behavior, and customized scheduling UX matter more than staying close to upstream. Choose upstream if you want the broadest feature coverage, fastest access to fixes, and lower merge risk.

Choose this fork if your priority is privacy-preserving scheduling and you are prepared to maintain a large divergence. Choose upstream if you want the broadest feature coverage, freshest fixes, and lower maintenance burden.

Choose this fork only if you need its specific older customizations and are prepared to maintain a large divergence yourself. For most adopters, upstream Cal.com is the safer and lower-cost choice.

Prefer this fork only if its custom API/platform/email-domain behavior is specifically what you need and you are willing to own a large, stale codebase. If you want active upstream security, reliability, and product improvements, the main Cal.com repository is the safer choice.

Prefer upstream unless you specifically need this fork's API v2/embed/platform changes and are prepared to maintain a large, stale divergence. For most adopters, the missing upstream coverage and inactivity outweigh the fork-specific additions.

Prefer this fork only if you need its custom API/platform work or existing downstream behavior and are prepared to carry a large merge burden. If you want the latest Cal.com features, fixes, and lower maintenance cost, upstream is the safer choice.

Prefer this fork if you need the companion-extension and custom workflow changes and are willing to own a diverged codebase. Prefer upstream if you want the broadest feature set, smoother upgrades, and fewer surprises in standard scheduling flows.

Choose this fork if you want a heavily customized Cal.com base and are willing to own ongoing merge work. Choose upstream if you want faster access to recent fixes, lower maintenance burden, and less divergence.

Prefer this fork only if its added routing, permissions, and embed/API changes are the point of the fork and you can carry maintenance yourself. If you want the safest path to current scheduling functionality, upstream is the better default because this fork appears materially stale and highly divergent.