Paxton Net2 Access Control
Managing doors, users, schedules, events and integrations from one place is what Net2 does: Paxton's networked access-control platform, run from a Windows-based system.
Sites where Net2 makes sense
Net2 is a practical choice when access control is the primary requirement, a local Windows management environment is acceptable and the security engagement benefits from Paxton's established controller and integration ecosystem.
Software, controllers and readers in Net2
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 needs to 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 needs to be surveyed for frame condition, egress hardware, handing, accessibility and available pathways before a bill of materials is finalized.
- Server and client software for Net2
- Door controllers and I/O modules, networked
- Readers and credentials, Paxton or compatible
- Hardware for locking, power, sensing and egress
Choosing between Net2 and Paxton10
Net2 and Paxton10 needs to 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 security engagement that requires tightly unified Paxton video may favor Paxton10, while a security engagement centered on access control and existing Net2 infrastructure may favor Net2.
A migration decision needs to 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.
- Preferred way to manage and host
- Condition of the Net2 equipment already owned
- Whether Paxton video must be unified
- Cost, disruption and training for a migration
| 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 |
Wireless locks, visitor entry and integrations
Net2 can exchange information with approved third-party integrations and can coordinate access events with Entry and other building systems. Integration requirements needs to 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 preventive maintenance tasks. Entry adds video calling and door release; panel location, lighting, accessibility, call routing, concierge functions and after-hours handling needs to be system engineeringed as part of the entrance workflow.
- Approved integrations and how data flows
- PaxLock suitability and battery-preventive maintenance plan
- Entry panel, monitor and call-routing system engineering
- Testing failures and how operators respond
Lifecycle and support engineering assessment
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 preventive maintenance window.
Regular service needs to include database backup verification, controller communication review, power and battery inspection, door-hardware testing, alarm-event review and credential cleanup. The client needs to know which issues belong to access-control software, the network, the door hardware or another integrated system.
- Inventory of versions and hardware
- Backing up and restoring the database
- Scheduled review of software and firmware
- Health checks on doors, power and communications
How the work is planned and carried out
The final system engineering depends on site conditions, existing systems, client policies and the selected manufacturer or platform.
Survey
Record every opening, controller, reader, credential, software item and network condition.
Compare
Weigh keeping, expanding or migrating against operational needs.
Implement
Doors, software, integrations and event workflows get installed and tested.
Maintain
Hand over records of backups, versions, support resources and repeat health checks.
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.
- Which Net2 software version runs, and on what server
- What controllers, readers and credentials exist
- Door hardware and the power it needs
- Requirements for Entry, PaxLock and outside integrations
- Constraints on expansion, migration and service windows
Questions about Net2
These are common engineering assessment questions. A site-specific answer needs to be confirmed during discovery and system engineering.
Does Paxton10 mean the end of Net2?
Paxton continues to present Net2 and Paxton10 as separate systems. Selection needs to be based on security engagement requirements and the installed environment.
Does Paxton Entry pair with Net2?
Yes. Paxton Entry can be integrated with Net2, with the required Entry and Net2 components selected for the system engineering.
Will the readers already installed carry over?
Sometimes. It turns on the target controller platform, the reader protocol and credential technology, plus wiring and condition.
Is an installer’s website the right place to get firmware?
No. Going to Paxton’s own product and support resources keeps the file, the documentation and the compatibility guidance coming from the manufacturer.
Software, firmware and technical files live on the manufacturer’s official website and are downloaded from there. No firmware is mirrored on this site.
Discuss a commercial 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.
Paxton owner, administrator and buyer resources
Use these parent-company Paxton guides to research current Net2, Paxton10, Solo, Entry and PaxLock requirements before Georgia survey and implementation.
Discuss Paxton installation, upgrade or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.