Starter
One property finding its feet.
Up to 10 units · 1 property · 5 staff
- Reservations, folios and guests
- Housekeeping and maintenance
- Your own booking page
- Reports and CSV export
Reservations, direct bookings, housekeeping and the money actually collected — one calm system in naira, online and offline. No spreadsheets, no double-bookings, no guessing what was paid.
These are not edge cases. They are Tuesday. NiroStay is designed around the moment each one happens.
Two confirmations, one key. Someone gets walked, and the review mentions it for a year. Availability is decided by the database, not by whoever looked last.
Bank alerts in one phone, the reservation book in another, and checkout becomes a negotiation. Collected is verified receipts only; the balance is computed from the folio.
Turnover instructions travel by shouting, and the checkout-to-check-in window collapses. The clean is queued by the checkout and visible on a phone that works offline.
The calendar, the folio, the cleaner's queue and the guest's booking page all read the same inventory and the same money. Nothing is synchronised because nothing is separate.
A unit × date calendar, conflict protection at the database, and a check-in that attaches the guest to the room and starts the folio in one action.
Charges, refunds and verified payments on one folio. VAT and levies derived from rules; invoices issued with numbers from your own sequence.
Your name, your colours, your address. A twenty-minute hold, a deposit through Paystack, and a confirmation the desk recognises. No commission.
Turnover, deep clean and inspection queue on the cleaner's phone, with photo proof and retries when the network drops.
Repeat guests matched on email or phone, with stay history, lifetime value and an open balance that follows them between visits.
Occupancy, earned versus collected, channel mix and outstanding by currency. Every figure traces to a folio line and a verified receipt.
Four jobs, four screens, all reading the same inventory and the same money. These are previews, labelled as previews.
The same engine, arranged for the way each business actually sells a night.
Long stays, cleaning between guests, a receptionist who is also the accountant. The building is the product; the admin should not be.
Read the use case →Room types, a rate calendar, walk-ins and a manager who needs the night's revenue before midnight.
Read the use case →Many units across many buildings, often with no front desk at all. The system is the front desk.
Read the use case →One brand, several addresses, a finance team that needs one book and a guest who sees the building, not the group.
Read the use case →Fourteen days with your real rooms, no card. A plan is by unit band, not a per-room multiplication, and staff accounts are not a line item.
One property finding its feet.
Up to 10 units · 1 property · 5 staff
A property with a team.
Up to 40 units · 3 properties · unlimited staff
A group of buildings.
Up to 150 units · unlimited properties
All plans include the booking engine, the folio and the reports. Annual billing is twelve months for the price of ten. Prices exclude VAT.
The claims on this site are the ones the product can keep. Where it cannot yet, the page says so.
Housekeeping was built for a weak signal. Actions queue on the device and retry with idempotency keys, so a completed clean or a recorded payment cannot apply twice. The rest of the console needs a connection, and says when it has lost one.
Bank transfers with a reference today, and cards or transfers through Paystack with your own merchant account. Only verified money counts as collected; a transfer you recorded is visible as recorded, not proved.
The channel manager speaks Channex and is built and tested against a stub provider; live OTA connections are being onboarded one property at a time. Direct, walk-in, corporate and agent demand is tracked per booking today, so you always know which channel earned the night.
Yes. Owner, manager, front desk, finance and housekeeping each see what their shift needs, and property access can be narrowed per person. Every sensitive action lands in the audit trail.
Days, not quarters. We map your units, rate plans and one weekend of rates with you, open your booking page, invite your team, and hand over the same console you can try now.
No. Reservations, guests, folios and reports export as CSV, and the 30-day export window after termination is written into the terms.
NiroStay is a product of 34orients Ltd, a software company incorporated in the UK with an office in Nigeria. The people who build it also onboard you.
Thirty minutes, your numbers, no slideware. We walk through the real product — the same build linked across this page.
Prefer email? [email protected]