Opens the app itself, with a switch between what your guest sees and what you
see. No sign-up, no passcode — you land inside both.
More than one property? Here it is for a group of three — the guest picks theirs and sees only that hotel. Both hotels are invented, and nothing you type into either is kept.
What it costs
One app. One price, set by the size of your hotel.
Everyone gets everything; the band sets the price. An agency takes
15–20% of a booking, so five or six room-nights taken direct cover the month.
20–30 rooms
₱1,500per month
About five room-nights a month, taken direct instead of through an
agency.
The first two hotels pay a founding rate and keep it for good.
I’d rather have two owners who vouch for this than three who paid list. Ask whether they
are still open.
Setting it up: ₱18,000, once. Your app in your own colours, a Google account in
your name, your content loaded with you, the room QR codes, and a walkthrough with your
desk. The same at any size.
Pay yearly and you pay for ten months. ₱15,000, ₱25,000 or ₱35,000, and nothing
to remember each month.
Nothing after that. No hosting bill, no charge per guest, no commission on what a
guest books.
Stop whenever you like. One month’s notice, no tie-in — your guest list and content
are in your own Google account, and you can export the lot.
Everything that is in it
What your guest gets
Opens on their stay — tonight, the offer, what is nearby
Room QR straight into the app, with nothing to download
One WhatsApp button to your front desk
Your rooms, dining, tours, transport and policies — only the parts you have
Offers they redeem with a code at your desk or outlet
What’s on — your events, while they run
Photo galleries and a full-screen viewer
A link before they travel, their details already in, a code for the desk
Installs to the home screen and works offline after the first open
English and 简体中文
What you run it with
You edit the content — rooms, photos, offers, contacts — from your phone
Publish, and every guest’s app updates at once
A guest list you own, with CSV export
A front-desk console: approve a guest, or undo it
An outlet console: check a code and redeem it
A PIN for the desk and one for your outlet staff
A dashboard: what was redeemed, and which listings guests actually open
Your arrivals list — typed, pasted, or synced if you run Cloudbeds
Everything in your own Google account
Bot protection on sign-ups
Cross a band and I’ll tell you at your renewal, not mid-year. Nothing is
rebuilt either way.
What it does not do.
Better said now than found in week three.
If you run Cloudbeds, it reads it and never writes back. Marking a guest in on
your own system is still your desk’s job.
No payments, no chat in the app. Guests message your front desk on WhatsApp.
There is no availability calendar and nothing is charged here.
It is a dark app, on purpose. That is what reads as expensive on a phone in a
dim room.
It does not take your guests’ passports. Checking in before arrival works from
the booking you already have — a link, their details filled in, a code for the desk.
Who builds it.
One person, and small hotels are the point. A beach house, an inn, a small
resort. It also runs across an eight-hotel group in Palawan, which is how I know it
holds up. I don’t name clients; I’ll introduce you to one when we both want that.
Your data stays yours. The guest list and the photos sit in your Google
account. I build it; I do not hold it.
If I disappear, your app keeps running. One file on your hosting, one script in
your own Google account.
One client at a time. I’d rather deliver yours properly than sign three and be
late for all of them.
What happens next
Tell me how many rooms you have.
I’ll reply with your price and when I could build it. No tie-in, one
month’s notice, and nothing to pay to ask.