By SafePath Tech Solutions · Reviewed October 22, 2026
Compare the choices.
| Question | Supported Mercury-based hardware | Vendor-specific panels |
|---|---|---|
| Main appeal | Potential reuse across supported software platforms. | Defined equipment/software pairing and feature set. |
| Software choice | Confirm board support, firmware, and OEM conditions. | Confirm supported choices and documented migration options. |
| Changing platform | May retain boards, with conversion work and licenses. | May require new panels; some door equipment may remain. |
| Readers and credentials | Their compatibility and security are separate choices. | Their compatibility and security are separate choices. |
| Support | Assign responsibility across platform, equipment, and integrator. | Review support choices, lifecycle, integrations, and replacement costs. |
What Mercury brings to the choice.
Mercury supplies access controllers designed for multiple management-software partners. This can create options when replacing software. The panel is one layer alongside expansion boards, readers, credentials, locks, power, and management software. Cloud versus on-site hosting is a separate decision.
Source: Mercury access-control hardware
Verify the exact installed boards.
Request model, revision, OEM identity, firmware, support status, and written target-platform compatibility. Review authorization, conversion requirements, licenses, and manufacturer restrictions. A cabinet with Mercury boards is a useful starting point for assessment, not proof that every board or feature transfers unchanged.
Understand the vendor-specific tradeoff.
A manufacturer’s own panel architecture can provide a consistent feature set, deployment process, and support path. It may also narrow software alternatives or increase future replacement cost. Examine downstream modules, supported readers, integrations, and contracts; a proprietary panel does not automatically make every door component proprietary.
OSDP addresses another layer.
OSDP is a standard for communication between controllers and peripherals such as readers. It supports two-way communication, supervision, and Secure Channel capabilities. It does not make a controller portable between management platforms. Verify the reader/panel combination and commission Secure Channel; support on a datasheet alone is insufficient.
Source: SIA OSDP overview
Credentials can create a separate dependency.
Panel reuse does not guarantee badge or mobile-credential reuse. Review card formats, application keys, reader configuration, mobile licenses, and who can issue credentials or authorize changes. Reading only a smart card’s serial number differs from authenticating its protected application.
Cost migration door by door.
Separate retain/replace decisions for controllers, expansion boards, readers, credentials, supplies, locks, wiring, software, and integrations. Include configuration, event-history retention, commissioning, staff training, and downtime. Identify assumptions and fallback replacement costs before committing to reuse.
Keep ownership and exit terms in writing.
Record the owner administrator, board inventory, authorized recovery procedures, exports, configuration records, and handover obligations. Changing a service provider and changing a software platform are different projects. Ask what a future integrator receives and what approvals are needed.
Put these answers in the proposal.
- Exact inventory and written target-platform support
- OEM, firmware, license, and conversion requirements
- Reader protocol and Secure Channel commissioning
- Credential technology, key custody, and reissuance rights
- Door-by-door retain/replace plan and downtime
- Owner accounts, exports, records, and service transition terms
Request a supported migration assessment.
Have the provider identify the installed boards and document support for the target platform. For a larger rollout, pilot a representative opening before agreeing to reuse or replace the whole installation.
Questions worth asking.
Is Mercury open-source?
No. It is commercial hardware designed for multiple software partners. Software and licensing remain platform-specific.
Does Mercury work with every cloud platform?
No. The board, firmware, OEM conditions, and software integration must be supported.
Does OSDP make the whole system open?
No. OSDP addresses the reader/controller link. Panel/software compatibility and credential ownership are separate.
Let’s make your next security decision a confident one.
A new facility. An aging system. A challenge you need to solve. Start here.