QKEY
by QENTRA In designA door that opens for the right guest, for exactly as long as their stay.
Guest door access for a property: one NFC or QR tag on each door, a key that lives in the guest’s phone browser, and access that follows the booking — issued when the stay starts, gone when it ends. Sold as a module inside EBO or on its own, one instance per property.
- Runs on
- Web · NFC / QR tags
- Speaks
- English · Français · Nederlands · العربية
- Since
- August 2026
tag per door, printed once, serving every guest forever
details that must match a live booking to get in — name and room
apps for the guest to install
property per instance, never shared
The interface
What it looks like to work in.
A drawing of the real layout, not a screenshot — the product sits behind a sign-in, and we will not fake one. Ask for a demonstration to see the live one on your own data.
What it does
- A static NFC or QR tag on every door — no token in it, so one printed tag lasts for years
- The key lives in the guest’s browser; tapping any door’s tag asks that door to open
- Name and room number must both match a live booking — a phone number is contact, never a credential
- The next door in the sequence — gate, villa, room — is promoted to one big button
- Two lock modes: relay, where QKEY switches something; code, where the guest is shown a PIN for the lock’s own keypad
- White-label: the property’s name, logo and colours on the guest side; the operator’s brand, not ours
Chapter 01
Which door am I at?
That question decided the design. Rather than an app that must know where the guest stands, each door carries its own tag with its own address. The guest taps the door in front of them; QKEY already knows who they are.
Chapter 02
Two ways to open a lock.
Not every property has a gateway, and a villa’s internet is its single point of failure.
Relay
QKEY switches a strike, a relay or a smart lock — through Home Assistant, Shelly, a webhook or a lock vendor’s cloud. The guest taps a button.
Code
The guest is shown a PIN for the lock’s own keypad. No wiring, no gateway, and it still works when the internet is down.
Chapter 03
Why one instance per property.
A booking bug costs a spreadsheet; a door bug costs a break-in. So QKEY is never multi-tenant: each property runs its own instance, provisioned in one command, and every door keeps a working mechanical override.
Who it is for
Guesthouses, villas and small hotels that hand over keys by hand today — and the property operators who run several of them.
In design. The software runs end to end against a mock lock; the hardware has not been bought, so no date is claimed.
Get it
Put it to work.
-
Demonstration
On your own data
Thirty minutes with the live product loaded with what you actually run.
Book a demonstration