Mercury Favorability Statistics 2023

Published Sep 21, 2023 12:21 PM

Mercury Security was acquired by HID in 2017 and is part of mega-access control manufacturer Assa Abloy. Its panels are supported by 30+ partners and widely used, but what do integrators think about Mercury in 2023?

IPVM Image

Over the past few years, Mercury and sibling HID have had significant product shortages. See our coverage, including:

For more background on the company and its controllers, see Open Access Controller Guide (Axis, HID VertX & Aero, Isonas, Mercury)

This report examines statistics and commentary from 140+ security integrators on Mercury's positioning, pros, and cons.

Net ******** ************

******* ********'* ******* **** ******** *** positive (+**%), ****** **** *** ********** *****. *******, ******* ******* *** **** Abloy's ****** ******** ************, ***** *********, and *** ******** ******* ** ******** years -***'* ************ **** **** **** *** to ****** ***** ******.

IPVM Image

********** ********* **** *** ***** ********** around ****** ***** ****** *** ******* than *** ****** ***. *** ***** who ***, **** ** **** **** that ** *** ******* ********. ****, Mercury *** ****** **** *** ****** HID ** *********** ********** ******** (*.*. "*" ******), ***** ****** ******** *********** **** the ***** **. *** ****** ***.

*******'* *** ******** ************ ******** ** nine ********** ****** ********:

IPVM Image

Strong *** ********, **** ***** ******* *** **

******* ** **** ***** ***** *********** outside *** **, *** *** ********** is ***** ** +**%:

IPVM Image

******* ** * **-***** *******.

Key ******

*** **** ****** ***** ** ***********' responses ***** ******* ******** *** ** follows:

  • ***** ******** ******** *** ****************
  • ******** *** ******
  • ******** ********
  • **** **** **********/************
  • ***, ********** ******
  • ******** ** ********** ****
  • ********/********** ********
  • *********
  • **** *****/*** ********* & *********

***** ******** ******** *** ****************

*** ******** ** *** ******** ********* were ********* *******'* ***** ******** *** interoperability:

  • "******* ***** ** ** *** "***********" of ****** *******. **'* ********* ** be **** ****** *** ****. **** have ****-*****, ******** ****** ** * look ** ** **** * "*****" centric ***** ** ****. *****'* ******* of ******* ****** *** ******* ** to **** **** ******* ********."
  • "* **** *** **** **** **** systems *** *** ******* ******. ****** is ****** ****** ** ***** ******. This **** *** ** ******* **** more ******* ******* ****** ** ******* all *** ********."
  • "* **** *** **** **** *** job **** * ******, ******* **** with *** **** ****** **-*****, **** can (**** * ****** ****) ****** out ***** ****** ******. ***** ****** to **** ************ *** **** *******."
  • "********, ********** **** **** *******. ***** not ****** *** ****, *** ******* to ***** *** ********** ** *** with ********* ******** ***** *** ******** money."
  • "**** *** **** ** ****** ******** ability. *** ****** ** ******* **** support ******* ** ****, *** **** are ***** ** ******** *** ***** when ******* ***** ****** ******."
  • "**** *** *********-***** ****** **** ****** many ****** ******* ********* ** *** and **** **** ******** ** *** original ********* ** *** ********** ******* the ******."
  • "*** **** **** *** *** **** to ****** ******** *** **** *** hardware ** * ****. **** *** even ******** ***** ********* ** ********* with ****."
  • "********, ********** **** **** *******. ***** not ****** *** ****, *** ******* to ***** *** ********** **** ********* software ***** *** ******** *****."
  • "** *** ********, **********, **, ***** works ******** ****. ** **** *** address *** **** **** ******, ** should ** ***% ** *****."
  • "**** ** ** **** ****** ** system **** **** ******* ******** **** little ** ** ********** ** ***********."
  • "******* *** **** ****** ******** **** work **** **** ********* ******** *************."
  • "** *** ***** *********** ***** *** to ***** ************* **** **** ** the ******* ** **** **** ** to."
  • "************ ********. ** *** *** ****** boards, *****/****** ******, *** *********** *** the ****."
  • "***** *** **** ******* ****, ** concerns ********* ****** ******** *** *************."
  • "***** ********. ********* ************ **** ********* all ***** ******* ** *** ****** control *****."
  • "******* ******. **** ***** ************* **** vendors ***** ******** ** ***** ********."
  • "***** ****** ******** *********. ****** *** techs ** ** **********. ********** *******."
  • "* **** *** **** **** **** are ********** **** **** ********* *******. I **** **** *** *** *** locked ** **** * ************."
  • "******** ** ******* *** ***** ****** platforms. ***** ******** ****** *** ***** terminating ******."
  • "**** ******** *** *********, **** **** several ******** *************."
  • "*********** ****** **** *** ** **** over ******** *********."
  • "*** ** **** **** ******** ****** control *************."
  • "*'** **** ** ***** ** *** past **** *******, **, *** ******."
  • "** *** ******* ****** **** ***** and ******** ****** *********."
  • "** *** **** **** **, *** they *** ******** *** *********."
  • "* **** *** **** ************ ****'* used ****** *** ********."
  • "***** ******* **** ***** ****** **** platforms."
  • "*** **-** *******. ** ***** ***** and ** *********."
  • "**** ****** ** ******** ******* ** known ******."
  • "**** ** ** **** ** **** hardware, **** ******."
  • "* ****** **** *** *********** ** their *********."
  • "**** *** **** ********* *** ***** quality."
  • "**** ** **** **** **** ********."
  • "***** ** ******* ********."
  • ***** **** **** ***** **."
  • "****, ***** ******."
  • "****** ********."
  • "**** ********."
  • "*********."

