Why Enterprises Choose Komodor
Over Rafay

With Komodor, we were able to finally gain visibility into our nodes, and use our engineering resources properly, instead of wasting so much time on troubleshooting. It used to take us hours to detect a faulty node, and by the time we did, it would’ve already affected other resources.

My advice would be don’t overthink it. It was so easy to onboard. It’s definitely worth it in the long run. The great thing about it, and this speaks volumes about the organization and the product they have made, is that it does a great job running itself, and the users are very happy with it.

Komodor has significantly sped up development process by taking the operations team out of the loop, having a huge impact on our development velocity and end-to-end ownership, from development to deployment and monitoring.

Komodor has been a valuable addition to our K8s toolkit. It has allowed us to easily manage and troubleshoot our clusters, greatly reducing the load on our DevOps while making our developers more efficient.

There were things that simply weren’t apparent to us before we saw the issue in Komodor. It has been immensely helpful for us whenever we’ve had network problems or other such issues.

With Komodor’s new capabilities around Helm management and auditable actions, we can empower our developers and enable them to operate K8s independently, increasing end-to-end ownership, system security, and velocity.

The initial setup was very straightforward and only took two minutes. The more time we use Komodor the more we save. Currently, we have seen around a ten percent return on investment.