Browser-based access control and event monitoring for small facilities through large distributed enterprise deployments.
Products and selection guidance
NetBox appliances and virtual-machine options provide person records, credentials, alarms, threat levels, reporting and system partitioning. Product families range from standard NetBox through Extreme, Enterprise and virtualized deployments; sizing is based on portals, nodes, concurrent operators, integrations, resilience and database partitions.
- NetBox appliance and browser administration
- NetBox Extreme, Enterprise and Virtual Machine scale options
- Threat level, alarm/event and person record workflows
- Partitions, backups, failover and open API integrations
- Door, lock, free-egress, accessibility and fire-alarm requirements
- Network, power, standby battery and outage behavior
- Current licenses, subscriptions, firmware and integrations
- Administrator training, backup, documentation and maintenance
Site-specific design
Boston High Tech inventories existing equipment and validates current manufacturer compatibility before specifying reuse, migration or replacement. Qualifications may be confirmed privately when needed; license numbers, certificate copies and named certificate-holder details are not published.
Request a manufacturer-specific consultation
Projects are supported from our Charlotte headquarters and local client offices serving Massachusetts, New York and New Jersey.
Official manufacturer references
How to compare and specify this product family
For LenelS2 NetBox Browser-Based Access Control, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following access-control system decisions before equipment is ordered:
- Number and type of controlled openings
- Controller, reader, lock and credential compatibility
- Cloud or on-premise administration and ownership
- Offline behavior, backup power and emergency operation
- Directory, HR, video, visitor and elevator integrations
- Licensing, cybersecurity, training and lifecycle support
Installation, testing and handoff
A site survey records each opening, door hardware, cable path, power, network, credential policy and integration requirement. The design then maps readers, controllers, locks, inputs, outputs and administrator roles to the operational workflow. Commissioning includes door-by-door functional tests, failure-mode and backup-power checks, permission and schedule tests, event verification, administrator training and as-built documentation. Product availability, subscriptions and supported integrations are confirmed for the current project before procurement.
Frequently asked questions
Questions about sizing, operating and integrating LenelS2 NetBox, from a single building to a distributed enterprise.
How is the right NetBox family determined?
By sizing, and the inputs are listed on this page: portals, nodes, concurrent operators, integrations, resilience and database partitions. Count the controlled openings and the nodes behind them, list every operator who will be signed in at the same time, and add the integrations and partitions the organization needs. That total is what separates standard NetBox from Extreme, Enterprise and virtualized deployments.
How do we choose between the NetBox appliance and the Virtual Machine option?
Sizing drives it more than preference. NetBox Extreme, Enterprise and Virtual Machine are named together as scale options, and the sizing inputs are portals, nodes, concurrent operators, integrations, resilience and database partitions. Work those numbers out with your IT group, check current LenelS2 documentation for the option you are sizing toward, and record who owns partitions, backups and failover.
What still works at the doors if the appliance is unreachable?
What continues is whatever the field hardware was specified to do, proven at commissioning rather than assumed from the platform. Operators lose browser administration in the meantime: person record edits, reporting, alarm monitoring and threat levels cannot be changed. Write the required behavior for each opening into the sequence of operations, then test it with the appliance disconnected and the results recorded.
What is tested before a NetBox system is handed over?
Door-by-door function, failure modes, backup power, permissions and schedules, followed by event verification and administrator training. On this platform the handover also walks the person record workflows and the threat level procedure the site will actually use, so operators are not learning them during an incident. As-built documentation records device names, addressing and administrator procedures without publishing credentials.
Can NetBox exchange data with our other systems?
This page lists open API integrations as a decision to document, so what is available for your project depends on the systems you name and the current license and firmware level. Bring the target systems, the direction of each data flow and the owner of each connection to the design review. Licenses, subscriptions, firmware and integrations are then confirmed for the project before procurement.
How do we keep departments from seeing each other’s cardholders?
System partitioning separates them, and database partitions are part of how the platform is sized, so the boundaries are drawn before enrollment starts. Decide which group owns each partition, which operators work inside it and who may see across, then match operator roles to that map. Moving person records between partitions later is administrative work that is easier to avoid than to redo.
LenelS2 owner, administrator and buyer resources
Discuss LenelS2 installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.
Official LenelS2 NetBox software, firmware and support
Official manufacturer resources. We link out rather than host firmware.
Before updating: confirm model, hardware revision, current version, entitlement and rollback plan, and schedule monitored or life-safety-adjacent systems with the administrator.