Hyperglance: Up to 10000 Resources [GovCloud]

Our main use case for Hyperglance  is cloud analysis, which helps us visualize the infrastructure and serves as a cost-effective cloud management system for our organization.

We initially faced an issue with AWS  where costs were very high and tracking dependencies was difficult. We switched to Hyperglance  to have a single view of the cloud, which addresses costs, architecture, and dependencies together. This allows us to consolidate our cloud infrastructure from AWS  and Kubernetes  into one unified location.

Hyperglance provides visibility that creates a unified view of the entire cloud system, allowing us to debug much faster than we were able to initially. With this visibility, new engineers being onboarded find it easier to understand the infrastructure. Cost optimization is also a significant benefit we gain from Hyperglance, as we are able to see unused resources, which aids in budgeting.

Beyond easier onboarding and faster debugging, Hyperglance automatically identifies idle servers, reducing costs by shutting them down and creating Jira  tickets automatically.

The unified view offered by Hyperglance is a huge benefit that we have been able to see. These features stand out for us because it becomes easier to make decisions when all of the information is in a single, simple, unified view. This simplicity makes it easier to debug and for new team members to understand the infrastructure, as they can see budget costs and consider options regarding budgeting, ultimately increasing capacity and speeding up decision-making.

Hyperglance is greatly scalable because, as soon as we scale it to a greater architecture or a larger number of servers, it quickly identifies unused resources, making debugging faster and enhancing budget tracking. We also receive automatic anomaly alerts, so I would say it performs very well in terms of scalability.

Hyperglance has a multi-cloud visualization system and automates many things; however, a downside is that the user interface feels somewhat complex when you start. When we first began using Hyperglance, the user interface felt complex initially, but once you become familiar with it, it becomes easier to use. It is powerful, but it is not very easy for a beginner to adapt to.

The user interface of Hyperglance might feel complex in the initial stages, and I would also say that it can be somewhat expensive for small teams or early-stage startups. Hyperglance could be costly for someone with simple infrastructure. Therefore, I think the cost aspect and the user interface could be improved.

Hyperglance is a powerful tool when it comes to cloud operations, functioning as a control system. However, for an early-stage startup that does not have much reliance or is not heavily dependent on cloud operations, it might not be a good option for them. If the cost could be reduced and onboarding made a little easier, early-stage startups would benefit greatly from Hyperglance.

I have been using Hyperglance for nine months.

Hyperglance is stable in its performance.

I have not faced any issues that required customer support, so I cannot comment on that. However, I think the product is really good, and we have not had many issues that would necessitate support.

Initially, we were using AWS before switching to Hyperglance.

We have seen a return on investment from Hyperglance, as we are now able to identify waste very efficiently. We have achieved approximately twenty percent cost reduction due to the shutdown of idle servers, and we have also seen approximately eight to ten percent improvement in time, providing significant benefits from Hyperglance.

The cost was pretty steep, and we were not initially very certain about taking Hyperglance due to its price. However, it is a very powerful tool, and I have not been the one handling the pricing and licensing aspects.

I evaluated other options before choosing Hyperglance, but I cannot elaborate on this as I am not familiar with those specific options.

My advice for others looking into using Hyperglance is to first assess their team's needs. If there is a small team that does not rely heavily on cloud services and does not need multi-cloud complexity, they might be fine without it. However, if they have a heavy reliance on cloud services and need visibility, automated shutdown of idle servers, and budget tracking, I would definitely suggest Hyperglance. Although it might be complex initially, once you become familiar with it, it is an excellent tool.

For Fintech teams or those who rely heavily on cloud services, Hyperglance might be a great tool, even though the user interface might feel complex at first. I would rate this review a seven overall.