*** *********** **** **** ******** ** negative *** ******* ** **** **** partners:

  • "** ***** ***** *** **** **** their ******** **** ******* ** ****** multiple ********* *******. ****, ***** ***-*********** approach ******* ** ******** **** **** solutions ********** *** ******* ** *** user ** ******** **** **** ********."
  • "** *** **** ****, **** **** with **** ****** ** **** *** not *** **********. ** *** *** side, **** **** **** ** **** that **** **** **** ***** ********. There's ** ********* ***** *** **** in *** ******, *** **** **** never ******** **."

*** ********** **** **** ******* ******** some *******:

********* **** ** **** *** *********** of ******** **** ******** **** ****. But **** **** ******* **** ******* and ****'* ***** ** **** ****.

Reliable *** ******

**** *********** **** ************ ******* ** its ******* ********* *** ***********:

  • "******* ******** ******** **** ****** ****** for *** ******* ****** ******* ********* in *** ***********. ***** ******** **** a ***** **** ** ************* *** can ** ******* **."
  • "***** ******** *** **** ******* ** access **********, * ***** ********* ** simple *********** ** ******* *** ******. Plus, ***** **** ** *** ****** provides ********* - ****** ** **** not **** ******* ******* ** ************, opting *** *** *********** ***."
  • "* **** **** **** ** * stable ******** ********, *** ******* ********* well, *** ***** *** ******* *******."
  • "********* **** ******** ** ***** ******, and **** *** *****. **** **** to **** *** ******."
  • "**** - ***********, ******* **** ******* access ******* ******** *************."
  • "** **** ******* ******* **'* **** very ********** ***** ******** *** ********."
  • "***** ******** *** ****. ** ****** have ** ****** ***** ***********."
  • "***** ******, **** ************, *** *************, nothing *** ** ***."
  • "**'** **** ******* ****** *** * long ****, *** **** *** **** solid."
  • "** ********** ***** ***** ******** **** regards ** ***********."
  • "**** *** ******* *** **** ** extremely *** ******* ****."
  • "****** ******* **** **** ****** *** test ** ****."
  • "**** - ****** *** ********, ******* up ** ****."
  • "********* *** ******** ****** ******* *****."
  • "*** ** *** **** ****** ******* PCB ******."
  • "*** ******** ***** ** ** **** reliable."
  • "***** **** *** ******** *********."
  • "******** **** ** ** ********."
  • "*********, ******** ********."
  • "*** ******* ** ***********."
  • "***** **** *** ********."
  • "******** *******."
  • "******* ********."
  • "**** ******."

