We just raised a $30M Series A: Read our story

EverestIMS Reviews

Maharajan S
CISO / Associate Vice President - IT Infrastructure at a pharma/biotech company with 501-1,000 employees
Real User
Top 5
Provides data accuracy for availability and policy harmonization

Pros and Cons

  • "Our response time is within 30 minutes for any support. This solution provides alerts immediately, so we are within our SLA, giving efficiency to our support."
  • "This solution is available in SaaS. The reason why we have not gone to SaaS is they do not have a country-specific separation of assets. There are GDPR and other requirements that might require country-specific sensitive information to be filtered as well as other things that need to be taken care of. Normally, if we need to do any compliance, like ISO27000 compliance, they don't have such a report within their system. This kind of report is missing from their SaaS. That is one of the reasons that we have gone to the on-prem version, where I am assured that my data is secure."

What is our primary use case?

We are geographically spread across 11 countries. At each location, we have a firewall and other critical IT infrastructure. We have to log in to all the systems and different URLs, so we are very dependent on some individuals who have the knowledge, control, or access. Moving to this system, I have a single portal where I can access all 10 locations' firewalls from that portal with easy manageability.

We are in the life sciences domain with a lot of customer-hosting apps in our AWS cloud. We deployed this monitoring system in our on-premises environment to monitor all the critical IT infrastructure.

We are using the latest version.

How has it helped my organization?

We use the solution to automatically trigger processes to help to resolve issues when the solution detects compliance violations. While they don't have a report, this feature is in our environment. For example, our system is ISO27000, but it can miss this, instead our system goes through the on-premises process. We have segregation of duty, data storage, and the level of data encryption as well as how the server is being protected from the onset. We took all these things and kept them since it is under our validated environment. Any system implemented with us has to follow through this process. We can confidently say that our system is there, but the moment we move to SaaS or hybrid, we won't have control because they don't provide this. So, they need to build in this sort of solution for SaaS or hybrid. 

I have a Moscow office. In Moscow, I don't have an IT engineer. We have a very small team in a satellite office. We can easily manage the firewall, servers, and other things from here. When we are operating a central kind of implementation for any new initiatives, that is a big challenge for us. However, by implementing this monitoring tool, I can write any policies or procedures centrally. The process is harmonized so I don't need to worry about whether these policies play well with a particular Germany or Moscow firewall. This is more like a control mechanism. We could see the responses after implementing this tool.

Manual or time-consuming activities have been reduced by implementing this solution. Getting this information from each site takes a lot of time. Sometimes we get the wrong updates where the accuracy is not intact. By implementing a centralized tool that manages availability and the health situation of far away systems, this was ideal rather than doing it manually. Though, it was a learning curve for us.

What is most valuable?

The most important part is the real-time network monitoring dashboard. It pops up when you log into the system so it gives you clear-cut, real-time availability of the firewall/gateway-level infrastructures.

My network team, the server team, and I have different dashboards. There is also a complaints manager who has different access. These different dashboards are important because we are in the life sciences domain, and segregation of duty is very important.

The role-based dashboards summarize data points as well as provide charts and topology diagrams in a single window. We support all other regions from India. Therefore, it is better that the dashboard is a single point of entry to each site, managing those infrastructures. 

The dashboards tell us the details. For example, even in the firewall, I can go to the port level. Then, on the port level, I can deep dive on the configuration. It will also go into the level of services, memory, CPU, and storage availability. From the dashboard, you can look at that specific infrastructure or asset.

The graphical user interface is very good. It is readable, which doesn't need a technical expert to do that. That is critical. You don't need a network administrator or some other administrator to see the monitoring or anything else. Non-technical people can log in and understand it. 

Infraon's individual tunnel monitoring capabilities are more critical on the firewall side because we have a lot of Point-to-Point Tunnels created. The tunnel usage is more critical when you have a ransomware attack or any other attack has happened. When I implement a policy for a particular configuration, it will apply to all the tunnels. That makes easy for us to manage or maintain. This is a very important feature.

