LenelS2 OnGuard, NetBox and Elements Comparison
LenelS2 offers multiple access-control operating models. OnGuard, NetBox and Elements needs to be matched to organizational scale, infrastructure, integrations, administration and lifecycle strategy.
Three platforms, different operating priorities
The most familiar product is not automatically the best fit. Start with day-to-day operating requirements, existing hardware and integration dependencies.
OnGuard enterprise access control
OnGuard is system engineeringed for organizations and facilities that need broad integration, enterprise administration, identity workflows, monitoring and customization. It supports complex deployments spanning departments, facilities and geographies, but that flexibility brings server, database, licensing, upgrade and governance responsibilities.
A system engineering needs to define client and browser workflows, alarm monitoring, identity and visitor functions, video integration, interfaces to HR or other business systems, high availability and disaster recovery. Existing OnGuard environments require a version, hardware and integration inventory before an upgrade or expansion is proposed.
- Enterprise access and alarm monitoring
- Identity, visitor and credential workflows
- Open integration and business-system interfaces
- Server, database and high-availability engineering assessment
NetBox browser-based access control
NetBox provides browser-based access control and event monitoring through the LenelS2 NetBox ecosystem. It can suit organizations and facilities that want an appliance-oriented system with scalable nodes, reporting, threat-level functions and integrated event workflows.
Plan node capacity, network communication, partitioning, video association, BlueDiamond readers, administrator roles and backup. A NetBox expansion needs to confirm current software support and compatibility for nodes, application blades, readers and integrations.
- Browser-based administration and monitoring
- Network nodes and application blades
- Partitioning and multi-site organization
- Video, mobile credential and integration options
| Platform | Operating model | Typical engineering assessment emphasis |
|---|---|---|
| OnGuard | Enterprise server or supported cloud deployment | Integration, scale, identity, database and resilience |
| NetBox | Browser-based appliance ecosystem | Nodes, partitions, event monitoring and expansion |
| Elements | Cloud-based access and video | Subscriptions, supported hardware, remote administration and migration |
Elements cloud access and video
Elements provides a cloud-based path for access control and supported video workflows. It can reduce local server responsibility and help organizations and facilities manage distributed sites, but it introduces subscription, Internet, identity and cloud-administration considerations.
Existing NetBox hardware may have supported transition options in certain configurations, and hybrid relationships with OnGuard may be available. These possibilities must be confirmed through current LenelS2 documentation and the exact installed hardware; they needs to not be assumed from a brand name alone.
- Cloud administration and subscription ownership
- Supported controllers, readers and cameras
- Remote and multi-site operating needs
- Migration and hybrid-platform verification
Credentials, integrations and migration
Credential technology, readers and identity data can be more difficult to migrate than the server. Inventory card formats, badge data, access levels, readers, Mercury or NetBox hardware, wireless lock integrations and enrollment systems. Identify the authoritative source for people and access approvals.
For integrations, document data direction, event handling, API or middleware ownership, version dependencies and failure behavior. Migration acceptance needs to include user records, permissions, schedules, alarm priorities, video links, reports, administrator roles and emergency procedures.
- Credential and reader technology inventory
- Controller and firmware compatibility
- Identity, visitor, video and elevator integrations
- Database, reporting and operational acceptance tests
How we plan and deliver the work
The final system engineering depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Inventory
Capture software, controllers, readers, credentials, servers and integrations.
Select model
Match hosting, scale, operations and governance to a platform.
Plan transition
Define retention, replacement, data migration and downtime.
Accept
Test access, alarms, video, identity, reporting and emergency workflows.
Information to gather before system engineering
Good decisions are easier when the security engagement team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Current platform, version and support status
- Controller, reader and credential inventory
- Server, database, cloud and resilience requirements
- Identity, visitor, video and building-system integrations
- Migration schedule, rollback and administrator training
Frequently asked questions
These are common engineering assessment questions. A site-specific answer needs to be confirmed during discovery and system engineering.
Is OnGuard only for very large organizations and facilities?
OnGuard supports a range of configurations, but its enterprise integration and infrastructure capabilities needs to be justified by the client’s needs.
Is NetBox cloud based?
NetBox is a browser-managed access-control and event-monitoring ecosystem. Elements is LenelS2’s cloud-based platform.
Can NetBox hardware move to Elements?
Some supported transition options may exist, but the exact node, firmware and current LenelS2 guidance must be verified.
Where can customers find LenelS2 downloads?
Use LenelS2 Connect, Support Central or the official Elements portal as appropriate. Some resources require an authorized account.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Discuss a commercial security security engagement
Tell us about the doors, buildings, users, existing equipment, operational requirements and desired completion date. We will help organize the right discovery and system engineering conversation.