Can Acuity Scheduling be vibe coded?
Client booking, intake forms, payments, reminders, and classes
The visible appointment scheduling loop is buildable, but a credible replacement needs more than the first screen. Acuity Scheduling earns its keep through OAuth, calendar reliability, so expect a substantial build and a narrower personal scope.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
medium editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Build a personal appointment scheduling tool that reads one calendar, publishes availability, reserves a slot, and writes the event back.
- 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
- race-free booking under load
- team routing and round robin
- reliable reminders and timezone edge cases
- calendar-provider edge cases and timezone correctness
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
Why people still pay
Acuity Scheduling: People pay because a booking tool must never double-book them, leak private events, or send the wrong time to a client.
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 Acuity Scheduling
Context
**Acuity Scheduling** — Client booking, intake forms, payments, reminders, and classes. It currently costs $20/mo.
The visible appointment scheduling loop is buildable, but a credible replacement needs more than the first screen. Acuity Scheduling earns its keep through OAuth, calendar reliability, so expect a substantial build and a narrower personal scope.
This brief describes a focused, single-operator replacement for the part of Acuity Scheduling 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
Build a personal appointment scheduling tool that reads one calendar, publishes availability, reserves a slot, and writes the event back.
Model availability, accept bookings, handle time zones, and send confirmations.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Hosted callback URL.
Data and integrations
Google Calendar OAuth credentials.
Email provider API key in.env.
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 a deliberately narrow personal substitute for Acuity Scheduling, not a full clone.
Use exactly this stack: Next.js 15 + TypeScript + SQLite.
Primary job: Build a personal appointment scheduling tool that reads one calendar, publishes availability, reserves a slot, and writes the event back.
Start from an empty folder and create the complete working project.
Make the default mode single-user and private.
Store user data locally unless the core job requires the declared self-hosted database.
Do not add analytics, telemetry, ads, or third-party accounts.
Put every secret and external credential in .env and provide .env.example.
Use realistic sample data that is clearly labelled and easy to delete.
Implement the smallest polished interface that completes the core loop end to end.
Include clear empty, loading, validation, success, and failure states.
Add import and export so the user is not trapped in the app.
Use accessible keyboard navigation, labels, focus states, and sensible contrast.
Validate untrusted input and never log secrets or private file contents.
Deliberately exclude these paid-product advantages: race-free booking under load; team routing and round robin; reliable reminders and timezone edge cases.
Do not fake integrations, network effects, proprietary data, model quality, compliance, or security claims.
Where an external API is optional, keep the app useful without it and explain the degraded mode.
Write focused unit tests for the data model and the most important workflow.
Add one end-to-end smoke test that proves the core loop works.
Create a README with setup, permissions, architecture, data location, backup, and limitations.
Add scripts for install, development, test, build, and a production-style local run.
Run the tests and build before finishing, then fix errors rather than merely describing them.
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:
Race-free booking under load.
Team routing and round robin.
Reliable reminders and timezone edge cases.
Calendar-provider edge cases and timezone correctness.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
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: medium. No independent one-shot implementation is linked yet.
Prior art
Working open-source software you can read, fork, or borrow from before starting:
[Cal.com](https://github.com/calcom/cal.diy) — Mature open-source scheduling platform and OAuth reference
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/acuity-scheduling
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.
Open-source prior art
Before you start
Can Acuity Scheduling be vibe coded?
Partly, if you narrow it. The visible appointment scheduling loop is buildable, but a credible replacement needs more than the first screen. Acuity Scheduling earns its keep through OAuth, calendar reliability, so expect a substantial build and a narrower personal scope.
What can an AI coding agent reproduce from Acuity Scheduling?
Build a personal appointment scheduling tool that reads one calendar, publishes availability, reserves a slot, and writes the event back. 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 Acuity Scheduling replacement still be missing?
race-free booking under load; team routing and round robin; reliable reminders and timezone edge cases; calendar-provider edge cases and timezone correctness; 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 Acuity Scheduling 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.