U Ministry Utility
25“api.repos: "Scheduling infrastructure for absolutely everyone." README: "Cal.diy is the community-driven, fully open-source scheduling…”
source unavailable
calcom/cal.diy
Scheduling infrastructure for absolutely everyone.
Trust Score
47.5
Last full review 2026-10-05 · Trust Score decays −2 points per month without a fresh review (never below 20)
U Ministry Utility
25“api.repos: "Scheduling infrastructure for absolutely everyone." README: "Cal.diy is the community-driven, fully open-source scheduling…”
source unavailable
M Maturity
75“api.releases: "latest tag v6.2.0 published 2026-03-01"; latest_commit dated 2026-09-20; api.repos pushed_at 2026-09-26; three contributors…”
source unavailable
47.5 → 47.5 (+0.0 over window)
ranked #5 of 21 in G4 (▼1 vs previous snapshot)
calcom/cal.diy looks like a candidate for web applications (self-hostable); U=25: no ministry features; pure general-purpose scheduling — a church could run it for appointments but nothing is ministry-modeled.
Use it with
Selected: Gloo AI Studio
Tool names and logos belong to their owners; shown so you can pick your own client. Not affiliated.
Step 1 — Connect Refinry once (prompt only)
Gloo AI Studio does not document external MCP server setup. Use this prompt with the copied Refinry research brief in Studio.
https://studio.ai.gloo.com/I am choosing open-source software for my ministry using Refinry, a review site. Read Refinry’s plain-language agent feed — https://refinry.dev/docs.md — then help me evaluate calcom/cal.diy: summarize the Trust Score, the strongest and weakest dimensions, and any caution flags it cites. Give me one small first step I can complete this week, and tell me honestly if this looks like more than I can handle.
Some clients need manual setup. Follow the plain-language steps on the Docs page.
Step 2 — Plan your first step
Tell the AI what you want to do; edit this to match your situation.
I am choosing open-source software for my ministry using Refinry, a review site. Read Refinry’s public review of calcom/cal.diy (https://refinry.dev) and help me assess it for using calcom/cal.diy for web applications (self-hostable) in my ministry. Summarize the Trust Score, the strongest and weakest dimensions, and any caution flags it cites, separating reviewed evidence from what still needs verification. Give me one small first step I can complete this week, and tell me honestly if this looks like more than I can handle.
Prefer a hand-off that works without a connection? Copy the research brief: every reviewed fact, all caution flags, and a feasibility-only first assignment.
S Security / License
50license 75 · security 50
“api.repos license.spdx_id: "MIT"; README badge: "license-MIT" (no dep-license scan evidence quoted). Security: security.md "present: true"…”
source unavailable
A Ease of Adoption
25dev 50 · volunteer 25
“README: "Self-hosting requires advanced knowledge of server administration, database management, and securing sensitive data. Proceed only…”
source unavailable
C Community Trust
75“api.repos: 48867 stars, 15278 forks, ~1457 open issues; Docker pulls badge in README; multiple high-contribution maintainers answering via…”
source unavailable
I AI-Agent Integrability
50“README excerpt: accurate project description, MIT license badge ("license-MIT"), links to CONTRIBUTING.md and issues, consistent layout…”
source unavailable