Explore here
- Web app
- Products to sell
Build a booking system that fits your availability rules
Off-the-shelf scheduling breaks on the rule that makes your business yours: the two-hour buffer, the room that can take six people but only four on Saturdays, the deposit before a slot is held. So the booking runs by message, and somebody keeps the real calendar in their head. A booking system is availability rules, a customer-facing flow, a confirmation and an owner view — Vibely builds those from a description, on a real database, deployed to a URL you can put on your own domain.
- Platform
- Web app
- Category
- Products to sell
- Stack
- React, TypeScript, Supabase
- Plans
- Free to start; database and sign-in from Lite
Availability rules enforced in the database, not in a spreadsheet
Included in the first build
Separate customer and owner views behind one sign-in
Yours to keep
- Stripe available as a shipped connector when you want deposits
- Deploys to a live URL — nothing for your team to install
- Custom domain support when you are ready to launch it
- React and TypeScript you own, synced to GitHub on Lite, Pro and Business
1. Who this is for
For studios, clinics, tutors, classes, rentals and service businesses whose scheduling has one rule the tools do not support. If a generic scheduling link genuinely fits your business, use one — this is for the case where it does not.
2. Start with this prompt
Paste it in and edit the details to match your own. Being specific about the screens and the data is what separates a working app from a mockup.
Build a booking system for a two-room pottery studio. Customer side: pick a class, see the open slots for the next four weeks, and book with a name, email and phone. Only show slots that are genuinely free. Rules: classes run Tuesday to Saturday, 10:00 to 18:00, in two-hour slots with a thirty-minute buffer between them. Each room takes six people. No bookings on Sundays or Mondays. Owner side: a sign-in, a day view and a week view of who is booked, and a way to block out a date. Data in Supabase. Seed a couple of weeks of bookings so both views look real.
3. What the build actually consists of
Your rules, as rules
Opening hours, slot length, buffers, capacity per slot and blackout dates as data the app enforces, so a double booking is impossible rather than merely discouraged.
Two views of the same calendar
A customer flow that shows only genuinely open slots and takes the booking, and an owner view that shows the day, the week and who is coming — with sign-in separating the two.
Live on a real URL
Deployed on the first build, with GitHub sync and a custom domain when you move to a paid plan. Add Stripe when you want a deposit to hold the slot.
Built on:The Supabase backendOne-click publishingCode you ownPayments with StripeCustom domains
4. What you get
- A customer booking flow that only ever offers open slots
- Availability, buffers and capacity as rules you can change by asking
- An owner calendar for the day and the week
- Confirmation screens, and confirmation emails when you add a mail provider
- A live URL, ready for a custom domain on Lite and up
5. What to build next
Once the first build lands, these are the prompts people send next.
- Add a Stripe deposit that has to be paid before the slot is held.
- Add a cancellation link in the confirmation, with a 24-hour cutoff.
- Add a waitlist for full slots that promotes the first person on a cancellation.
Works with the tools you already use
115 built-in connectors, from Vibely AI, Supabase, Stripe and GitHub to Slack, HubSpot, Shopify and Snowflake. Anything else is an API call in code you own.
Questions, answered.
Describe it. Watch it build.
Paste the prompt above and react to something running instead of writing a spec. The free plan needs no card, and the code is yours from the first build.