Homeowners who start researching "alternatives to Salto" are usually not unhappy with Salto hardware — they are trying to understand what else exists, and whether a different architecture fits their property better. The honest answer is that the decision is less about brand and more about three structural questions: where the access data lives, how mobile credentials are issued and revoked, and how cleanly the lock talks to the lighting and control system that already runs the house.
This is a companion to our existing Salto vs UniFi Access comparison, which focuses on wiring and credentials for a single estate. Here the goal is a broader framework — the questions worth raising with your integrator before you commit to any platform.
Cloud-managed vs. on-premise: the real fork in the road
Salto itself frames its own product line around this split, and it is a useful way to think about any access-control alternative, not just Salto's. According to Salto's own comparison of its platforms, cloud-based access control (what Salto calls ACaaS, or Access Control as a Service) stores software and data on remote servers, is managed from anywhere with an internet connection, and shifts infrastructure maintenance to the service provider — Salto's cloud products are SALTO KS and SALTO Homelok. On-premise access control, which Salto delivers as SALTO Space, keeps the infrastructure and data on the organization's own network, which Salto describes as reducing points of vulnerability and removing dependence on an internet connection, at the cost of more hardware and software to maintain locally (Cloud-based or on-premise access control solutions).
The same split applies to UniFi Access. Ubiquiti's Cloud Gateway hardware (the Dream Machine and Cloud Gateway lines) runs UniFi Access as one of several applications on the gateway itself — alongside UniFi Network and UniFi Protect — while still offering remote management through UniFi Site Manager and automatic cloud backups for configuration (UniFi Cloud Gateways). That's a hybrid: the access-control logic and credential database run locally on hardware you own, while management and monitoring are available from anywhere. For a homeowner evaluating alternatives to Salto, this is the first question to settle with a contractor: does the credential database live in a vendor's cloud, on local hardware you control, or some combination — and what happens to lock behavior if that connection drops?
Mobile credentials, revocation, and who holds the keys
Every modern access platform promises mobile keys, but the mechanics differ. Salto's cloud platforms (KS and Homelok) are built around remote credential issuance — administrators can add, revoke, or reassign access from a web interface without touching the door hardware, which Salto positions as a core advantage of the as-a-service model. On-premise Salto Space trades some of that remote convenience for data staying on the owner's own servers.
UniFi Access folds credential management into the same dashboard used for cameras and network gear — mobile credentials, PIN codes, and NFC fobs are issued and revoked from one interface, with every door event logged alongside the UniFi Protect camera timeline. Ask your integrator directly: who actually holds the API that issues and revokes a credential, and what is the fallback if that service is unreachable at 2 a.m.? That answer — not the marketing name of the platform — determines how the system behaves on a bad day. A full accounting of camera, access, live-guard, and alarm layers together is covered in our security upgrade overview.
How the lock becomes a native object in Crestron or Lutron
The part of this decision that gets skipped most often is integration depth: does the lock just unlock the door, or does it actually become part of the house's control system?
Crestron Home OS 4.5 changed this materially. Before that release, Crestron Home natively supported only Yale locks in the US; third-party locks had to be shoehorned in through workarounds. With OS 4.5, Crestron introduced a "Door Lock Device Type" that lets Crestron Service Providers write native drivers for effectively any wireless lock, so it appears directly in the access-control section of the Crestron Home app rather than as a bolted-on extra. Crestron's own announcement describes this as eliminating "a major pain point for integrators" and enabling full user-management features — PIN assignment, per-door permissions, and guest access — for any connected lock once it has a driver (Crestron Home OS 4.5: Locks, Lighting, and Climate Control). Crestron's own developer documentation lists "Lock" as a formal extension driver device type alongside Camera, Door Access, and Door Station, confirming this is a structured, supported category rather than a one-off hack (Crestron Home OS Documentation — Drivers).
Practically, this means the question to ask about any Salto alternative is not just "does it have an app" but "does a certified driver exist for this lock inside Crestron Home, and who maintains it?" A platform with a mature, actively maintained driver behaves like any other room device — door status on the touch panel, scenes that respond to lock state, PIN management from the same interface used for lighting and shades. A platform without one means a separate app, a separate credential system, and a separate point of failure.
For Lutron-centric homes, the lock relationship works differently: Lutron's lighting and shading platforms don't natively absorb door locks the way Crestron's extension-driver framework does, so access control there typically runs as a parallel system coordinated at the network level rather than appearing as a lighting keypad object. That's a question worth raising directly with whoever designs your lighting system — ask specifically how door events will surface alongside lighting scenes, and don't assume the answer is the same as it would be on a Crestron-based house.
A decision framework, not a verdict
There is no single "best alternative to Salto" that fits every property. A homeowner choosing between cloud-managed and on-premise access control, or between Salto and UniFi Access, should walk into that conversation with three questions settled: where does the credential data actually live, what is the fallback behavior if connectivity drops, and does a maintained driver exist to make the lock a native part of whatever control system runs the rest of the house. Cave Group designs around Crestron for control and Lutron for lighting and shades, and treats access control as one layer in a broader security stack — cameras, access, live monitoring, and alarm — rather than a standalone purchase. If you're weighing lock platforms as part of a larger project, our security upgrade page walks through how those layers fit together.