Cal.diy

Run scheduling infrastructure without a commercial license key or Cal.com account

The README describes Cal.diy as a Cal.com fork with enterprise/commercial code removed, intended for self-hosters who want a community edition without a license key or commercial dependency.

Sources: [2]

Use a Next.js, tRPC, Prisma, and PostgreSQL web stack with optional integrations

The documented stack includes Next.js, tRPC, React, Tailwind CSS, Prisma, and Daily.co, with PostgreSQL as a prerequisite. Additional credentials are needed for integrations such as calendars or external services.

Sources: [2]

For individual self-hosters and evaluation environments that want direct control over scheduling data and code

It fits users who prefer an inspectable MIT codebase on their own infrastructure and are willing to operate the database, integrations, upgrades, and security themselves.

The project explicitly recommends personal, non-production use

The README warning says Cal.diy is intended for personal, non-production use and that production self-hosting requires advanced server, database, and sensitive-data security knowledge. Commercial and enterprise-ready use is directed to Cal.com.

Teams, Organizations, Insights, Workflows, SSO/SAML, and other enterprise-only features have been removed, so feature parity with Cal.com should not be assumed.

Sources: [2]