Feature
Hostel smart locks and keyless entry
Each guest gets one 4-digit code for gate, entrance and their dorm; in a group, everyone gets the same code. It works from check-in to checkout and appears only in the guidebook, never in a message.
What is keyless entry, and how does it work for a hostel?
Keyless entry replaces physical keys and front-desk key handoffs with time-limited digital codes issued automatically around each guest's stay. In EZ2Stay, that means TTLock smart locks and one 4-digit code per guest (in a group, everyone shares the same one) that works on the gate, the entrance and their dorm, instead of a different code for each door. The code is generated and put on the locks on the arrival day at 07:00 property time, works from the guest's check-in time, is shown only in the guidebook once the guest's online check-in is complete, and is deleted at checkout — no key to cut, return or lose. Smart lockers on the same code are on the roadmap.
What does it do today — and where does it stop?
Every capability with its honest limit and its status: Live, Beta or Roadmap.
| Capability | Limit | Status |
|---|---|---|
| TTLock native integration | the only live lock brand — Nuki, Salto, igloohome and Yale are on the roadmap | Live |
| One 4-digit code per guest for gate, entrance and dorm | the digits are unique across every lock of the property and stay the same if the guest moves bed or dates | Live |
| Code put on the locks on arrival day at 07:00, valid from check-in time, deleted at checkout | activation and deletion run on the schedule set for each zone, not on demand mid-stay | Live |
| Group bookings: everyone in the group gets the same code | one code per group, nothing to choose; a code is never shared outside the group | Live |
| Early access and late checkout extend the entrance window | dorm windows are never extended — a fixed security boundary | Live |
| Access history per lock: every opening with time and method | read from TTLock at set times each day, or on demand from the admin | Live |
| Low-battery warning per lock | the lock turns red on the admin Locks page and the owner gets an e-mail alert | Live |
| Smart lockers on the same guest code | no locker hardware is connected yet — not live anywhere | Roadmap |
How does it work, step by step?
The code goes onto the locks on arrival day
At 07:00 property time on the arrival day, EZ2Stay generates the guest's unique 4-digit code and puts it on the gate, the entrance and their dorm through the TTLock API.
The guest sees it in the guidebook
The code appears only in the guidebook, which opens once the guest's own online check-in is complete. It works from the property's check-in time and is never sent by message.
One code opens every allowed door
The same 4-digit code works at every zone the guest is entitled to — no separate PIN to remember per door.
Early access or late checkout, if purchased
The entrance window can extend to start earlier or end later. The dorm window never changes, whatever is purchased.
Checkout deletes the code
When checkout time is reached, the code is removed from every zone via the TTLock API — nothing lingers for the next guest to find.
Every opening is logged
Each lock's history records openings with time and method, read from TTLock at set times each day or on demand.
What can the owner configure?
Defaults you get on day one, and what stays fixed by design.
| Setting | Default | Who can change it |
|---|---|---|
| Standard access window per zone | gate 08:00–18:00; entrance and dorm 14:00–11:00/12:00 by zone | Owner |
| Early access (entrance start time) | off | Owner, purchasable per guest |
| Late checkout (entrance end time) | off | Owner, purchasable per guest |
| Dorm access window | fixed to the stay dates | Not configurable by early/late access — a hard security boundary |
| Codes in a group booking | one code shared by the whole group | Not configurable — the same for every group |
| Staff-only doors (e.g. a basement) | excluded from guest codes | Owner |
Where does it run in production?
In production · Popcorn Hostel, Bucharest
This runs the door hardware at Popcorn Hostel, Bucharest — 15 smart locks: 1 gate + 1 entrance + 12 dorms + 1 basement. Guests open the gate, the entrance and their dorm with one code; the basement is staff-only, and no locker hardware is installed.
Read the Popcorn Hostel case studyNot a fit if
- You already run Nuki, Salto, igloohome or Yale hardware — those brands are on the roadmap, not live; TTLock is the only lock brand EZ2Stay controls today.
- You need guest lockers opened by the same code today — smart lockers are on the roadmap, not live.
- You want staff to hand over a physical key at arrival — the whole point of this system is that nobody needs to be there to do it.
- You need per-guest codes that persist beyond checkout for late luggage pickup — codes are deleted on the checkout schedule, not held open manually.
FAQ
Smart locks — questions operators ask
How many codes does a hostel guest need to remember?
One. A single 4-digit code opens the gate, the entrance and their dorm — every door a guest is entitled to for that stay.
Which smart lock brands does EZ2Stay support?
TTLock is the only live brand today, with native integration on gate, entrance and dorm locks. Nuki, Salto, igloohome and Yale are on the roadmap.
Does the code open lockers too?
Not yet. Smart lockers on the same guest code are on the roadmap; today the code covers the gate, the entrance and the guest's dorm.
When does a guest's code stop working?
At checkout time, the code is deleted from every zone via the TTLock API. It never carries over to the next guest.
Does buying early access or late checkout unlock the dorm earlier?
No. Early access and late checkout only extend the entrance window. The dorm access window is never modified — that boundary is fixed for security.
Can I see who opened a door, and when?
Yes. Each lock's history lists openings with time and method, read from TTLock at set times each day; the owner can also request a fresh read from the admin.
Run your hostel without a front desk
EZ2Stay is in closed beta. Request access and we'll onboard your property — typically live in 1–2 weeks, with the channel manager and PMS included.