Salto Systems
SVN Data-on-Card Architecture — Wireless Access Without Cable to Every Lock
Salto Systems (Oiartzun, Basque Country, Spain, founded 2001) is Europe's largest independent access control manufacturer, known for the SVN (Salto Virtual Network) architecture that stores access data on the key card itself rather than requiring a cable to every lock. With 3,000+ employees and installations in 100+ countries across healthcare, education, hotel, and commercial sectors, Salto is particularly strong in the European market for retrofit and new-build electronic access control where running RS-485 cable to every door is impractical.
Role in our panels
How we use Salto Systems
SVN (Salto Virtual Network) architecture: in SVN, the keycard (Mifare DESFire EV2 or Salto BLE-capable card) acts as a data carrier — when a user taps an SVN-enabled update point (typically a heavily trafficked door), the card is updated with new access permissions and any blacklist entries. This 'offline-online' architecture means each Salto lock decision is made locally (battery-powered lock processor checks card data against its internal whitelist), while card updates propagate across the building via user foot traffic. No cable to individual locks needed — only update points (typically 3-5 per floor) require a cable. SVN update points connect to the Salto Space access management server via TCP/IP or RS-485. SALTO KS cloud access: for smaller commercial installations (< 200 doors), Salto KS (Keys as a Service) provides cloud-managed access control: lock firmware updates, user provisioning, and access log retrieval all via Salto KS cloud API. Salto KS REST API enables integration with building management systems: room booking software (Microsoft Bookings, Condeco) sends access permission updates via Salto KS API — meeting attendee gets temporary access to booked room. For KNX integration: Salto KS webhook sends door opened/closed events to middleware → middleware maps to KNX group address write via KNXnet/IP → KNX binary GA triggers room lighting and HVAC occupancy mode. KNX integration methods: (1) Salto SVN IP-enabled update points provide a BACnet object for door status — Intesis IN701KNX BACnet-to-KNX gateway translates this to KNX group address. (2) Salto Space server REST API → custom middleware (Node.js) → KNXnet/IP socket → KNX group address write. (3) Hardwired: Salto locks with relay output (Salto XS4 GEO model with AUX relay option) → dry contact → KNX binary input → DPT 1.002 door status. (4) Home Assistant integration: Salto KS via HA community integration → KNX HA integration → KNX group address. Method (3) and (4) are most common for smart building KNX integration. TTHotel PMS integration module: for hotel applications, the Salto TTHotel module integrates directly with Oracle Opera Cloud, Mews, Protel, and other PMS systems via XML/JSON API. Guest check-in in Opera → Salto TTHotel module encodes a new keycard for the assigned room → card created with check-out date validity → desk agent issues card at front desk. KNX hotel room automation link: Opera check-in event → middleware → KNX group address (DPT 18.001 scene recall) → welcome scene activates in room (lights 70%, HVAC comfort, TV on). This requires a separate KNX integration middleware alongside the Salto TTHotel module — the Salto system itself does not natively write KNX telegrams.
Salto integrates with KNX via Salto KS REST API webhook or Salto Space server BACnet objects (via Intesis IN701KNX), providing door open/closed status and access granted/denied events as KNX binary group addresses. Relay-output Salto locks (XS4 GEO AUX relay) connect directly to KNX binary inputs for hardwired integration.
Used in these project types
Salto Systems products
Key components we install
XS4 GEO slim profile lock
Slim-profile electronic lock cylinder for standard European mortise lock cases. Supports SVN data-on-card (Mifare DESFire EV2), Bluetooth Low Energy mobile key (SALTO KS app), and RFID. Optional AUX relay output provides a dry contact (NO, closes on door open) for direct hardwired KNX binary input integration — the most reliable and lowest-latency Salto-to-KNX integration method. Battery life: up to 2 years on AA batteries depending on access frequency. Fits DIN18252 and ANSI A156.30 lock cases. Used for office internal doors, meeting rooms, and server rooms where no cable run to the lock cylinder is practical but real-time KNX door status is required via the AUX relay.
XS4 2.0 mortise lock
Full mortise electronic lock with integrated card reader. Supports Mifare DESFire EV2, Mifare Classic, and OSDP v2 reader interface for third-party access controller integration (Lenel, Genetec, Paxton). In OSDP mode: the Salto XS4 2.0 reader communicates with the external controller over RS-485 OSDP v2, while the lock cylinder decision-making remains on the SVN card. Used in high-security entrance doors, server room access, and perimeter access points where a full mortise lock with anti-panic function is required. Available in stainless steel and black finishes. Audit log: 1,000 events stored in lock memory.
Salto Space access management server
Windows Server-based central access management platform for SVN installations. Manages users, access levels, time schedules, and lock database for up to 64,000 doors. REST API for integration with third-party systems: HR software (SAP, Workday) for user provisioning, room booking systems (Condeco, Robin) for temporary access grants, and KNX middleware for door status forwarding. BACnet object server (optional module): exposes door status as BACnet binary input objects — Intesis IN701KNX BACnet-to-KNX gateway reads these objects and writes to KNX group addresses. On-premise deployment: Windows Server 2016+, SQL Server Express (included for <10,000 users). Requires fixed IP on the building network for KNX middleware TCP/IP connection.
SALTO KS cloud access controller
Cloud-managed access control platform for smaller commercial installations (up to 200 doors). All lock management, user provisioning, and access log retrieval via Salto KS REST API (OAuth2 authentication). Webhook support: sends real-time door open/close events to middleware endpoints — middleware writes to KNX group address via KNXnet/IP. Home Assistant community integration available: exposes doors as HA lock entities, automations can write to KNX via HA KNX integration. Limitation: REST API polling (not full push for all events) — state updates up to 30 seconds delay. For latency-sensitive KNX automation (immediate lighting response): prefer Salto XS4 GEO with AUX relay output instead of SALTO KS cloud API.
TTHotel PMS integration module
Middleware module integrating Salto Space access management with hotel property management systems (PMS) via XML/JSON API. Supported PMS: Oracle Opera Cloud, Opera On-Premise, Mews, Protel Air, Fidelio, Cloudbeds. Check-in workflow: guest checks in at PMS → TTHotel module encodes keycard for assigned room with check-out date expiry → desk agent issues card at front desk within 5 seconds. Check-out: PMS notifies TTHotel → card blacklisted at next SVN update point contact. KNX room automation link: check-in event from TTHotel → KNX middleware → DPT 18.001 scene recall → welcome scene in room. Requires Salto Space on-premise server and a separate KNX middleware for the PMS-to-KNX event bridge.
Salto Systems FAQ
How is Salto SVN different from traditional wired access control for KNX integration?
Traditional wired access control (e.g. Paxton, Lenel) runs RS-485 or IP cable to every card reader, with a central controller deciding access in real time. Every door status change is available to the controller (and thus to KNX via relay output) immediately. Salto SVN locks are mostly cable-free — each lock makes its own access decision locally. Door status (open/closed) from SVN locks is only available to the Salto Space server via SVN update point propagation — which can have a delay of minutes to hours depending on user traffic. For real-time KNX door status (needed for HVAC occupancy or immediate lighting response): use Salto XS4 GEO locks with the optional AUX relay output, which provides immediate hardwired dry contact — or install Salto IP-enabled update points on key doors for near-real-time status via BACnet/API.
Can Salto SALTO KS integrate with Home Assistant for KNX bridging?
Yes — there is a community Home Assistant integration for Salto KS (saltosystems.com API, OAuth2 authentication). The HA Salto KS integration exposes each door as a lock entity with open/closed state. A Home Assistant automation can then write to KNX via the HA KNX integration: door opens → HA automation triggers → write DPT 1.002 = 1 to KNX group address → KNX switch actuator turns on corridor lights. Limitations: Salto KS REST API polling (not real-time push for all events); delays up to 30 seconds on state updates. For latency-sensitive applications (immediate lighting response on door open): prefer hardwired AUX relay output from Salto XS4 GEO → KNX binary input.
Does Salto support OSDP for reader integration?
Salto's primary reader protocol is their own SVN data-on-card system, not OSDP. However, Salto manufactures OSDP-compatible readers for integration with third-party access controllers (Lenel, Genetec, Paxton) where Salto SVN lock decisions need to interface with a different access controller platform. In such configurations, the Salto OSDP reader communicates with the third-party controller via RS-485 OSDP v2, while the lock cylinder decision-making remains on the SVN card. For pure Salto installations, OSDP is not used — the SVN protocol handles reader-to-lock-to-server communication. Salto also supports BLE (Bluetooth Low Energy) for mobile key access via the SALTO KS app on smartphones, eliminating the physical keycard entirely for staff.
Need a panel with Salto Systems components?
We select, procure, assemble and certify. Free initial consultation.
Request consultation →