One calendar, 5 views, and a database that won't let a room double-book
Overview, timeline, classic grid, calendar, and list — switch views without losing your place. Move a booking by dragging it, and if the move isn't allowed, the calendar explains why and what to do instead.
The 5 views
Overview
A property-wide snapshot for a quick read of what's happening across rooms.
Timeline
Rooms down the side, dates across the top — good for seeing how long each booking runs.
Classic grid
A familiar spreadsheet-style grid of rooms and dates.
Calendar
A month-by-month view organised by date.
List
Every booking as a plain list, useful for scanning or searching.
What you can do by dragging
- 1
Move a room
Drag a booking to a different room and it updates in place.
- 2
Move dates
Drag the edges of a booking to change check-in or check-out.
- 3
Swap two bookings
Drag one booking onto another to swap their rooms.
- 4
If a drop isn't allowed
The calendar explains why — for example, the room is already taken that night — and suggests what to do instead, rather than just blocking the move silently.
Beyond the calendar grid
400-day occupancy heatmap
See how full you are up to 400 days out, at a glance.
Bulk edit
Change prices or availability across many dates and rooms in one action instead of one at a time.
Early check-out, per room
Close out a single room early on a multi-room booking, with the choice to keep or refund the remaining nights.
Release room — guest no-show
Mark a no-show and put the room back on sale, with a two-step confirmation so it isn't done by accident.
Walk-ins
Enter a walk-in booking directly into the calendar.
Who-changed-what history
Every change is logged for 400 days — who did it, and what changed. No IP addresses are stored.
What the calendar guarantees
Guaranteed
- A database-level rule blocks one room from holding two guests on the same night — enforced in the database itself, not just the interface, so it can't be worked around by a bug
- Every drag-and-drop move that isn't allowed comes with an explanation and a next step
- Change history goes back 400 days without storing IP addresses
Note
- We don't make speed claims about the calendar — judge it on your own property, not a number on this page
Frequently asked questions
Can two bookings end up in the same room on the same night?
No. That rule is enforced at the database level, so it can't happen even if there's a bug elsewhere in the system.
What happens if I drag a booking somewhere it can't go?
The calendar tells you why the move isn't allowed and what you could do instead, rather than just refusing silently.
How far ahead does the occupancy heatmap show?
Up to 400 days.
Can I see who changed a booking and when?
Yes, for the last 400 days. The history doesn't store IP addresses.
Can I release a room if a guest doesn't show up?
Yes, with a two-step confirmation so it can't happen by accident, and the room goes back on sale.
Keep reading
Try the real thing before you decide
The demo opens every feature with nothing to fill in · price is calculated from your real room count, no sales call