Paxton Net2 Access Control
Net2 is Paxton's networked access-control platform for centrally managing users, doors, schedules, events and integrations from a Windows-based system.
Where Net2 fits best
Net2 is a practical choice when access control is the primary requirement, a local Windows management environment is acceptable and the site program benefits from Paxton's established controller and integration ecosystem.
Net2 software, controllers and readers
The Net2 server and software provide the central database for people, credentials, access levels, schedules, events and reports. Net2 controllers make door decisions and supervise opening hardware. Reader selection determines credential compatibility and may affect a future migration, so the credential technology must be documented instead of described only as “proximity.”
The physical door remains a coordinated assembly. The controller must be matched to lock current, power supply, door contact, request-to-exit method, fire-alarm release behavior and any local annunciation. Existing doors must be surveyed for frame condition, egress hardware, handing, accessibility and available pathways before a bill of materials is finalized.
- Net2 server and client software
- Networked door controllers and I/O modules
- Paxton or compatible readers and credentials
- Lock, power, sensing and egress hardware
Net2 versus Paxton10
Net2 and Paxton10 must be compared by operating needs, not by assuming one is universally newer or better. Net2 focuses on established networked access control and a Windows software environment. Paxton10 combines access and video in a browser-based platform and uses a different controller backbone. A site program that requires tightly unified Paxton video may favor Paxton10, while a site program centered on access control and existing Net2 infrastructure may favor Net2.
A migration decision must account for controller compatibility, reader reuse, credentials, database conversion, Entry components, wireless locks, integrations, training and downtime. A staged migration may be appropriate, but two platforms can also create extra administrative work if the division of sites and responsibilities is not clear.
- Management and hosting preference
- Existing Net2 investment and component condition
- Need for unified Paxton video
- Migration cost, disruption and training
| Area | Net2 | Paxton10 |
|---|---|---|
| Primary model | Networked access control | Unified access control and video management |
| Management environment | Windows-based Net2 software | Browser-based Paxton10 environment |
| Controller backbone | Net2 controllers | Paxton10 controllers |
| Best decision method | Match existing investment and access requirements | Match unified video, remote and multi-site requirements |
Integrations, wireless doors and visitor entry
Net2 can exchange information with approved third-party integrations and can coordinate access events with Entry and other building systems. Integration requirements must be written as testable outcomes: which event moves between systems, how quickly it appears, who owns the interface and what happens during a communication failure.
Wireless locks can reduce pathway and door-modification work on appropriate interior openings, but they introduce batteries, radio coverage and different scheduled maintenance tasks. Entry adds video calling and door release; panel location, lighting, accessibility, call routing, concierge functions and after-hours handling must be deployment designed as part of the entrance workflow.
- Approved integration and data-flow review
- PaxLock suitability and battery-scheduled maintenance plan
- Entry panel, monitor and call-routing deployment design
- Failure-mode and operator-response testing
Lifecycle and support deployment planning
Document the installed Net2 software version, controller models, reader technologies, license or edition information, backup location and administrator ownership. Before an upgrade, review release guidance and compatibility through Paxton’s official resources. Do not apply firmware simply because a newer file exists; confirm the reason, dependencies, rollback plan and scheduled maintenance window.
Regular service must include database backup verification, controller communication review, power and battery inspection, door-hardware testing, alarm-event review and credential cleanup. The client must know which issues belong to access-control software, the network, the door hardware or another integrated system.
- Version and hardware inventory
- Database backup and restore procedure
- Planned software and firmware review
- Door, power and communication health checks
How we plan and deliver the work
The final deployment design depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Survey
Inventory openings, controllers, readers, credentials, software and network conditions.
Compare
Evaluate retention, expansion or migration against operational requirements.
Implement
Install and test doors, software, integrations and event workflows.
Maintain
Document backups, versions, support resources and recurring health checks.
Information to gather before deployment design
Good decisions are easier when the site program team starts with complete operational and technical information. The following items help reduce assumptions, change orders and avoidable return visits.
- Existing Net2 software version and server details
- Controller, reader and credential inventory
- Door hardware and power requirements
- Entry, PaxLock and third-party integration needs
- Expansion, migration and service-window constraints
Frequently asked questions
These are common deployment planning questions. A site-specific answer must be confirmed during discovery and deployment design.
Is Net2 being replaced by Paxton10?
Paxton continues to present Net2 and Paxton10 as separate systems. Selection must be based on site program requirements and the installed environment.
Can Net2 work with Paxton Entry?
Yes. Paxton Entry can be integrated with Net2, with the required Entry and Net2 components selected for the deployment design.
Can existing readers always be reused?
Not always. Reuse depends on reader protocol, credential technology, wiring, condition and the target controller platform.
Should firmware files be downloaded from an installer website?
No. Use Paxton’s official product and support resources so that the file, documentation and compatibility guidance come from the manufacturer.
Manufacturer software, firmware and technical files remain on the manufacturer’s official website. We do not mirror firmware files locally.
Discuss a commercial security site program
Tell us about the doors, buildings, users, existing equipment, operational requirements and desired completion date. We will help organize the right discovery and deployment design conversation.
Paxton owner, administrator and buyer resources
Georgia and Southeast clients can prepare Paxton software upgrades, new installations and service scopes with these centrally maintained technical guides.
Discuss Paxton installation, upgrade or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.