Scheduling · v0

Scheduling infrastructure.

A booking product built on a private operations layer. Google Calendar freeBusy sync, multi-calendar selection per host, encrypted token storage, fail-closed availability, per-IP rate limiting on the public endpoint. Currently dogfooding a single host before private beta.

Join waitlist →

What it does

The actual building blocks.

Google Calendar freeBusy sync. The public booking page reads the host's Google Calendar in real time so taken slots are unbookable. The host doesn't sync, doesn't push events, doesn't maintain a separate availability calendar.
Multi-calendar selection per host. The host picks which of their Google calendars participate in availability. Personal blocks merged with work commitments without exposing event titles to the public booker.
Encrypted token storage. Refresh and access tokens stored AES-256 GCM at rest, decrypted only at the edge function. The DB row is useless without the encryption key, which lives only in the edge runtime.
Fail-closed availability. If Google's API is unreachable, the booking flow refuses to render slots and refuses to confirm a booking. No silent over-booking during an outage.
Per-IP rate limit on the public endpoint. Fixed-window rate limit keyed on the original client IP from the gateway. Abuse surface bounded.
Internal booking trail. Confirmed bookings produce a private follow-up record for the host — booker name, email, and slot recorded on the booking row, plus an auto-created task. None of this is exposed to the public booker.

Waitlist

Tell me when it's ready.

Private beta is single-tenant for now. Drop your email and I'll reach out when host slots open. No marketing list, no automation — this is just a flat table of "who wants in."

Already a host? Open the host portal → Self-serve host creation isn't open during testing; if you don't already have access, the waitlist above is the path.