LenelS2 OnGuard, NetBox and Elements platforms
Choose the LenelS2 platform family from enterprise scale, appliance preference, cloud strategy, integrations and lifecycle requirements.
What LenelS2 includes—and how to choose
LenelS2 provides distinct access-control platform families. OnGuard is used for enterprise-scale access and integration requirements; NetBox uses a web-based appliance approach; Elements is a cloud-based offering. Platform selection should reflect operating model, integration depth, site count, cybersecurity policy and the installed controller base.
A LenelS2 design includes controllers and interface modules, readers and credentials, locking and egress hardware, servers or appliances, database and backup responsibilities, operator workstations and supported integrations. Exact software, license and hardware compatibility is checked using current manufacturer documentation before an upgrade or expansion.
Migration deserves its own plan. Existing Mercury-based or proprietary panels, reader technologies, badge formats, cardholder records, alarm procedures and integrations are inventoried. Reusing a panel may be technically possible but operationally unwise if firmware, capacity, cybersecurity or support status does not meet the target standard.
Product families and their roles
This portfolio map separates the main LenelS2 functions so the project is not reduced to a generic model list.
OnGuard
Enterprise access control, identity, alarms and integration architecture.
NetBox
Web-based network controller and appliance approach for supported deployments.
Elements
Cloud access-control operations for the supported hardware and subscription model.
Controllers and credentials
Field panels, interface modules, readers and badge technologies tied to platform compatibility.
Architecture decisions before procurement
The selected family must fit the opening, scene, network, power, software and administrative environment.
Platform operating model
Choose enterprise server, appliance or cloud administration intentionally.
Database and recovery
Define backup, redundancy, upgrade, archive and administrator recovery responsibilities.
Panel lifecycle
Inventory controller model, firmware, capacity, downstream modules and support status.
Integration governance
Document the source, destination, event, owner and failure behavior for every interface.
Commissioning evidence
Acceptance should demonstrate the intended workflow under realistic conditions, not only show that devices appear online.
- Exercise door, alarm, identity and schedule scenarios across representative sites.
- Verify controller behavior and event recovery during server or network interruption.
- Test supported integrations with expected and failed transactions.
- Deliver platform version, licenses, backups, panel maps, door schedules and administrator roles.
Official LenelS2 resources
Use the manufacturer pages below for current product status, compatibility, release notes, software and firmware. We link to official resources and do not host firmware files locally.
Detailed planning and product-family guides
Use the detailed LenelS2 guides below to compare specific hardware, software and deployment decisions.
Build an installation-ready LenelS2 scope
Share the site, existing equipment, required workflows and project timing. We can identify the survey, compatibility checks, design and commissioning evidence the project needs.
Discuss products and installation