Rooms + events
A hotel that hosts events has two things that constantly collide: people sleeping upstairs and people partying downstairs. Every other stack keeps them in separate systems and leaves the collision to the front desk. Here it's a query.
Conflict detection
This is the feature that made us build one platform instead of bolting ticketing onto a PMS. It only works because bookings and events are rows in the same database.
Gated booking periods
Festival weekends, buy-outs, member retreats: the dates are on the calendar, the rooms are bookable, and only the people with the code can book them.
Rates & rules
Every price on a booking is a snapshot taken at the moment of booking. Change a rate tomorrow and yesterday's guests still owe what they agreed to.
The booking flow
The same booking flow serves your website and the embeddable widget. There's one codebase for it, so there's one behaviour.
Guest self-service
Everything the guest can do themselves is something the front desk doesn't have to.
Operations
The watchdog exists because a broken payment form at 2 a.m. costs a weekend of bookings. It runs every hour and tells you the moment completion rates fall off.
Keep exploring
Tell us about your hotel or venue and we'll walk you through it on a call — or sign up and start exploring. It's free to set up.