Proudly serving and supporting
Toll-free(855) 203-6339
Request an estimate
Contact Us
×
Open-architecture controllers and door interface hardwareAUTHORIZED DEALER + INTEGRATOR

Mercury Security Access Controllers

Mercury Security supplies the open controller and interface hardware used behind many enterprise access-control software platforms. Terapixels designs the panel architecture, door capacity, secure reader communications, enclosures, power, expansion, and migration path around the selected host platform.

Mercury Security intelligent access controllers and interface modules installed in control enclosures
Mercury intelligent controllers and door interface modules
DIRECT ANSWER

What does Mercury provide for access control?

Mercury Security provides the intelligent controllers, reader interfaces, and input/output modules behind many enterprise access-control software platforms. Mercury is not usually the daily operator interface; an approved OEM host platform supplies the management software while Mercury hardware makes and executes field-level access decisions. Terapixels uses Mercury when an owner values open architecture, scalable door expansion, controller-level resilience, or a phased migration from an existing Mercury installation. Every design must coordinate host-software ownership, licensing, firmware, panel capacity, reader protocol, power, enclosures, I/O, and the actual door circuits.

Ask Terapixels about Mercury ↗
WHERE THIS PLATFORM FITS

Match the access model to every opening.

Best suited to commercial and enterprise systems that value open software choice, field-proven controller hardware, scalable door expansion, and a controlled migration from earlier Mercury generations.

CURRENT PRODUCT FAMILIES

Software, identity, controllers, and door hardware.

This project-focused overview covers representative product families and specialties. Final models, credentials, licenses, accessories, interfaces, firmware, and availability are verified during design.

NEXT-GENERATION CONTROLLERS

MP intelligent controllers

MP1501, MP1502, MP2500, and MP4502 controllers provide a current Mercury foundation with enhanced cybersecurity and an edge-capable application environment.

DOOR + ALARM EXPANSION

S4 I/O modules

MR50, MR52, MR54, MR16IN, and MR16OUT Series 4 modules expand readers, doors, monitored inputs, and relay outputs around intelligent controllers.

MIGRATION PLATFORM

LP controllers and MercOS

LP controllers remain part of the installed base, while MercOS and MP legacy modes support planned modernization and compatibility pathways.

FIELD CONNECTIVITY

Reader and interface products

Reader interfaces and related devices connect OSDP readers, credentials, locks, contacts, request-to-exit devices, and auxiliary security points.

SPECIALTY CAPABILITIES

What makes Mercury distinctive.

Open architecture

Mercury hardware is designed for use through approved OEM software partners, giving owners more platform choice than a closed controller stack.

Phased modernization

Compatibility across controller and I/O generations can help preserve supportable infrastructure while moving carefully toward newer hardware and cybersecurity capabilities.

Controller-level resilience

Access decisions, schedules, alarm functions, and event handling at the controller layer help the field system remain purposeful beyond a simple network endpoint.

DESIGN DECISIONS

What to verify before selecting Mercury.

Host platform and ownership

Identify the approved OEM software, existing controller ownership, licensing, database migration, integrations, and the organization responsible for future firmware support.

Controller generation

Inventory MP, LP, EP, MR, Series 3, Series 4, and legacy modules before deciding which hardware can remain, operate in a migration mode, or must be replaced.

Panel engineering

Calculate readers, inputs, outputs, downstream modules, network ports, power, battery standby, enclosure space, grounding, labeling, and spare capacity by location.

PLANNING OR MIGRATING?

Confirm compatibility before ordering hardware.

Terapixels can survey the doors, document existing equipment, verify the product path, and develop a complete scope for installation or migration.

Request a Mercury assessment ↗
COMMON APPLICATIONS

Commercial environments where this portfolio can fit.

SOUTHERN CALIFORNIA SERVICE

Mercury access control near you.

Terapixels assesses and engineers Mercury-based access-control systems across Southern California, including Orange, Los Angeles, San Diego, Riverside, and San Bernardino counties. Services can include panel inventories, OEM-platform migration planning, MP or S4 modernization, enclosure and power remediation, secure-reader conversion, door expansion, programming coordination, commissioning, and documentation.

Schedule an onsite door survey ↗
TERAPIXELS DELIVERY

The platform is one layer. We make the opening work.

Survey + engineer

Users, permissions, credentials, frames, doors, latching, egress, fire rating, pathways, power, network, integrations, and existing assets.

Install + commission

Cabling, readers, panels, enclosures, locking hardware, door monitoring, software, integrations, labeling, testing, and controlled cutover.

Operate + support

Administrator training, credential workflows, documentation, preventive review, troubleshooting, licensing, and lifecycle planning.

MERCURY QUESTIONS

Answers before product selection.

Is Mercury Security an access-control software platform?

Mercury primarily provides controllers, reader interfaces, and I/O hardware used by many access-control software manufacturers. The host software, Mercury firmware, controller generation, and module compatibility must be evaluated together.

What is the difference between Mercury MP and LP controllers?

MP is Mercury’s newer intelligent-controller family with updated cybersecurity, performance, and application capabilities. LP remains widely installed and is part of defined migration paths. Exact replacement and legacy-mode support depends on the host platform.

Can Terapixels reuse existing Mercury panels?

Potentially. We review model, generation, firmware, OEM ownership, licensing, enclosure condition, power, batteries, expansion modules, reader protocol, door wiring, and cybersecurity before deciding what should remain.

Which access-control software works with Mercury hardware?

Mercury hardware is embedded in multiple approved OEM access-control ecosystems. Compatibility is not determined by the board alone; the exact OEM, software version, licensing, controller firmware, database ownership, and downstream modules must all be confirmed.

Can Mercury controllers keep doors operating during a server outage?

Configured intelligent controllers can continue many local access decisions, schedules, and event functions when communication with the host is interrupted. Exact offline behavior, event storage, integrations, and recovery depend on the controller, firmware, host platform, and programmed logic.

REVIEWED · SEPTEMBER 23, 2026

Verify the current portfolio with the manufacturer.

Product names, specifications, software versions, credentials, licensing, integrations, certifications, and availability change. The page is based on current public manufacturer material; Terapixels validates final project fit and compatibility before proposal.

Ask Terapixels about product fit ↗

Authorized-dealer and trademark notice. Terapixels represents its current dealer and integration relationships for the access-control products shown here. Program status, product-line authorization, availability, and project eligibility are confirmed when a proposal is prepared. Product descriptions are original Terapixels summaries based on public manufacturer information; names, logos, imagery, and trademarks belong to their respective owners.

READY TO START?

Plan a better-connected facility with Terapixels.

Start a conversation ↗