Reservo
The booking SaaS for the service businesses Booksy charges by the staff member — owned outright, deployed under your brand.
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.
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.
- Public per-business booking page (/[orgSlug], no account)
- Schedule blocks / holidays / special hours
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.
- Deposit/payment at booking (fixed $ or % per service)
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.
- Public per-business booking page (/[orgSlug], no account)
- Intake forms at booking
You receive this. It ships behind a feature flag and sits on the Growth, Pro tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the — (fork) tier as configured, so it is revenue you can reserve for your own paying customers.
Deposits are available on the paid plans. On the free plan the deposit configuration is hidden and services simply book without payment.
You receive this. It ships behind a feature flag and sits on the Growth, Pro tier as configured, so it is revenue you can reserve for your own paying customers.
The Dashboard carries the same numbers as summary cards with today's agenda underneath, for the daily glance rather than the monthly review.
You receive this. It ships behind a feature flag and sits on the — (fork) tier as configured, so it is revenue you can reserve for your own paying customers.
A customer is never reminded twice for the same thing. Three independent layers guarantee it: the queue de-duplicates on a natural id, delivered events are recorded, and the database itself refuses a second reminder row for the same appointment, stage and channel. Cancel an appointment and its pending reminders are cancelled with it.
Reminder delivery needs an email provider and a queue credential, both entered under Admin → Integrations. Until they are configured, reminders are sent inline from the scheduled run instead of through the queue — they still go out, but without the queue's retry guarantees. Scheduled runs must be wired on the host; see the deployment guide.
SMS reminders are not in this release. The phone number is collected at booking so the data is there when SMS is switched on later, but only email is delivered today.
Under Settings → Policies a business sets:
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Canny
Amplitude
Custom Head Scripts
Pushover
Twilio SMS
Crisp
Tawk.to
Monday.com
fal.ai
Axiom
hCaptcha
Pabbly Connect
Freshsales
Pipedrive
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 52 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 65 tables, as text
active_boosts · admin_notifications · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · appointment_reminders · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · audit_logs · automation_log · automation_templates · availability_rules · booking_policies · bookings · calendar_connections · credit_balances · credit_transactions · currencies · customers · data_exports · data_imports · external_calendar_blocks · faq_categories · faq_items · feature_flags · inbound_webhook_events · inbound_webhooks · languages · marketing_audience_members · marketing_audiences · notification_log · notification_rules · notifications · organization_limit_overrides · organizations · plans · platform_secrets · platform_settings · processed_events · product_purchases · products · provider_prices · push_devices · report_templates · roles · schedule_blocks · scheduled_tasks · seo_meta · services · staff_services · subscriptions · theme_page_sections · theme_section_library · theme_sections · translations · user_sessions · users · webhook_logs · webhooks
The chassis, and anything particular to this product. 2 required.
The chassis. Next 16 on any Node host, with Postgres, auth and storage coming from Supabase.
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.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
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.