What needs improvement?

The reporting capabilities are a challenge and could be improved. We have been trying to connect to it from our help desk ticketing system, because the ticketing system manages asset tracking, which has been a bit challenging for us. Otherwise, they give some reports that are okay, but we do not use them much because we work in the dashboard. 

This solution is available in SaaS. The reason why we have not gone to SaaS is they do not have a country-specific separation of assets. There are GDPR and other requirements that might require country-specific sensitive information to be filtered as well as other things that need to be taken care of. Normally, if we need to do any compliance, like ISO27000 compliance, they don't have such a report within their system. This kind of report is missing from their SaaS. That is one of the reasons that we have gone to the on-prem version, where I am assured that my data is secure. I can take the report and show it to them from a compliance point of view. However, the moment we go to a SaaS model, I don't have control of the data and where the data is stored. I don't receive any complaints-based reports from the SaaS model.

For how long have I used the solution?

We have been using this solution for four to five months, including the implementation and PoC. We did the PoC in November 2020.

What do I think about the stability of the solution?

It is stable. We have never had an issue.

What do I think about the scalability of the solution?

Since it is on-prem, storage and our virtual environment are within our control. There has been no issue in terms of scaling up with the system. The scalability is good.

We have five to six people working in the system for different purposes. I log into the system based purely on availability, systems' health statuses, and other things. At the same time, a network engineer will have much more involvement than that. 

Within our system, we have around a 34-member team. Out of those 34 members there are only five or six people using this system because I don't want to give everybody a login with access to it. Since we centralize the management of the system, there are only a few people who have access. We built it in such a way that we manage it with limited resources.

How are customer service and technical support?

The technical support is good. They are very aggressive. They understand that requirements are very important. 

Which solution did I use previously and why did I switch?

Earlier, we were using Zabbix, which is open source. We had a lot of challenges with it. We had to build a distributed Zabbix environment, giving it a different kind of report. We were set up on that. While the product was very good, we were not capable of properly implementing it. 

Infraon IMS reads firewall logs, which is an important reason why we chose this product. There were other products where we had an issue reading the logs of firewalls and other things. Most of the tools provide an SNMP log, but we can reach syslog and other firewall logs with this solution. The best part: Our policies can be driven from this system and applied to multiple firewalls. For example, I am writing a rule for some URLs or specific sites to be blocked. I can then write one single policy which can be pushed to all 10 different locations. Earlier, we used to log into each system and do this process. Now, the system takes care to push these common policies.

This tool was introduced by one of our vendors. Through them, we got to know this tool and engage with it. 

How was the initial setup?

We built a PoC where we provide all this information. That PoC was running in 30 days. Effectively, once the PoC was complete, we upgraded the system to production. That is how it happened. So, the implementation was very smooth. 

We started with a PoC for around 20 assets. This takes a day or two, but it took a lot of time to understand the configuration and make changes. That took a couple of weeks because we were not familiar with their dashboard and they were not familiar with our life sciences domain requirements and regulatory requirements. That was the challenge. Once they understood our requirements, the configuration part was more like a day-to-day job.

What about the implementation team?

The team is very eager and aggressive on this. Priya put a lot of effort into the system. She provided more clarity on how to implement it. She also understood our requirements. Any tool implementation is successful based on the people who were involved and how well they understand the customer requirements and implementation. In this case, the vendor's team was good. 

Maximum two to three major players were involved from our end, maybe someone from network admin and another person on the server side. They were directly involved, but there were a few other people, like the site engineers, who contributed but weren't directly involved.

For setup and training, we only ever worked with the Everest team.

What was our ROI?

It gives us a lot of time savings. 60% to 70% of our time has been saved.

We are able to see the availability. Before people know that the infrastructure is down, we are able to get this information from the system. That is critical as far as infrastructure operations. This solution provides cost savings and is effective.

