Use case · Go Keyless
Mobile keys on the locks already on your doors.
The phone is the key, provisioned from the PMS, revoked at move-out and working offline, on every connected lock and the common-area readers already installed. Pricing can start at $0 depending on setup, paired with a revenue share.
The problem
Keyless was supposed to simplify things.
Then the lock came with its own app, the front door came with another, and staff started provisioning credentials by hand. The building that wants to switch resident apps can't, because the locks are tied to the old one.
What operators say
Three things operators say about keyless.
“Every lock came with its own app.”
Every connected lock and common-area reader opens with one key, in the building's own app.
“Staff provision credentials by hand.”
Credentials are provisioned from the PMS to the lock system and revoked the same minute the lease ends.
“Our locks are tied to the old resident app.”
ElevateOS connects to the lock system already installed. No reprogramming.
What's included
Keyless access on the locks already installed.
PMS provisioning
The PMS says who. ElevateOS issues the key.
Revoke at lease end
Access ends the same minute the lease does.
Offline mobile keys
Keys work over Bluetooth without signal.
Device binding
Each key is bound to one phone.
One-tap unlock widget
The front door is one tap from the home screen.
Unit locks and common-area readers
One key for the unit, the lobby, the garage and the gym.
Mixed lock brands, one app
Every connected lock brand in the portfolio runs in one app.
Audit log
Every lock event is logged.
Deep dive
The PMS says who. The lock says how.
The PMS says who lives in the unit. The lock system says how the door opens. ElevateOS does the rest: the key is provisioned, bound to the resident's phone, works offline and is revoked the same minute the lease ends.
Security
Device binding and instant revoke, by default.
Each key is bound to one device. Deactivation revokes it instantly, and every lock event lands in the audit log. ElevateOS is SOC 2 Type II certified.
Keep going
More ways to modernize the building.
IT and innovation
The credential lifecycle, the open API and the integration layer.
Proof
Keyless already running on ElevateOS.
2.56M+
access events on a single lock platform
The Hadley: access control and lockers in one app
50+
integrations
SOC 2 Type II certified
Works with
Keyless runs on the rest of the platform.
Access integrations
Keyless access, unit locks, access control, intercoms, PMS sync and every integration run in one app.
FAQ
Questions buyers ask on the first call.
Do locks need to be reprogrammed to go keyless?
No. ElevateOS connects to the lock system already installed.
Can one app run different lock brands across a portfolio?
Yes. Every connected lock brand in the portfolio runs in one app.
Does the mobile key work over Bluetooth?
Yes. The key works over Bluetooth without signal, with device binding and instant revoke still in force.
Do common-area doors use the same mobile key?
Yes. Unit locks and common-area readers open with the same key.
Where does the key appear on the resident's phone?
In the building's branded app. A one-tap unlock widget sits on the home screen.
Does staff have to issue keys by hand?
No. Credentials are provisioned from the PMS to the lock system, and move-out revokes them the same minute the lease ends.
Is ElevateOS keyless access secure?
Each key is bound to one device, and every lock event is logged. ElevateOS is SOC 2 Type II certified.
How is keyless access priced on ElevateOS?
Pricing is per unit, scoped to the modules the property turns on. Pricing can start at $0 depending on setup, paired with a revenue share.
Related
Keep exploring.
See the resident app open the door.
Bring the lock schedule and watch a key provisioned from the PMS open a unit door and a common-area reader on the same phone.