Devices and integrations
We read each vendor's official documentation and recorded what we found and what we could not verify. No integration has been tested on a physical device yet. A status only changes after a recorded test.
23 lock and access control vendors reviewed
Counts are computed from the integration list in the code itself.
These are the kinds of devices the platform deals with in a hostel. Each category connects differently and each model has different capabilities.
A code, card or mobile key, depending on the lock.
Through the vendor cloud API or a gateway
At the entrance, a gate or the kiosk.
Through a cloud reader or a controller
A card per guest, encoded and revoked with the stay.
Through the access control system
A front desk device that writes the card.
Through vendor software or an SDK
Connect locks to the internet for remote commands.
Required by some vendors for remote unlock and revoke
A locker per bed with an electronic lock.
Through the locker system or the lock itself
An iPad or tablet for self check-in.
A browser only, no special connection
Manage several doors and readers in a building.
Through the vendor's local or cloud server
Temperature, leak or usage sensors.
Under study, no connection today
A list of cameras and their locations only.
The platform never receives or stores video
Every integration climbs the same steps in order. We never skip a step without recorded evidence.
Documentation available
We read the vendor's official docs and they are enough to start. No code yet.
Integration developed
We wrote the connector against the docs and tested it on recorded responses.
Tested in vendor sandbox
We ran it against the vendor sandbox with a real test account.
Verified on hardware
We ran it end to end on a physical device.
We never say a device works with the platform before it is verified on hardware, or a payment provider before it is tested in its sandbox.
Every detail here comes from an official page we read on the research date. Anything we could not confirm is marked as not verified. We do not show vendor logos.
23 results
Research date 26 October 2026. Documented capabilities means the vendor lists them in its docs. It does not mean they work with the platform today.
These are fixed conditions for connecting any lock or door to the platform. We ask the installer for them because guest safety comes before any feature.
The exit side of the door always stays mechanical or independent of the system.
Linking locks to the alarm system is the installer's job and is recorded at handover.
A backup key or code at the front desk if the connection or battery fails.
Depends on the vendor. Without it, remote revocation may not arrive at once.
We connect with your account and its permissions. We never reuse one property's account for another.
The lock vendor receives only a credential reference, never a name or ID number.
In the trial hostel you can see how commands and their states show up without any device.