OpenCalendly alternative

Calendly-grade scheduling UX, fully owned by your stack.

Run scheduling on Neon + Cloudflare with modern booking flows, operational tooling, and public embeds without vendor lock-in.

10+

Feature streams shipped

40+

API routes in v1

Neon

Single supported database

OSS

Open source stack ownership

Scheduling that rechecks correctness at commit

Slot conflicts are validated at booking mutation time with transaction-safe guarantees and idempotency keys.

Organizer operations without hidden dashboards

Event types, availability, teams, webhooks, calendar sync, and writeback controls are exposed in product UI.

Public flows ready for real traffic

One-on-one booking, team booking, cancel/reschedule links, and embed scripts all route to implemented APIs.

How teams run OpenCalendly

1. Publish event types

Create one-on-one or team event types, define location mode, and control active state from organizer UI.

2. Open booking links

Share public booking pages with timezone handling, buffer-aware slot generation, and duplicate-request protection.

3. Operate at runtime

Track analytics, run webhook deliveries, sync calendars, and clear writeback failures from authenticated surfaces.

Live product routes

All links below are wired to currently implemented product functionality.

Integrations + platform

Google Calendar

OAuth connect, sync, busy-window conflict blocking, and writeback retries.

Microsoft Calendar

Provider parity with connection lifecycle, sync scheduling, and failure visibility.

Resend

Booking lifecycle emails with delivery telemetry and action-link support.

Cloudflare Workers

Low-cost API runtime with Hyperdrive bridge to Neon.

Pricing clarity before scale

Starter OSS

  • One-on-one + team booking
  • Organizer console + analytics
  • Embeds + webhook runners
See pricing model

Operator Focused

  • Calendar sync + writeback controls
  • Action links + lifecycle emails
  • Rate-limit and idempotency hardening
See feature matrix

Ready to own your scheduling stack?

Start with demos, then move into organizer workflows and analytics without changing infra.