*** *********** *** ********* ********, ******** out **** **** *** *** ****** with ******* ******:

  • "*** **** ****** ********. ***** ********, recurring ****** **** **** ******, ***."
  • "*** **** *** ** * ****** notice *** * **** ** *** and ** *******."

***** *********** **** **** ******* ******** are **** ** *******:

  • "**** *******, **** ** *********."
  • "**** ** ********* *** ****."
  • "**** ** ***."

"Industry ********"

******* *********** ********* **** ******* ** the "******** ********," ********** ** ******* it's * **** ** *** *****:

  • "**** ****** *** ******** *** ****** controllers *** * *****-**** ********."
  • "**** *** *** ******** ******** *** door *********** *** ****** ******* **** there ****'* ****** ***** ******."
  • "* **** *** **** ******** ********, but **** *** *** ********."
  • "*** ******** *** **** ** ******** standard *** *****."
  • "***** *******, ***** **** ******* ******. Set *** ******."
  • "****-**** ******, ******** ** * ********."
  • "*** ****** *** *****-***** ********."
  • "* ***** *** ** ** *** standard."
  • "******** **** ******* ******..."
  • "*** *** '**** ********.'"

*** *********** ********* **** ****** *** just ******** **** *** *****:

  • "**’* *** ***** **’** **** ******** with."
  • "*********** **** ** **** ****."

Lead **** **********/************

***** ***** *** ***** ********** ********** about *******'* **** **** ****** **** its ****** ***'*, ******* ***** ******* up *** *******:

  • "*** ******* ***** ****** ******* ****** seem ** **** **** **** **** times, ****** **** ****-************ *******. ********** of *** *******, ** *****'* **** for * **** ************ **** * client **** ***** ****** ************ *** be ******* ** *-** ****** *** to **** ** *** ************."
  • "*** '*** ******' ** ******* *** been ******** *** ** *** *** customers. **** ** ********* **** ******* until **** **** ********* ** ********** to ****** *** ** ** ******."
  • "******* ***** ** *** ***** ************* and ************ ***** ********, ** **** will ******** ** **** ****** ***** and ******** ***** ** ***** *****."
  • "** *****. ********** *** / **** some ************ ******."
  • "*** ******* ** *** **** **** is *** ************ ** ***** ***********."
  • "**** **** ***** **** ***** *** a ***** ***."
  • "******* *** * *** ** ****** chain ******."
  • "******* - ****** ***** ******."
  • "**** ** ***, *** ***** *******."

*******, ****** ********* **** *** **** time ***** *** ****** **** **** resolved:

  • "*******, ***** **** ***** **** **** better **** ******. *******, **** ***** seem ** ***** *** ****** *** industry ****** *** *** ** *** manufacturers."
  • "****** ***** ********* *** * *** problem ***** ***** ** **** **** resolved."
  • "*** **** **** ******** *** *** extended **** *****, *** **** *** been ********."
  • "*** ****** **** **** ****** ***** issues ***** **** ***** ********."
  • "******* ******** ** *** **** *** chip *** ****** ***** ******."
  • "**** *** ******* ******** **** ********* again."
  • "****** ***** ****** *** ** *** past."

********* - ***, ********** ******

**** *********** **** **** **** ***** Mercury ***** **** **********:

  • "**** ** ****** *** ******* ****. Need *** **** ******* *****. **** to ******* ***** */* ********** ***** connected ****** ******* * ****** ******. I'm **** ***** *** ***** ***** software ********* ***** *** ***, *** that's **** * *** **** ** installer's ****. ******-**** ***** **** ****** to ** **** ******* ** ******** and **** * ***** ***** ********** two-door **** **** ** ****** ****** than * **** ***-**** ****** **********."
  • "* **** ***** **** **** ** improve ***** **** **** ********** ******** with ***** ******** *********."
  • "* **** *** ******* ******* ************, but ** *** **** ****, * feel **** *** **** ** ******** and ****** *** ********."
  • "*** ** *** *** ******* ********* for ***********, *** ***** ** ******* innovation *** **** ** ****** *************."
  • "*** ******* ***** *** **** ****** for * **** ****. * ********* it **** ***** *******."
  • "** ***** ** **** ** *** more ********** *** ** ****."
  • "*** **** ****** ** ******* *****."
  • "**** ** ********."

