Cal.diy
Research-only community scheduling edition with a non-production warning
Review status: Research backlog. Research candidate with incomplete checks; not a vetted recommendation.
Official Website · Source Code
oss-osi-approved planned guideOverview
Cal.diy is the MIT-licensed self-hosted community edition associated with Cal.com. Its documentation describes individual appointment scheduling, but explicitly recommends personal, non-production use and advanced administration. Coworking tour scheduling is a possible research use only; it is not recommended here for a live operator booking system.
At a glance
| Field | Value |
|---|---|
| Categories | booking-scheduling |
| Deployment | self-hosted |
| License class | oss-osi-approved (MIT) |
| Cost model | free-self-hosted |
| Implementation difficulty | expert |
| Maintenance burden | high |
| Maturity | experimental |
| Freshness status | partially-verified (2026-10-23) |
| Completeness | partial |
| Confidence | medium |
| Directory tier | research-backlog |
Cost reality
MIT source has no software subscription, but servers, database operations, provider credentials, email, security and maintenance require technical work. Commercial Cal.com hosting or on-prem enterprise access is a separate offering.
Plans, provider terms and prices change; check official sources before making a budget or deployment decision.
Tasks reduced or augmented
Software does not replace community or ops staff. It may reduce or augment:
- Explore how an individual appointment link presents tour availability
- Study scheduling configuration without adopting it as an operational system
Human oversight still needed
- Respect the upstream non-production boundary when selecting operational scheduling software
- Review calendar credentials, conflicts and security in any isolated research environment
Manual process this can replace
Structured task-fit review has not been completed for this tool. Treat the free-text examples above as evaluation prompts, not replacement claims.
Data held
-
booking and attendee details
-
calendar access tokens
-
host availability
-
notification configuration
-
Personal data: yes
-
Payment data: no / not primary
Collect only data needed for the pilot and confirm access, deletion and export behavior before operational adoption.
Risks
| Area | Notes |
|---|---|
| Vendor lock-in | Export, migration and restore behavior have not been tested; retain a practical manual fallback before depending on the tool. |
| Security | Upstream does not guarantee the community edition security or safety. Do not connect production credentials or real prospect records for the first research pilot. |
| Compliance | Even test calendar access can reveal personal data; use synthetic data and test credentials. Commercial use suitability requires an explicit edition and support decision. |
| Licensing | MIT applies to the community repository, not the commercial Cal.com hosted application or enterprise offering. The old calcom/cal.com repository URL redirects here. Official documentation recommends personal, non-production use. |
| Operational | Official documentation strictly recommends personal, non-production use. Team events, round-robin and collective team scheduling are absent from its published edition comparison. No production recommendation or operational test is claimed. |
Coworking fit
Roles: technical-operator, consultant-implementer
Workflows: tour-to-close
Problems: self-host-for-data-control, reduce-manual-admin
Smallest useful experiment
Use an isolated test environment with synthetic attendees and a test calendar to inspect one sample tour event type; do not publish a live prospect booking link.
Links
Implementation guide
No implementation guide is published yet.
Verification
- Status:
partially-verified - Completeness:
partial - Confidence:
medium - Tier:
research-backlog - Last reviewed:
2026-10-23 - Sources:
Bounded official-source metadata review only. Features and edition boundaries were read; installation, task-fit evaluation, operator outcomes, integrations, security and recovery were not tested. Retained in Research Backlog; not a recommendation.