Operations software for small hotels
Philoxeniais a focused workspace for boutique hotels, B&Bs, and guesthouses: a live calendar, command search, guest histories, reporting, and team access—scoped per property so everyone stays aligned.
When availability, guest details, and nightly revenue live in different tabs, mistakes creep in and your team wastes time reconciling. Philoxenia keeps the operational core—calendar, guests, metrics, configuration—in one calm product surface purpose-built for properties with a handful of rooms.
No vaporware: the bullets below map to the screens and behaviors already in the product, from drag-and-drop scheduling to prorated revenue ranges.
Real screens from the product—layout, density, and tone match what you get after sign-in.
Month calendar
Room rows, month navigation, reservation bars, and the same sidebar as the live app.
Guests & history
Search the directory, then inspect stays with dates, room, nights, and totals in one table.
Reports
Date range at the top; occupancy, revenue, ADR, RevPAR, and sold room-nights in metric tiles.
See every room row at a glance and adjust stays without spreadsheet gymnastics.
One palette for guests and availability—built for front-desk speed.
A profile per guest with the paper trail in one table.
Occupancy and revenue for any range you select—not a black box.
Everything scoped per property, with the timezone that drives “today.”
Bring a manager or front desk without sharing a single login.
One account, many small hotels—each with its own shell and data boundary.
Add Philoxenia to your home screen for a focused, app-like window.
The same path your team walks inside the app—no consultants required.
Sign up with Clerk-powered authentication. You get a personal dashboard, not a demo tenant.
Name it and pick the timezone that defines “today” and month boundaries. You land on the calendar ready to plan.
Define the inventory the calendar rows represent. Reorder when the physical layout changes.
Schedule on the calendar, search from the command palette, nurture guests, pull numbers in Reports, and invite teammates when you are ready.
Set expectations before you invest time in a trial.
Straight answers grounded in how the product actually behaves.
The last paid night is the day before check-out. Nights are stored as [check-in, check-out) on calendar dates, so bars line up with how guests count nights and you avoid off-by-one errors.
Philoxenia uses your property timezone to compute “today,” month navigation, and stay boundaries. Set it in Settings so the board matches local operations.
Pick any date range. Revenue includes only the portion of each stay’s nights that fall inside that range, so partial weeks or months stay honest.
Property owners and managers generate a one-time link from Settings, choose Manager or Front desk for that invite, and share it. The recipient signs in, opens the link within fourteen days, and joins that property only. Front desk roles cannot create invites.
No—and that is intentional. It is built for very small hotels that need calendar, guest, and reporting clarity without channel managers, revenue teams, or enterprise modules you will never touch.
Next.js on the web, PostgreSQL for data, and Clerk for accounts. Straightforward primitives you can trust for a production workspace.
Create an account, add your first property, and invite your team when the calendar reflects reality—not when a vendor says you are “provisioned.”