Productivity / released

WHEN.

Self-hosted scheduling with public booking pages and availability rules.

A new take on the workflow.

The README describes a v1.0 scheduling MVP for solo operators. It documents time-zone-aware booking, event types and Google Calendar integration. Evaluate scheduling edge cases before moving real bookings.

What you can switch today.

Replace a solo Calendly-style booking page with your own event types, availability rules and calendar-connected scheduling.

Set up WHEN, Supabase and the documented Google OAuth integration.
Recreate a noncritical event type and availability schedule; configure confirmation email if needed.
Test a complete booking, cancellation and conflicting calendar slot across your relevant time zones before sharing the new booking URL.

Switching caveat. A self-hosted scheduling MVP, not managed Calendly infrastructure. Existing Calendly links/bookings are not automatically migrated; scheduling edge cases are not independently tested. Workflow evidence

Where it falls short.

Requires your own Supabase configuration; calendar sync and email require Google OAuth and Resend credentials. Feature claims have not been runtime-tested.

Documented capabilities.

Listed in project documentation; not independently functionally tested by VibeAlt.

Public booking pagesSource
Availability rulesSource
Google Calendar syncSource

Maker claims AI build. The README explicitly says WHEN was scaffolded with Claude Code; this is a maker statement, not an independently measured AI-written percentage. Inspect the evidence

Original build attribution.

The maker describes AI-assisted development of this project. This is a first-party claim, separate from any code contribution evidence. Read the original attribution

What it can stand in for.

Calendly alternatives

Scheduling reliability depends on time zones, calendar conflicts, availability rules and cancellation flows. Test daylight-saving transitions and duplicate bookings before sharing a new booking link.

Open the comparison

Sources & freshness.

Source review: 2026-10-29. First added: 2026-10-28. Repository metrics are fetched separately through the GitHub API. Last metrics retrieval: Not fetched.

Report a correction