How Does Krika Compare to Enterprise Grade Remote Supervision Systems?

This is a question that we occasionally face, especially when discussing our solution with businesses who operate in the corporate, commercial, and enterprise markets. IT people in charge here will typically claim “We can do this already using tools such as Nagios, PRTG, Zabbix or Zenoss”. Let's take a closer look at Krika compares to these tools, and where it might make sense to use one versus the other...

First we need to define the two different categories of products that we want to supervise: 1/ Network Infrastructure - Here we are talking about switches, network interfaces, routers, ISP connections, WiFi Access Points, and the data flowing through these products. This might look common to the residential market, but typically the corporate / commercial / enterprise markets use different brands, as well as a broader range of products and ISP's. 2/ The Endpoints - Here we are talking about the devices connected to the network. This is where the big difference lies. Except for devices such as phones, laptops, tablets, printers, etc we have almost no endpoints in common between the two industries. Properly supervising a device requires a deep understanding of what it's doing, its communication protocol, its API, etc. In the residential industry we want to know if our Integra receiver's Zone 2 is powered “On”. While in an enterprise we want to know if the mail service is “started”, or the load average of an SQL server.

Even if it seems like we are essentially doing the same thing there are clearly fundamental differences in the types of devices we supervise. Therefore it makes sense that specialized tools are developed to meet the respective segment needs. Moreover, there are important differences to consider when it comes to the people using these tools. Let's be honest, when it comes to network infrastructure and remote supervision home technologists can learn a lot from the folks in enterprise IT. Systems administrators tend to be very familiar with using line command prompts, and programming is part of their DNA. They are very good at customizing their supervision tools, and highly efficient at using them. But in the end these enterprise tools are not user-friendly enough for most residential technicians to operate.

I'll concede that with patience and determination any IT guy could program Nagios to supervise a C4 processor, but what a waste of time! Does he even know what a C4 processor is, and that's it's possible to parse and display the battery level of all its connected Zigbee Remote control? This brings to light Krika's big advantage. You can deploy Krika, which is pre-programmed to work with almost all residential products, for 1/10th the price a Nagios engineer would cost you.

Sure, if you had a massive residential job with money to burn, you could hire an IT company to deploy a solution like Nagios. They'd be up and running in minutes, ready to monitor the home's network infrastructure because that's what Nagios is built to do. But they'd spend months learning, and programming to, the protocols and various nuances of the specific residential equipment. Clearly this would not makes business sense. Krika, on the other hand, comes out of the box ready to work, making it much more profitable, and in the end it's all about profitability.

Clearly Krika fits into a market niche that enterprise do not. Not just for in-home applications, consider as well the thousands of small IT companies serving segments of the market that look a lot like residential. Here a product like Nagios or PRTG may not be profitable to install where Krika will be. This is because the network infrastructure more closely resembles that of a residential install than an enterprise one. Think about sports bars and various shops with TV's and digital displays for example. Here we see that, even outside of the home, Krika fills a market void due to its cost effective budget and ease-of-use.

Both the enterprise and residential are important market segments, each with their own set of nuances and user-needs. In the end it's easy to see that Krika plays a vital role in many installations where an enterprise-focused solution may not make sense.