Events
Concerts, talks, screenings, meetups
Concert tickets, a chef's counter, a padel court, a recording studio, a dentist's chair. The admin publishes the slots; you take them.
Every category runs on the same record — a title, a moment in time, a place, and a number of slots. That is the whole trick: a booking system stops being domain-specific the second you stop hard-coding the domain.
Concerts, talks, screenings, meetups
Tables, tastings, chef counters
Tours, transfers, excursions
Clinics, therapy, treatment rooms
Desks, studios, meeting rooms
Courts, lanes, classes, coaching
Repairs, grooming, consultations
An email and a password is all it takes. Sessions are issued server-side and carried in an HttpOnly cookie — nothing about who you are is ever taken from the client.
A single predefined administrator account creates listings — a title, a date, a location, a description, and a capacity. There is no admin signup route, by design.
Pick anything in the catalog and take a slot. A unique constraint on (guest, listing) makes double-booking impossible no matter how fast you click.
Cancelling deletes the booking outright, so the slot goes straight back into the pool and re-booking is always available.