GudCalGudCal

Changelog

What we have shipped recently on hosted GudCal. Newest first.

See the roadmapGet Started Free

  1. Plan limits, trial CTAs, and hosted MCP on Team

    Shipped

    • Free-plan trial on the dashboard

      Usage nudges after onboarding, a 7-day Pro trial CTA at plan limits, and public pricing that starts a trial instead of a vague upgrade.

    • Event-type cap email and API paywall

      Free and Pro hosts get a trial email when they create the last allowed event type. REST event-type creates return 402 at the same cap so API keys cannot bypass it.

    • Hosted MCP requires Team

      Authenticated MCP tools on gudcal.com require Team. Public guest tools stay public. Self-host is unchanged.

  2. Guest timezone picker and civil-date booking

    Shipped

    • Guests can change timezone on the booking page

      A compact timezone select updates availability. Day buckets and MCP get_availability ranges follow the guest IANA zone, not the host's.

    • Date-picker labels no longer roll back a day

      YYYY-MM-DD is treated as a civil date instead of UTC midnight, so a Los Angeles guest no longer sees September 15 when they picked the 16th.

  3. Multi-schedules, honest license, and calendar invites

    Shipped

    • Multiple availability schedules on Pro

      Free stays on one schedule. Pro and Team can create named schedules and assign them per event type. Booking slots honor the linked schedule.

    • BSL 1.1 wording across the site

      Marketing and docs now match LICENSE.md: source-available under Business Source License 1.1, not GPL or MIT. Self-host for your org is allowed; a competing hosted Calendly is not.

    • Plan limits actually enforced

      Event-type and calendar-connection caps apply in the dashboard and OAuth connect. Organizations require Team. MCP is no longer advertised as free.

    • Calendar invites no longer arrive as an unknown sender

      Google and Outlook no longer email guests as the host's personal inbox. Confirmation mail goes out as the host via GudCal, with a named ICS attached.

  4. Booking integrity and fail-closed freebusy

    Shipped

    • Connection-aware freebusy

      If a Google or Outlook calendar is connected and busy times cannot be verified, writes fail closed with 503 instead of double-booking. Hosts with no calendar still book against their availability rules.

    • Safer booking handoff

      After a guest books, they land on the booking confirmation page. Availability responses include host and guest timezones instead of a hardcoded zone.

Want the next thing?

GudCal is source-available (BSL 1.1). The roadmap shows what is in progress; GitHub is where requests land.

RoadmapStar on GitHub