# Reservo

> The booking SaaS for the service businesses Booksy charges by the staff member — owned outright, deployed under your brand.

Source page: https://saascode.ai/products/reservo
Machine-readable record: https://saascode.ai/products/reservo.md

One-time purchase · full source code · self-hosted by the buyer.

Price: $249 (one-time)

## How to read this document

Written for a model auditing this product on a buyer's behalf. Two labels
appear throughout and they mean different things:

- **measured** — produced by a script reading the product's own source tree
  or database at the stated date. The method is named beside each number.
- **stated** — written by the seller. True or not, it is a claim, and this
  document does not ask you to treat it as evidence.

The live demo is the strongest verification available from outside: it runs
the same source a buyer receives. Nothing to sign up for — the public side is
open, and the seeded credentials below get you into each role.

## What it is

This is an online booking and appointment-management product for service businesses. Every business is its own isolated workspace with its own services, staff, calendar, customers and public booking page — nothing is shared between businesses.

## Live demo

Two doors into the same running instance, and the same source a buyer
receives. There is no account to create; the public side is open, and the
seeded credentials below sign you into each role.

- **Guided (recommended):** https://saascode.ai/demo/reservo — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://reservo.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

3 roles seeded on the demo (of the 5 the schema defines — the build data below counts them all). Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Staff member** (`member`) — `maya@northwind-demo.com` / `demo123`
  Works their own agenda and the services they perform.
- **Business owner** (`org_admin`) — `owner@northwind-demo.com` / `demo123`
  Runs the salon: services, staff, calendar, billing.
- **Platform admin** (`super_admin`) — `admin@reservo-demo.com` / `demo123`
  The backend: every business, plans and settings.

Or open a role directly: https://saascode.ai/demo/reservo?role={role}

## Measured build

*measured — each number names the method that produced it.*

- **roles: 5** — distinct roles accepted by the role CHECK constraint: admin, end_customer, member, org_admin, super_admin
- **tables: 65** — distinct CREATE TABLE statements across every applied migration
- **migrations: 116** — .sql files in supabase/migrations
- **page modules: 78** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 149,570** — lines of code (comments and blank lines excluded) across 1029 TypeScript files (133,439) and 133 SQL files (16,131); node_modules and .next excluded
- **api route files: 213** — files named route.ts under src/app/api
- **http operations: 290** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 65 tables, 103 relationships** — parsed from the applied migrations

A large number here is scope, not quality. It says the product models a
real domain rather than a CRUD skeleton; it says nothing about code
quality, duplication, test coverage or maintainability, and should not be
read as if it did.

Release: v1.0.0 · built 2026-08-01

## Complete capability inventory

10 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### The booking engine

- **Schedule blocks / holidays / special hours** *(seller-authored)* — Blocks time that is not bookable — a holiday, a half day, a staff member's afternoon off — so the public page stops offering slots nobody will honour. A booking taken for a day the business is closed costs more than the empty slot did.
- **Staff external calendar sync (iCal read-only v1)** — Staff can connect an external calendar by iCal URL under Settings → Integrations. It is read-only in this release: external events appear as busy overlays so a slot is not offered while the person is elsewhere. If the external calendar is unreachable, booking is never blocked — the schedule falls back to the business's own availability rules and the connection shows a stale indicator. Two-way sync and direct Google/Microsoft connections are not in this release.
- **Group-class capacity (max_concurrent > 1)** *(seller-authored)* — Lets one slot hold more than one customer, which is what a class, a session or a group booking is. Without it a business running classes has to model each seat as its own appointment and reconcile them by hand.

### Deposits & payments

- **Deposit/payment at booking (fixed $ or % per service)** — A service can require a deposit at booking, set either as a fixed amount or as a percentage of the service price. When the customer confirms, a one-off hosted checkout is created for that exact amount, and the appointment is only held once payment succeeds.

### Occupancy & operator area

- **Occupancy + revenue reporting** *(seller-authored)* — Answers the two questions a service business actually has: how full were we, and what did it earn. An occupancy percentage against real capacity, and revenue beside it, rather than a count of appointments that says nothing about whether the week was good.

### The public booking page

- **Public per-business booking page (/[orgSlug], no account)** — 1. The business page (/{slug}) — the service menu with name, duration and price, plus the staff picker. 2. Slot picker (/{slug}/book/{service}) — a date calendar and a time grid built from the rules described in the booking-engine section, shown in the business's timezone. 3. Confirm (/{slug}/book/confirm) — customer details, the deposit step when the service requires one, and the confirmation. 4. Their appointment (/{slug}/appointment/{token}) — a private link, emailed on confirmation, where the customer can view, reschedule or cancel under the policy the business set. No login, no password.
- **Customer records + history + no-show count** — Every public booking creates or matches a customer record for that business. Customers lists them with a no-show count; the detail page adds their full appointment history. Records belong to the business that took the booking and are never pooled across businesses.
- **Intake forms at booking** *(seller-authored)* — Collects what the business needs to know before the appointment — a reason for the visit, a preference, a required detail — at the moment of booking rather than in a phone call the day before.