Our response time is within 30 minutes for any support. This solution provides alerts immediately, so we are within our SLA, giving efficiency to our support.

It improved our data and availability accuracy over doing the work manually. Once we installed this central system, our site engineers who provide the data started believing in the data's accuracy.

What's my experience with pricing, setup cost, and licensing?

The cost model is within our budget. I have less than 180 critical assets, but the moment that I have 1,000 assets, then the license model is totally different. I don't know whether they are capable of handling that kind of a load. They could revisit the licensing model. They are not mature enough to define this license. We had a discussion about that. 

They have given us different services as a separate license, but the cost is not there proportionally against those services. The cost was one number, but the number of services were specific to the license. For example, for server licenses, they have X quantity, and network licenses also have X quantity, but they cumulate the cost and then provide it. They don't provide the unit cost. Normally, when you work in costing, you should have some kind of clarity about standard, professional, or enterprise kinds of models, or go with a unit-based license. So, we redid our licensing cost and they provided it. So, they should work on their licensing model.

Which other solutions did I evaluate?

We evaluated ManageEngine and this solution. After doing the PoC for Infraon IMS, we were happy with it so we ended up implementing it. We didn't go with other tools because of cost and the support from the bigger players is limited. We got burned with an implementation of a bigger player previously and were not keen on going that way.

Normally, you have a product for different sectors. For example, network management will have a separate tool from server management. Here, it is a mixture of these tools in one system. Additionally, you can do vulnerability and penetration testing from this associated product. You can do network auditing, vulnerability assessment, and penetration tests on a particular critical infrastructure. Plus, you can do monitoring. I didn't see many tools that had this combination of services. There are many enterprise tools available, but we cannot afford those. This solution was something that we could afford and achieve what we really required.

What other advice do I have?

I would recommend this tool for people who want to have data accuracy in terms of availability and policy harmonization. They should look for this tool.

We are very good at integrating it with third-party applications, like AWS and other information security platforms. For our SOC, we build using some other tools, like Acunetix as SAS programming. We have integrated all these things.

I haven't seen any workflow automations.

We plan to increase our licenses going forward. However, Everest is a small company, and that has risks. I don't know their five- or 10-year plan. They need a proper roadmap for customer support, engagement, etc.

I would rate this solution as an eight out of 10. The licensing model, the compliance report, and integration of other tools are little challenges that we have with the tool. Though, we are happy with the tool. Aside from that, our requirements have been fulfilled. 

Which deployment model are you using for this solution?

On-premises
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
AashishGiri
Chief Technology Officer at Leads Innovation
Reseller
Top 10
Gives us a single, consolidated view of our system, network, and ITSM requirements, while helping us achieve ISO certification targets

Pros and Cons

  • "The role-based dashboards provide data points and charts and topology diagrams in a single window. It's like a spider web, where the application, connectivity, and everything is defined for each user of those applications."
  • "I would like to see an integrated view of Infraon IMS and Infraon Desk. It would be very helpful if that were integrated into the solution."

What is our primary use case?

We have been using it to monitor our data center services, including servers, storage, and all our security appliances. We have a 24/7 NOC operating at our data center and they have been using Infraon IMS extensively for network and data center monitoring.

We also are using Everest Infraon Desk to manage our assets, our incident management system, and our ticketing system, and it's helping us to achieve our ITSM rules.

It's on our own private cloud.

How has it helped my organization?

We were using a lot of open source products to manage our ITSM. We didn't have asset management. We needed to have a network monitoring solution and we needed to have a system monitoring solution. We were using a lot of tools in our data center. That meant that our NOC and system guys had to maintain all these different kinds of devices, and maintaining those products was a headache. With Everest, we have a single, consolidated view of our system, our network, and even our ITSM requirements, like asset management, change management, and incident management. We are even using their ticketing system for our organization. It's been a great help for us in terms of managing our ITSM policies. 

