SALTO is one of two primary access-control families wrapped by the operating layer. The integration covers three SALTO product lines, each suited to a different building profile.

SALTO KS. Cloud-based access control for buildings that need centralised credential management and remote operation. The integration uses the KS REST API for credential issuance and revocation, real-time door commands, and event subscription. KS is the default choice for portfolio operators who want a single management surface across multiple buildings.

SALTO Nebula. A unified cloud platform for SALTO's broader hardware range. The integration uses the Nebula REST API and event stream. Nebula carries the more recent SALTO product roadmap and is the recommended path for new commissioning unless an existing building is already on KS.

SALTO Homelok. Designed for residential applications with a stronger resident-facing posture — mobile credentials, guest passes, delivery codes. Where Homelok is deployed, the operating layer wraps it the same way: residents see the Apareé surface, Homelok handles the door.

What gets wrapped. Door control commands, credential lifecycle (issue, modify, revoke, replace), real-time event ingestion (access granted, denied, door held, forced), and device health telemetry. Configuration of doors, schedules, and access groups remains in the SALTO console where SALTO owns the truth — the operating layer reads from those configurations rather than mirroring them.

What is unified. From the resident's perspective, there is no SALTO. There is the building. The same is true for staff using the operations console and for the workflows that issue access decisions. SALTO is an implementation detail, swappable without disturbing the experience.