Bookerva
A booking-and-payments platform for Caribbean service businesses: a public booking page customers pay on, a staff calendar, and per-service deposits through Inkress to cut no-shows.
- Book → paid
- one shared link, no app to download
- Deposits per service
- off, optional or required at booking
- No double-books
- conflicts enforced in the data model
The problem
A salon, clinic or auto shop taking bookings by phone and DM loses hours to back-and-forth and money to no-shows and double-bookings. And the global booking tools that could help don't take card payments where these businesses live. Bookerva closes the whole loop for Caribbean service businesses: customers book themselves on a public page, pay up front through Inkress, and the calendar runs the day.
What it does
Each business gets a shareable booking link (bookerva.com/book/your-name, dropped in a bio, a WhatsApp status or a QR code) where a customer picks a service, picks a time and pays, with no app to download. Staff see the day in month, week, day and agenda views, and the whole appointment lifecycle is handled: confirm, reschedule, cancel, complete, no-show, with waitlists and blocked-off slots.
Payment is the difference-maker: a business can require a deposit, a partial payment or the full charge per service at booking time, collected through Inkress and settled to the business's bank. Around that sit bundles that sell several services as one booking, intake forms, automated confirmations and SMS reminders, virtual appointments that create their own Google Meet or Zoom links, and a healthcare setting that treats patient details as protected health information, encrypted and audited. It ships templates for the trades it serves: salons and beauty, healthcare, fitness, education, home services, automotive and pet care, among others.
Key features
Customers book themselves
A share-anywhere booking link takes a customer from service to time to paid in a few taps, so the calendar stops living in phone calls and DMs.
Deposits before the chair is filled
Per-service payment rules (off, optional or required) collect money at booking time through Inkress, which is what actually cuts no-shows.
Double-booking, prevented for real
Conflict detection, waitlists and blocked slots are enforced in the data model, so two customers can't land in the same slot. The core promise of a booking tool, actually kept.
Bundles sold as one booking
Two or more services chain into a single bookable package at the spacing the business sets, so a 'spa day' is one click for the customer and packs cleanly on the schedule.
Virtual appointments, native
A virtual service creates its own Google Meet or Zoom link and carries it on the confirmation, the calendar entry and the reminder: no copy-pasting links around.
A real team on one diary
Owner, manager, staff and provider roles with per-provider calendars, working hours and services fit how a multi-staff, multi-location business actually runs.
Where it stands
Relaunched in 2026 as a ground-up rebuild of the original Remix-over-Phoenix version. Card acceptance runs on Inkress, so it reaches the markets Inkress serves.
Under the hood: for the technically-minded
How it's built
The relaunched Bookerva is a ground-up rebuild: a Remix app over Postgres with Drizzle and Redis, structured as a small kernel with the product built as plugins on sixteen typed extension points: appointments, public booking, payments, notifications, calendars, intake forms and tenancy each live behind their own seam. Multi-tenancy is enforced at the data layer with row-level security, background jobs send the reminders and follow-ups, and an event bus records what happened as persisted, replayable facts.
Payments are an Inkress plugin rather than a hard-wired dependency: the platform that already moves money for Caribbean merchants handles cards, deposits and settlement. Bookerva also runs as an embedded app inside Inkress itself, so a merchant there gets a booking book without leaving their dashboard.
The hard problems
Conflict-proofing the calendar
The whole value of a booking tool is that it never double-books, so conflicts, waitlists and blocked slots are enforced per tenant at the schema level: the promise is kept by the data model, not just checked in the UI.
A kernel-and-plugins rebuild
The first Bookerva grafted appointments onto a fork of Inkress's commerce backend; the relaunch inverts that into a small kernel with sixteen typed extension points and the features (payments included) as plugins, so each capability can evolve or be swapped without surgery on the core.
Chaining bundles onto a live diary
Selling several services as one booking means the pieces must land on the calendar together, in order, at the spacing the business sets: a packing problem the scheduler solves at booking time rather than leaving staff to arrange it by hand.
Built with
- Remix
- Drizzle
- Postgres
- Redis
- Inkress payments
Building something in this space?
Work with us →