A door-entry platform with standard, touch and vandal-resistant panels, indoor monitors and an optional mobile answering workflow.

Entry system components
| Component | Options to evaluate | Planning impact |
|---|---|---|
| Entrance panel | Standard, touch and vandal-resistant (VR) panel families | User directory, accessibility, abuse risk, weather exposure and mounting determine the choice. |
| Mounting accessories | Flush, surface and rain-hood arrangements where available | Wall construction, sealing, camera view and finished appearance must be coordinated. |
| Indoor station | Audio/video monitors with handset or hands-free configurations and wall/desk options | Reception, tenant and after-hours workflows determine quantity and placement. |
| Door control | Entry control unit and associated lock/door inputs | Lock power, release, monitoring and life-safety behavior are engineered together. |
| Mobile answering | Entry app for compatible phone/tablet answering and access release | Paxton states internet service and a monthly user license are required. |
Standalone or integrated operation
Paxton Entry can operate as a dedicated door-entry system and can also be designed alongside Net2. Paxton also lists Entry compatibility within the Paxton10 ecosystem. The correct architecture depends on whether reception only needs visitor call/release, or whether the same entrance should share credentials, events and wider security workflows.
Panel choices



Information we collect before design
- Number of entrances, users, tenants and call destinations
- Reception, after-hours and failover workflow
- Visitor directory and privacy requirements
- Panel mounting, weather and vandal exposure
- Camera field of view, lighting and accessibility
- Existing lock, door contact and egress hardware
- Network, internet and mobile-app policy
- Net2 or Paxton10 integration requirement
Manufacturer references
Product capabilities and compatibility were checked against Paxton’s official U.S. materials. Specifications, availability and software support can change; Boston High Tech confirms the current design before procurement.
Explore the Paxton product family
Plan a Paxton system around your doors—not a generic parts list
Boston High Tech surveys the openings, network, power, life-safety interfaces, credential population and operating workflow before finalizing equipment. We serve projects from our Charlotte headquarters and local client offices serving Massachusetts, New York and New Jersey. Visits are by appointment so the appropriate specialist is available.
How to compare and specify this product family
For Paxton Entry Video Intercom, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following video-surveillance system decisions before equipment is ordered:
- Scene purpose and required pixels on target
- Lens, mounting height, WDR, IR and low-light needs
- Analytics supported by the selected camera and VMS
- Bandwidth, PoE and network segmentation
- Retention, storage throughput and export workflow
- User roles, cybersecurity, health monitoring and support
Installation, testing and handoff
Design starts with the evidence or operational result required at each scene—not megapixels alone. We document fields of view, identification targets, lighting, camera placement, network load, recording profiles and retention assumptions. Commissioning covers focus, exposure, time synchronization, analytics calibration, user permissions, mobile or remote access, export testing and health alerts. Final documentation records device names, locations, addressing, retention settings and administrator procedures without publishing private credentials.
Boston High Tech supports projects from its Charlotte headquarters and local client offices serving Massachusetts, New York and New Jersey.
Official Paxton software, firmware and support
Use the manufacturer links below for current software, firmware, release notes, manuals and technical resources. Boston High Tech links directly to official manufacturer portals and does not copy or host firmware files.
Before installing an update: verify the exact model, region, hardware revision, current version, required intermediate releases, licensing or support entitlement, backup and rollback plan, integrations and maintenance window. An incorrect firmware package or upgrade sequence can interrupt service, invalidate compatibility or prevent a downgrade. Coordinate updates for monitored, life-safety-adjacent or business-critical systems with the system administrator and an authorized specialist.
Some resources require a customer, dealer, certified-technician or active-support login. Cloud-managed products may update automatically and may not provide a public firmware file.
