Brivo Opens Up, Adds Mercury Support

By Brian Karas, Published Mar 16, 2017, 09:56am EDT

Brivo's cloud-based access control was built around the companies proprietary hardware controllers, and was often seen as a limitation by customers. Now, the company has shifted strategy, by embracing hardware from perhaps the most well-known open platform access control company, Mercury Security.

IPVM spoke with Brivo CEO Steven Van Till [link no longer available] about their decision to embrace open hardware and what this means for Brivo's own hardware line. 

In this report we share details of the conversation and analysis of this move.

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

***** ********* ******** ******* *** Mercury ********** ***** *****-****** ********, with ************ *********** ** September ****. ********* ** the *******, *** ******* hardware **** ******* *** same **** ************* ** Brivo's *** *********** ********, but **** ***** ********* more ****** *********** ** the ****** ** ******* ******** Mercury-based ****** ******* ******* to *****'* ********.

Consultants ******* ****** *******

***** **** **** *** security *********** ******** **** supportive ** *****-***** ****** control *******, *** ** the **** ****, **** supportive ** ****** ******* in *******. ******* ********* into * ******* ** a ********** ** *********** a ********** **** *** a ************, *** **** competitors ***** **** ********, such ** ******* **** ********, ******** ** ***** ***** for ***** ** **** this **** ** *********** consultants,  ****** ***** ****** position.

Integrators **** ***** ******** ** *******

*********** **** ***** **** while **** *** ** opportunity *** *****'* ***** system, **** ********* ** reduce *** ****** ** controllers **** *********** ****** to ******** ******** **. Brivo said **** *** ****** to *** ******* ******** was *** ** *** top ********* ******** ***** from ***********, *** *** difficult ** ******* **** earlier ******** **** *** less *******-*******.

Proprietary *** ****

*****'* *** **** **** the ******* ***** ** maintain *** ******* **** of *********** ******** ******, and *** ** ***** ** discontinue ****. *** ******* is ********** ** ****** development ******* ** ***** products *** ********* ****** expect ******* ** *****'* own ********.

No ***** *** *** ** ***** ********

***** ***** *** ** specific ***** ** ******* other ******** ******* ****** Mercury, ***** **** **** **** have *** ***** *** the ***********. *** ******* of *** ******* ***********, and ******** **** *********, will ********* ***** ******, if ***, ***** **** ******* for ****. 

Utilizes ******* "**** ****" ********

********* *** **** ** use ******* ********, ** convert ******** *******-***** ******* to *****'* ********, ****** be **** ** ** so ******* *** **** for ********** ******** ** specialized ********, ********* ** Brivo. *******-******* ******* *********** have ********* * "**** home" ******* *** ******* years, ***** ***** **** can ** ******** ** connect *** ********** ** Brivo's ***** ****** ******* the **** *** *** Brivo-specific ****** ********. 

New ******** **** ** ****** ******

**** **** ** **** about ****** *********** *** consultants ******* ******* ** install ***** ** *** locations **. **** **** existing *******, ********* *** CEO. ***** ****** ********* are ********, *** ******* says **** *** *** their ******* ********** *** adding ******* ******** *******.

Price **********

********* ** *****, ******* for * ****** ***** Brivo ******** ** ******* hardware ****** "**** ** minus **%" *** * comparable ****** *****, *******, etc. *** ******** ************ price ** **** *** either ********.

Good **** *** *****

***** ***** ******* ******** theoretically ***** ********* *** ability ** ****** **** Brivo ** ***** ****** control *********, **** **** signals *****'* ********** ** their ********, *** ********** the ****** *** *********** to ***** **** ** a ****** ** *********** product. ************, ***** *** take ********* ** *********** Mercury cards, **** ** ***** ***** [link ** ****** *********] *** ****** [**** ** ****** available] cards, **** ******* ******* uncommon ************** (**: ******** *******) that ** **** *********, or ***********, **** **** with *****'* *** ********.

 

Comments (2)

This reminds me of when mobotix decided to support H.264. Long overdue decision that makes sense.

Nice article!

 

Read this IPVM report for free.

This article is part of IPVM's 6,649 reports, 895 tests and is only available to members. To get a one-time preview of our work, enter your work email to access the full article.

Already a member? Login here | Join now
Loading Related Reports