The register, except it counts itself.
Every bed on every floor, coloured by what it is doing — and one already taken cannot be given twice.
StayOne is PG and hostel management software for India — beds, rent, UPI payments, complaints and staff in one app, replacing the register, the rent sheet and the WhatsApp group your building runs on today. Your manager and your residents use the phone already in their pocket, in the language they speak.
Photographed from the running app, not drawn for a website — the same ones they open on a Tuesday morning.
Every bed on every floor, coloured by what it is doing — and one already taken cannot be given twice.
Bill the whole building in one tap, take part payments, and see deposits counted apart from rent.
Straight to your own UPI ID — no gateway, no cut — and nothing is credited until you have approved it.
The real screens, on sample data. All four tabs keep one set of books — so check someone into a bed here, and their name is in the rent register before you get there.
The refusal is the product. Not a warning printed after the fact — the second lease
is never written, and the app answers 409 BED_OCCUPIED.
Part payments, receipts and the arrears that follow are the three things a rent register on paper gets wrong. Every rupee taken here prints a receipt.
The lists grading what you type are backend/src/lib/triage.ts, ported
here unchanged. A gas leak outranks a corridor bulb however it was typed, and in
whichever language it was typed in.
Every sentence is written from the figures the other three tabs are showing, never from a script. It can read; it cannot record a payment or move a resident.
Try one of these
Try one of these
Every sentence is written from the same figures the other three tabs are showing — not from a script. Check a resident in, collect a rent, file a gas leak, then ask again and the answer has moved.
In the product it works the same way, against your own data, fetched as you: a manager's answer covers their property and an owner's covers their portfolio. Every source it can reach is a read. It cannot record a payment or move a resident.
Beds, rent and UPI have their own screens above. These are the rest — the jobs that usually live in a second notebook, a WhatsApp group, or nobody’s hands at all.
Residents write in their own words and never pick a priority — the app grades what they wrote, in three languages, and the gas leak goes above the corridor bulb. Try it in the sandbox above.
Print the A4 poster for the gate or send the link on WhatsApp. They type a name and a number, and nobody becomes a resident until you approve them.
Days worked, advances taken, and what each person is owed at month end.
What came in, what went out and what it leaves — per property, per month.
Agreements and ID proofs, filed against the resident they belong to.
Post once. Everyone sees it, and there is a record of who was told what.
Every screen, not just the menus — each person reads it in their own language.
Behind the chat button on every screen. It answers from your own figures, sees only what you are allowed to see, and can only read.
So they do not get it. Each role opens to the thing that role actually does, and can only ever see its own properties.
Stated plainly, because a PG holds ID proofs, agreements and payment records for a hundred people who did not get a choice about it.
Six digits, never stored as typed. Nobody at StayOne can read a resident's PIN, and a forgotten one is reset, not looked up.
Every screen and every answer is limited to the property or organisation you belong to. One owner's portfolio cannot appear in another's.
Public forms are rate-limited per address and carry a proof-of-work check, so a script left running in a browser tab cannot fill your database with junk.
Who changed what, and when. Rent moved, a bed reassigned, a resident checked out — recorded rather than remembered.
The only real work is entering your rooms and your residents once. After that the app does the counting.
Name, city, how many floors and what sharing you run. That is the whole form — no card, no call scheduled before anyone has seen anything.
Two minutesRooms and beds are created per floor in one pass, with rent per bed. Existing residents are added against the bed they are actually in, with their rent day.
An afternoonThey open Today and see rent due, tickets and free beds. Residents get a PIN and see their own rent and complaints. Nothing to install — it opens in a browser.
From day oneWhen an operator needs a laundry, a tiffin service or a plumber at short notice, this is the list they check. Getting on it is free, and takes about a minute.
No fee, no commission, and nothing taken from what an operator pays you.
Somebody calls the number you give us before it is shown to anyone. Nothing is listed off a form alone.
One message and you are removed. You are not signing up to anything you cannot leave.
You say which neighbourhoods you will actually travel to, and only operators there see you.
Billing is switched off while StayOne is in early access, and every feature is open to every account. When it does start, the only thing that separates the plans is how big your PG is. A fifteen-bed PG needs its rent ledger and its expense book exactly as much as a two-hundred-bed one does — so a bigger plan buys room, not capability.
All three include everything: the bed map, rent and receipts, reports, expenses, payroll, visitors, bulk import, tickets, notices and the resident app in English, Hindi and Telugu. Rent is collected by UPI into your own account or as cash at the desk — there is no gateway and no cut. Prices are not set yet; nothing is charged while StayOne is in early access.
Name, city and how many beds. We set the property up with you, and your manager runs it from the same day — or try the sandbox above first and decide after.
owner · manager · resident · one tap each