Can Calendly be vibe coded?
Scheduling links for booking meetings without back-and-forth email
A single-user booking page is easy; production-grade scheduling needs OAuth, availability rules, time zones, reminders, payments, team routing, and trust.
Jump to the build brief ↓Layer-reviewed assessment
Checked Jul 2026
What you pay today, before any DIY hosting
high editorial confidence
Tracked separately from the pricing check
Buildability by layer
Event pages, availability forms, confirmation states, and admin controls are familiar interface work.
Single-host availability and booking preserve the core scheduling job.
Calendar availability is accessible through provider APIs with the user's authorisation.
OAuth refresh, time zones, reminders, conflict prevention, and provider outages require dependable operation.
Scheduling is manageable when availability is least-privilege and double booking has a recovery path.
The achievable core
- Connect calendar, publish event-type pages, let guests choose available slots, create calendar events, and send reminders.
- Model availability, accept bookings, handle time zones, and send confirmations.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- polished Google/Outlook OAuth kept working for you
- team round-robin and routing
- SMS reminders
- the integrations directory
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
Build, switch, or keep paying
Narrower, with trade-offs
Connect calendar, publish event-type pages, let guests choose available slots, create calendar events, and send reminders.
Use the build brief ↓3 checked options
- Cal.com Free ↗Unlimited solo event types, calendars and bookings, with payments and notifications; team routing costs money.
- Google Calendar appointment schedules ↗One bare appointment page inside the calendar you already use; reminders, payments and polish are paid.
- Koalendar Free ↗Unlimited booking pages and two calendar connections; payments, forms, reminders and team routing are paid.
$12/mo
They pay because double-booking or missed meeting invites is costly.
Visit Calendly ↗Why people still pay
They pay because double-booking or missed meeting invites is costly.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Calendly
Context
Calendly — Scheduling links for booking meetings without back-and-forth email. It currently costs $12/mo.
A single-user booking page is easy; production-grade scheduling needs OAuth, availability rules, time zones, reminders, payments, team routing, and trust.
This brief describes a focused, single-operator replacement for the part of Calendly that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Connect calendar, publish event-type pages, let guests choose available slots, create calendar events, and send reminders.
Model availability, accept bookings, handle time zones, and send confirmations.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Hosted app.
Email notifications.
Timezone handling.
Auth.
Data and integrations
Google/Microsoft calendar OAuth.
Each of these needs a real account, credential, or quota. Set them up before writing feature code.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build me a personal booking page like Calendly. Requirements:
A public /book page showing my available slots for the next 14 days; visitors
pick one, enter name + email + note, and get a confirmation page.
Availability = weekly rules in a config file (e.g. Mon–Fri 10:00–17:00,
30-min slots, 15-min buffer between meetings, my timezone) minus existing
bookings, rendered in the visitor's local timezone.
Google Calendar sync via OAuth (credentials in .env): busy events block slots,
and confirmed bookings are created in my calendar with the visitor invited and
a Google Meet link attached. Warn me in the README: this OAuth app setup is
the fiddly part · the Google Cloud console is the worst of it.
Email confirmations to both sides via SMTP creds in .env.
Cancel/reschedule links with a signed token in the email.
SQLite storage, one Node process, no accounts, no framework lock-in.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
Polished Google/Outlook OAuth kept working for you.
Team round-robin and routing.
SMS reminders.
The integrations directory.
What you still own after launch
Secure credentials, rotate secrets, and handle provider rate limits.
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Maintain every third-party integration as APIs and OAuth rules change.
Risk
Operational risk. The code is achievable; dependable data, integrations, and ongoing operations are the real cost.
Editorial confidence in this assessment: high. No reviewed project implementation is linked yet.
Existing alternatives
Before building, compare these checked options:
Cal.com Free — Unlimited solo event types, calendars and bookings, with payments and notifications; team routing costs money
Google Calendar appointment schedules — One bare appointment page inside the calendar you already use; reminders, payments and polish are paid
Koalendar Free — Unlimited booking pages and two calendar connections; payments, forms, reminders and team routing are paid
Prior art
Working open-source software you can read, fork, or borrow from before starting:
cal.com — open-source Calendly — self-host and skip the OAuth pain
Generated by Can It Be Vibe Coded? · Full report: https://www.canitbevibecoded.com/calendly
You still own the product
- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.
Projects built from this idea
No reviewed implementation has been linked for Calendly yet. A submission is evidence for review, not automatic proof that the whole product was replaced.
Built a version of Calendly?Submit the project as evidence for this report.
Open-source prior art
Before you start
Can Calendly be vibe coded?
Partly, if you narrow it. A single-user booking page is easy; production-grade scheduling needs OAuth, availability rules, time zones, reminders, payments, team routing, and trust.
What can an AI coding agent reproduce from Calendly?
Connect calendar, publish event-type pages, let guests choose available slots, create calendar events, and send reminders. Model availability, accept bookings, handle time zones, and send confirmations. A responsive interface with real empty, loading, success, and error states.
What will a DIY Calendly replacement still be missing?
polished Google/Outlook OAuth kept working for you; team round-robin and routing; SMS reminders; the integrations directory; Connectors, OAuth flows, and vendor API changes require constant upkeep.; The last 20 percent is sync, migration fidelity, speed, and edge cases.
What do I still own after building a Calendly alternative?
Secure credentials, rotate secrets, and handle provider rate limits. Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss. Maintain every third-party integration as APIs and OAuth rules change.