The platform
One system for the whole stay.
The booking, the registration, the folio, the rent, the ledger and the close — in one place, so nothing has to be reconciled between two systems at midnight. Everything on this page is in the product today. Where something is not, it says so.
Front desk
The desk, on one screen.
What is arriving, what is leaving, what is free, and what happened to room 204 last night.
-
Room calendar
Every room down the side, every date across the top, and each stay drawn where it falls — a night or six months, on the same grid.
-
Today's queues
Arrivals, departures and in-house, each one a list you can work down.
-
The whole life of a booking
Create, quote, assign a room, check in, move rooms, extend, check out, cancel, reinstate or mark a no-show.
-
Room status board
Each room's status, who changed it and when. The history cannot be edited after the fact.
-
Guest profiles
One record per guest with their stay history, contact details, occupants and vehicles.
-
More than one property
Run several properties under one organization, with a person's role set per property, and switch between them in the header.
Extended stay
A resident, not 180 bookings.
The part most property management systems bolt on afterwards, and the reason GuestPad exists.
-
Agreements that keep their history
Draft, activate, amend, renew, terminate, expire — each version kept, so you can see what was agreed and when.
-
Rent on your schedule
Weekly, every 28 days, monthly, or once for the term of the stay. Recurring charges post themselves as the dates come round.
-
Deposits
Held against the stay, applied to a folio, or refunded — each step recorded.
-
Resident invoices
Raised automatically for the period, with what has gone past due marked as the days pass.
-
Long-stay tax
Transient tax that stops applying once a stay passes the number of nights your jurisdiction sets, so a resident is not taxed like a tourist.
Registration & signing
Hand the iPad across the desk.
The registration card, the ID and the signature, without a printer or a folder.
-
Four steps, in the guest's hands
Confirm details, capture a photo ID, read each policy, sign.
-
Policies acknowledged one by one
Each policy is accepted separately, and a fingerprint of the exact wording the guest saw is stored with the acknowledgment.
-
A signature that means something
Every signature is stored with a versioned statement of intent to sign electronically, and cannot be altered afterwards.
-
Paper still works
A guest who registers on paper at the desk is recorded the same way, so the record is complete either way.
-
A printable registration card
Rendered on demand. The photo ID is left out unless the person asking for it is allowed to see IDs.
Folios, payments & A/R
Money that adds up.
One folio per stay, split where it needs splitting, and a ledger for the companies that pay later.
-
Folio windows
Route part of the bill to a company and part to the guest, and settle them separately.
-
Charges and corrections
Charges, payments, refunds, adjustments and reversals — corrections are recorded, never rubbed out.
-
Cards on your own account
Payments run through your hotel's own Stripe account, so you are the merchant, the payout is yours, and GuestPad takes nothing per booking.
-
3-D Secure
When the card's bank asks for a challenge, the guest completes it in their own browser and the payment posts only once it clears.
-
Corporate accounts
Companies with credit limits, and a transfer to the city ledger at check-out that stops at the limit unless someone overrides it and says why.
-
Chasing what is owed
Ageing buckets, per-account statements, credit notes, write-offs, and a CSV export of the ageing for your accountant.
The daily close
The night audit, in one run.
GuestPad's night audit is something a person starts when the desk is quiet, not a job that runs behind your back.
-
A pre-check first
It tells you what would stop the run before you start it.
-
What one run does
Posts the night's room charges, renews and expires agreements, posts recurring charges that fall due, raises resident invoices, marks what is overdue, records the day's totals, and moves the business date on.
-
Once per business date
A second click cannot double-post: the close is recorded against the date it closed and each posting has its own key.
-
Dashboards and reports
Today at a glance, extended stay, registration status, revenue, and what is still outstanding.
Your guests' front door
A booking page and a portal, in your name.
Both live at your property's own address, so a guest deals with your hotel, not with GuestPad. How guests find their booking →
-
Direct booking
Your published room types and rates, availability for the dates asked for, and a card taken on your own Stripe account.
-
Signing in without a password
A guest asks for a code by email, or finds a single booking with its confirmation number and their surname.
-
Check in before arriving
Details, ID and policies, done at home. Your desk still checks the guest in when they walk through the door.
-
Paying and signing
Settle a folio or an invoice, read receipts and statements, and read and sign an agreement.
-
Asking for changes
Request a different date or an extension and get a quote back, cancel, or add occupants and vehicles.
-
Talking to the desk
Messages, service requests with a photo attached, and the notices you publish for the property.
Connections
What GuestPad talks to — and what it doesn't yet.
We would rather be dull and accurate here than lose your first month to a promise that wasn't ready.
-
Webhooks, today
GuestPad can call your own systems when something happens, signed so you can prove the call came from us, retried in order if your endpoint is down.
-
Inbound credentials
A partner you work with can be given its own credential to push into your property.
-
Channels: built, not yet switched on
Connectors for Booking.com, Expedia, SiteMinder, Agoda and Priceline are written into GuestPad, but each channel has to certify our connection before a property can enable it. Ask us where a particular channel stands.
-
No developer API keys yet
There is no self-serve public API. If you need one, tell us — it helps us know where to start.
Setup & your team
A checklist, not a project.
The trial starts empty and walks you through filling it in.
-
Seven steps
Property, room types, rooms, charge codes, taxes, policies, team — ticked off as the data appears, not by hand.
-
Starters to edit
Common charge codes and house policies are created for you, so you adjust wording rather than write it from nothing.
-
Your team
An administrator creates each account with a role and hands over a temporary password the person must change when they first sign in.
Security & operations
Guest records deserve a locked door.
Each of these is in the product now. Single sign-on, passkeys and customer-managed encryption keys are not, so they are not listed.
-
Two-step verification
Authenticator-app codes with single-use recovery codes. An owner can require it of admins or of everyone, and the requirement is checked on every request, not only at sign-in.
-
Roles and permissions
10 built-in roles, from receptionist to general manager, assembled from 57 individual permissions such as refunding a payment or seeing a guest’s ID. Enforced on the server, never only hidden in the screen.
-
An append-only audit log
Who did what, to which record, from where. The database itself refuses to update or delete an audit row, and an administrator can read the log inside the app.
-
One hotel cannot see another
Every table carries a row-level security policy keyed to the organization, and the database role GuestPad connects as is not allowed to bypass them. The API refuses to start if it finds that it could.
-
Encrypted database connections
In production GuestPad refuses to start unless it can reach the database over TLS, and the database has no public address at all.
-
Card numbers never reach us
Cards are typed into Stripe’s own hosted fields, on your hotel’s Stripe account. GuestPad’s servers and database never see or store a card number, and a 3-D Secure challenge is completed in the guest’s browser.
-
Retention you set
You choose how long a photo ID is kept — 90 days unless you change it — and how long registration records are kept. A daily job deletes the files when the window closes and records that it did.
-
Documents in a private bucket
ID images and signatures are stored in a bucket with public access blocked, reached only through short-lived signed links, and every read is written to the audit log.
-
Sessions you can end
Sessions live on the server with an idle and an absolute timeout, passwords are hashed with Argon2id, repeated failures lock an account for fifteen minutes, and every user can sign out everywhere else.
-
Backups and recovery
Managed Postgres with automated backups, point-in-time recovery and a high-availability configuration in production, with a written restore runbook.
See it with your own rooms in it.
Start a 14-day trial on Pro, or let us walk you through it first.