We’ve written about the Hyper9 acquisition on The WhiteBoard and on Geek Speak, but I’m going to add a couple of thoughts and try my best to indicate where Hyper9 and our other related products are headed.
First off, why did we buy Hyper9? As we’ve said before, we listen to our customers. What we heard them telling us is that virtualization continues to grow in importance. Moreover, we heard that they’re facing new management challenges around capacity planning, performance optimization, and configuration tracking. We have a great engineering team, and they could have built what our customers needed, but it’s pretty clear that the problems they face are both serious and urgent, so we looked around at other companies offering virtualization management solutions. To be honest, it’s not easy to find companies and products to join SolarWinds because their software has to meet the same standards as our software: Easy to install, configure, deploy. The UI has to be simple, yet powerful. It has to be accessible to the little shops yet scale to the really big shops. It’s not easy to find products like that because it’s not easy to build products like that.
I can’t speak for everyone at SolarWinds, but one of my personal tests for evaluating other people’s software is whether I’m overcome with envy that someone else built something so good and that I didn’t get to be part of it. That’s how I felt when I saw Hyper9’s product. It’s pretty awesome. Why didn’t I do that? Sigh. My personality disorders aside, the quality of the product really came as no surprise because the product team is actually here in Austin. Consequently, many of us already knew the folks on the Hyper9 team personally or by reputation. Awesome product, awesome product team. We bought Hyper9 because they solved the virtualization management problem so well that seemed like a much better option to join forces on this front than to compete with them.
If you have a virtual environment, you should check out Hyper9. It’s a virtual appliance that you can download and drop on your VMware host. Simple config process, and you’re collecting data. You’ll find orphaned VMs. You’ll be able to see how to squeeze more performance and more capacity out of your infrastructure. It’s got an incredible search engine that lets you find out anything you need about your VMs and their performance. Plus, it’s just cool to play with that much new data.
I do want to answer one of the questions we’ve started to get on thwack and directly to PMs about how Hyper9 relate to our existing Profiler product line, which has some virtualization-related functionality. Where does each product fit? Here’s the deal: The Profiler product line is focused on storage management, but it has some virtualization features around mapping VMs to storage resources, which allows troubleshooting of VM problems such as those caused by multiple VMs contending for the same storage resources. If you have a problem managing storage or a problem managing how virtualization impacts storage (or vice versa), then Profiler is the right product. In contrast, Hyper9 is aimed at broad and deep virtualization problems like VM sprawl, performance optimization, and capacity planning—pretty much anything that isn’t storage. Anyone who wants to get the most out of their virtual infrastructure needs Hyper9.
- If you have a virtualization problem that has nothing to do with storage, you need Hyper9
- If you have storage problem, but don’t much care about virtualization, you need Profiler
- If you have a problem with the impact of virtualization on storage, you need Profiler
- If you have a problems with storage, virtualization, and with the impact of virtualization on storage, you need both Hyper9 and Profiler.
And that’s how we’re going to invest in these products going forward: Profiler will continue to focus on storage management, including storage management problems arising from virtual machines. Hyper9 will continue to focus on all other aspects of virtualization management. Will we integrate Profiler and Hyper9? I can’t promise anything, but it wouldn’t be a shocker if we did, would it?