Controller **** **********

******* *********** ******* *** *** *******'* boards **** ** *** **** ***** and *** **** ****** **** ***********':

  • "***'* **** *** **** ****** ** several ******, *** ***, **** ** too **** **** ******, ********* ** a **** *** ****** ********, **** customer ***** ********, **** ******** ** install. ******, ******, ***. ***** *** a ******** ** ****** ***** ***** by **%, ***** *** ************** **** the ******."
  • "** *** ********, **** **** ** a *** ** **** ****** ** a ****, *** *********, ****'** ****** their ****** ***** ****** **** **** devastating."
  • "*** **** ***** ******** ** *** size ** *** ******. **** *** rather ***** *** **** ******* ****** enclosures."
  • "**** **** ***** ****** ***** ********* to **** * * ** * reader ***** ******** **** ****** **."
  • "**** ** ******* ** *** **** of *** ****** *** ***** ******** to ******* ****."

********/********** ********

*** *********** ******* *** ***** ******** about *** ******** ** ********** ***** too ********* ** *******:

  • "** *** **** ****** ******* ******** and *** ** ****** ******** ******** solutions. *** ****** ***** ****** **** have **** ************ ******** **** ***** us *****, *******. ** ******* ** were *** ********* ** ****."
  • "*** ****** ***** ****** **** *********, however. ** ****** * ********* ** the ********'* ********** ** *** ********, which ***** ** ***."

*********

******* *********** **** **** ******* ******** are *********:

  • "******* ** *****, ********* **** ********* than *** ************'* *********** ******."
  • "******* ** ****. * ***'* **** with **** *****, *** * **** in *** ****."
  • "*** **** ******** ** ***** * steep ***** **** ********* **** ***** products."
  • "*******: * *** ********* *** ******* projects."
  • "*********, ******."

**** *****/*** ********* & *********

*** ********** *** ******** ***** *******'* relationship **** **** *****:

**** ********* ** **** *****, ** should ****** * ****** ** * short ****, ** ******** ** ********* its ******, ****** **** **** ******, small, ********* *** **** ************* *****.

*** *********** **** ******* ***** **** of *** *** **** ***** **********:

  • "* ** ********* **** **** **** them, *** ***** **** ** ********* a **** *****, ***** ** * downside ** ***** **** ** * large ***********."
  • "*** ** **** ** ****** *** did ******** *** ******* ******** ********* as **** ******. *** ****'* ******* this *** ***** **** ****."
Comments (3)
U
Undisclosed #1
Sep 22, 2023

*** ******* ***** **** ******** ** is **** ******* **** ********. ** what ***** **** **** ** ** competitor. * **** *** **** *******, even ****** ***** ********.

UE
Undisclosed End User #2
Mar 14, 2024

****/*** **** ** ********, * ******'* worry ***** **** ********* ** *** application *****

PH
Paul H Aube
Sep 26, 2023
Consultant PHA

* ****** *** ******** *******. ******* is * **** ******** *** *****-****** facilities, *** ** *** *-* ******(*) or ***** ********* ******, *** ** unit **** ** ******* *** ********** accessories.