In addition, it has helped us to achieve our ISO certification targets for which we need to maintain all incident management and incident reporting. We can also find an SLA report for our appliance.

We have also tested the workflow management, to try to find dormant VMs, machines that haven't had any traffic or that are not being used by customers; or if there are any VMs that are using very high CPU or memory or choking our network bandwidth. We're also monitoring NetFlow to see the traffic behavior of the VMs: What kind of traffic have they been using? We're using these workflows and NetFlow monitoring tools to zero in on the VMs, if there are any infections going on or if there are any management activities going on that have been using our infrastructure.

What is most valuable?

What I really like about it are the details that it provides whenever we click an icon or any of the objects on the dashboard. We get a detailed description. We're running 200-plus VMs in our infrastructure. If I click on any of the symbols I can see detailed information about a VM: the traffic, the resources utilized by that VM, and whether the SLA is being met by that VM and the services. That is visible on the dashboard. It's just a few clicks and you get all the details as required.

There are role-based access policies defined for our employees. For example, at the L1 level, we define the policies that they can view and the devices they can access. They can only view them, they cannot edit. Our higher-level guys can edit, add devices, and they can create multiple dashboards as required. This is important because each person in our NOC or our data center has specific, targeted goals. Some of the network admins only require seeing network traffic utilization. Some will require port utilization. They may require specific ports and specific devices to monitor a single application.

For example, we have a database system and we need to monitor the underlying network infrastructure related to it, as well as the application related to it. We created a customized dashboard and handed it to the application custodian or database custodian of that system so that he can get an overview of the condition of all the infrastructure that he is using.

We have set a role-based access policy for network admins and network operators so they will only be monitoring VPNs, network device connectivity, and all the tunnels. We are connected with multiple internet service providers, so we can monitor which of them is using a lot of traffic and where the traffic is coming from. 

The role-based dashboards provide data points and charts and topology diagrams in a single window. It's like a spider web, where the application, connectivity, and everything is defined for each user of those applications.

The granularity that Infraon IMS provides to us is really spectacular. If we see a VM in what may be an unhealthy state, we drill down and see what the issue is, whether it's a memory issue or a CPU issue, what time it was triggered, and how it was recovered. All these kinds of measurements are available via drill-down from an events list base.

In addition, the GUI is very interactive and customizable, because the dashboards are customizable. There are two parts to the GUI. One is the operation part where we can see reports and customize them. The other is the admin part where you can add devices. That has to be very quick because we are adding new devices every day, and it is very helpful. We are pretty satisfied with the GUI.

We were also amazed by the reporting capabilities. Previously, we were using open source monitoring systems, like Nagios and Cacti, and we were having a hard time with them. You need to customize each and every module and every parameter to generate an intuitive report view and a summarized query. So getting analytics or doing capacity planning was difficult. With Infraon IMS we're happy with the number of reports and the granularity. And its summarized view of the infrastructure helps us in planning.

What needs improvement?

In terms of improvements, I would like to see an integrated view of Infraon IMS and Infraon Desk. It would be very helpful if that were integrated into the solution.

In terms of additional functionality, a feature they may have but that I haven't been able to find is the ability for a manager to see all the tickets of his subordinates. It would be good if a manager could see every incident ticket, even those not assigned to him. That way, a manager could see every incident ticket that has been opened in the organization and assign them to individuals.

For how long have I used the solution?

We've been using Infraon IMS for more than six months.

What do I think about the stability of the solution?

I have not seen any hiccups since the deployment. There haven't been any issues.

What do I think about the scalability of the solution?

We have not scaled it that much, but per the information that I have, and from what we have seen in the infrastructure and system, increasing resources or trying to add modules is not too difficult. Because we were not previously using NetFlow monitoring, we added a small module for NetFlow monitoring, and the system was scaled out for the database sizing to retain the NetFlow sizes. It was straightforward.