### Reminders & policies

- **Automatic email reminders (24h + 1h)** — Every confirmed appointment schedules two email reminders: one 24 hours before and one 1 hour before. They are written as future-dated tasks the moment the booking is taken, so nothing depends on a person remembering to send anything.
- **Reschedule/cancel with configurable policies + forfeiture** — The policy is shown to the customer on their appointment link, and it is enforced server-side when they act on it — the rule is not merely displayed, it decides the outcome.

## What each system gives the operator

*stated.*

- **The booking engine** — Two customers can never end up holding the same slot.
- **Deposits & payments** — The deposit lands in the business's own account, not in yours.
- **Occupancy & operator area** — You can answer how full we were and what it earned.
- **The public booking page** — Customers book themselves at midnight without an account or a phone call.
- **Reminders & policies** — Fewer no-shows, without anyone making the reminder calls.

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### Two people clicking the same time at once produce one booking and one apology.

Double-booking is the failure a service business cannot absorb. Two customers arrive for the same eleven o'clock, one of them is turned away, and whatever that appointment was worth is now a refund and a review. It happens in the seconds between someone opening the booking page and confirming — a window that widens exactly when the business is busiest and can least afford the phone call that follows.

### A deposit is taken at the moment of booking and settles with the business.

No-shows are the quiet tax on a service business, and the usual defences do not work. Confirmation calls take staff time, overbooking annoys the customers who did turn up, and a cancellation policy nobody paid against is a sentence on a website. The businesses that solve it take money at booking — but then the platform holding that money inherits refunds, disputes and an obligation it never intended to sign up for.

### The page takes bookings at midnight, without an account and without you.

Most appointments are decided outside business hours, and a business reachable only by phone during the day loses every one of them to whoever answers first. The alternative most take is a form that emails a request, which is not a booking: somebody still has to read it, check the calendar, reply, and hope the customer has not gone elsewhere in the meantime. Each step is a place to lose the customer, and the busiest weeks are when the replies come slowest.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **A Node host and a Supabase project** (required) — The chassis. Next 16 on any Node host, with Postgres, auth and storage coming from Supabase.
- **A scheduled runner** (required) — Six jobs ship declared for Vercel, including the reminder sends. On another host they are a cron configuration you wire by hand — reminders are the product's defence against no-shows, and they only go out when something calls them.

## FAQ

**What exactly do I receive after purchase?**

The complete source repository behind the live demo — 149,570 lines across the application and its database, 65 tables defined by 116 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.

**Is the live demo the same product whose source I receive?**

Yes. The Reservo demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.

**Can I test every account role before buying?**

Yes — all 3 of them: Staff member, Business owner, Platform admin. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.

**Is this a complete product or a starter template?**

Complete. 78 page modules and 290 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.

**Can I rebrand and modify it?**

Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.

**What does the licence allow?**

A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.

**Can I resell the source code?**

No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.

**What services and ongoing costs are required?**

You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: A Node host and a Supabase project, A scheduled runner. Optional: none. The table above says exactly what stops working without each one; most have usable free tiers at low volume.

**How difficult is deployment?**

Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 116 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.

**What updates and support are included?**

Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.

**Why does a complete codebase cost $249?**

Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.

**Do I need to be a developer?**

No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.

## Licence

The buyer receives the complete source and may deploy, modify and operate it
as their own SaaS, charging their own customers. The source itself is not
resold or redistributed: you build and deliver **with** it, you do not sell **it**.

## What this document cannot tell you

Stated plainly because a review that misses it is not a review:

- code quality, duplication, or architectural consistency
- test coverage
- query performance under load
- security posture beyond what the stack implies
- how maintainable it will be in a year

Scope is measurable from outside; implementation quality is not. Anyone
evaluating this should say so rather than infer quality from size.

## Written about it

- [Deploying Reservo for clinics and allied-health practices](https://saascode.ai/inside/deploying-reservo-for-clinics-and-allied-health-practices.md)
- [Booking SaaS for salons, barbershops, and spas — deploying the platform Booksy charges by the hire](https://saascode.ai/inside/booking-saas-for-salons-barbershops-and-spas-deploying-the.md)
- [Booking software for service businesses — a genuine buyer's guide (2026)](https://saascode.ai/inside/booking-software-for-service-businesses-a-genuine-buyer-s.md)
- [Reservo vs Booksy, Cal.com, and the ways to acquire a booking platform](https://saascode.ai/inside/reservo-vs-booksy-cal-com-and-the-ways-to-acquire-a-booking.md)
- [Reservo: a booking platform you own and sell to service businesses](https://saascode.ai/inside/road-to-reservo.md)

## Links

- Catalog page: https://saascode.ai/products/reservo
- Product record: https://saascode.ai/inside/products/reservo
- Live demo: https://reservo.saascode.ai
- Every product: https://saascode.ai/llms.txt