Regarding expanding use of the solution, because we are providing services to our customers, we want to create a type of tenant-based model and sell it to our customers.

In addition, as of now we are only monitoring the infrastructure that we are handling, like data center services, meaning our infrastructure. We're planning to enhance it so that all our data center colocation customers can also have their own ITSM tools.

How are customer service and technical support?

As far as I know, the experience with their technical support has been very wonderful. Whenever we have had any queries, they have responded promptly. The technical guys are in touch with our project team all the time. Whenever they need any plugins or tweaks, they have been helped by the Everest technical team.

Which solution did I use previously and why did I switch?

We were using open source tools, like Cacti and Nagios, and we were using another solution for our ticketing system. We decided to switch because there are limitations with open source. We had to have a dedicated team assigned to the open source solutions and that team had to manage the system. There was a lot to tweak with open source, per our organization's requirements. 

We had Cacti for network monitoring to provide a graphical representation. For SLAs we needed to maintain a Nagios system where we had to add all our devices and network monitoring tools. We were also using a separate asset management tool which was not fully functional. It was a separate system and we needed to train our guys on multiple systems. It was a pain for the operation team, and the NOC team also had to look at different consoles and different solutions to find any compliance issues.

And the ticketing system also created a lot of impact, because previously we were using a plain vanilla ticketing system that was open source and not very feature-rich. It was just a basic ticketing system, and generating reports to get any analytics on incidents required a lot of manual work.

With Infraon IMS what we have found is a single pane of glass to view all our network monitoring requirements for our NOC system. 

How was the initial setup?

The setup was pretty straightforward for our team because Everest sent a guy who helped us to develop the infrastructure and that helped a lot when it came to the initial deployment.

They required some VM cloud infrastructure information, like space and sizing. We had to prepare those machines before deploying the solution.

We had our guys trained on it within a week or so. They understand the architecture, as there are a lot of components built into this solution. There are databases, collectors, and some network connectors. But it's pretty easy to learn Infraon IMS because there aren't too many components that you need to set up.

Within a month or so our ticketing and NMS were already deployed.

As of now, our whole NOC team of 10 to 15 guys is using the solution. Our system team, which has about another eight people, is also using it, as are the executives to generate asset, compliance, and SLA reports.

What about the implementation team?

We assigned two of our staff to the deployment, one from the network team and one from the system team, and the Everest guys were aligned with that. They helped our team to get it deployed and, in the next month, we rolled it out to production.

What was our ROI?

We have not done an ROI calculation yet, but I'm seeing a lot of impact as a result of the deployment of this infrastructure, with our guys needing less time to manage the NMS solution itself. We have a technical pool that manages our system and the operations of the data center. When they need to spend all their time managing the NMS system, we're losing all that time. Now, they don't need to focus on the management tools. They can monitor another customer and do other work. It's saving a lot of time for them, something like 20 to 30 percent of their time.

We had a lot of tools and products in the data centers and we were getting bogged down. All these solutions required resources and our guys needed to be trained on them. Whenever someone would leave, we needed to train the newer guy. It was creating a lot of havoc.

What's my experience with pricing, setup cost, and licensing?

The pricing is reasonable, given the features that they provide. There have not been any additional costs beyond the standard fees.

Which other solutions did I evaluate?

We looked into ManageEngine, PRTG, and other tools. But for our infrastructure and our scale, we required something that could be scaled out and something that was customizable. We also needed something to provide us with ITSM tools, a help desk with workflow and a ticketing system.

We also evaluated Zabbix about a year and a half ago but the deployment cost was very high. It was going to take more than two months to deploy. Our guys were not so aligned with or trained on Zabbix. They would find it very difficult to manage all the plugins. So we opted not to go with open source.

With Infraon, we get a one-stop view of all infrastructure and every ITSM requirement that we have, from a single vendor and solution. It had good reviews in the international market also. We came across it because we had proposed it to one of our customers and we saw that the customer was very happy. While managing the system, we found that it is a very helpful tool.

What other advice do I have?

We don't use Infraon IMS to automatically trigger processes to help resolve issues when it detects compliance violations, but we have triggered reports. We don't want any automation as of now, so we are only using manual intervention to take any actions. We need to be sure about our workflows. Once the actions are tried and tested then we will put in the automation.

The biggest lesson I have learned is around the consolidation of all our NOC and ITSM requirements in a single solution. We were only looking for an NMS solution, but they provided us with a workflow, automation, a ticketing system, and an incident management system. It has been a revelation for us.

Overall, it's a wonderful one-stop ITSM solution for infrastructure.

Which deployment model are you using for this solution?

Private Cloud
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor. The reviewer's company has a business relationship with this vendor other than being a customer: Reseller.
Flag as inappropriate

EverestIMS Questions

Miriam Tover
Content Specialist
IT Central Station
Jul 20 2021

If you were talking to someone whose organization is considering Infraon IMS, what would you say?

How would you rate it and why? Any other tips or advice?

Julia Frohwein
Content and Social Media Manager
IT Central Station
Jul 20 2021

How do you or your organization use this solution?

Please share with us so that your peers can learn from your experiences.

Thank you!

Miriam Tover
Content Specialist
IT Central Station
Jul 20 2021

Please share with the community what you think needs improvement with Infraon IMS.

What are its weaknesses? What would you like to see changed in a future version?

Miriam Tover
Content Specialist
IT Central Station
Jul 20 2021

Hi,

We all know it's really hard to get good pricing and cost information.

Please share what you can so you can help your peers.

Julia Frohwein
Content and Social Media Manager
IT Central Station
Jul 20 2021

Hi Everyone,

What do you like most about Infraon IMS?

Thanks for sharing your thoughts with the community!

Miriam Tover
Content Specialist
IT Central Station
Jul 08 2021

If you were talking to someone whose organization is considering Infraon Desk, what would you say?

How would you rate it and why? Any other tips or advice?

Julia Frohwein
Content and Social Media Manager
IT Central Station
Jul 08 2021

How do you or your organization use this solution?

Please share with us so that your peers can learn from your experiences.

Thank you!

Julia Frohwein
Content and Social Media Manager
IT Central Station
Jul 08 2021

Please share with the community what you think needs improvement with Infraon Desk.

What are its weaknesses? What would you like to see changed in a future version?

Julia Frohwein
Content and Social Media Manager
IT Central Station
Jul 08 2021

Hi,

We all know it's really hard to get good pricing and cost information.

Please share what you can so you can help your peers.

Julia Frohwein
Content and Social Media Manager
IT Central Station
Jul 08 2021

Hi Everyone,

What do you like most about Infraon Desk?

Thanks for sharing your thoughts with the community!

Julia Frohwein
Content and Social Media Manager
IT Central Station

Hi,

We all know it's really hard to get good pricing and cost information.

Please share what you can so you can help your peers.

reviewer1476927The price is much better than SolarWinds. We pay for a number of devices on the… more »
Abhirup SarkarLicensing is fairly simple being device-based with certain add-on modules for… more »
Miriam Tover
Content Specialist
IT Central Station

If you were talking to someone whose organization is considering Everest IMS, what would you say?

How would you rate it and why? Any other tips or advice?

Miriam Tover
Content Specialist
IT Central Station

How do you or your organization use this solution?

Please share with us so that your peers can learn from your experiences.

Thank you!

Julia Frohwein
Content and Social Media Manager
IT Central Station

Please share with the community what you think needs improvement with Everest IMS.

What are its weaknesses? What would you like to see changed in a future version?

Julia Frohwein
Content and Social Media Manager
IT Central Station

Hi Everyone,

What do you like most about Everest IMS?

Thanks for sharing your thoughts with the community!