We use this solution to optimize and manage our multi-terabyte, core banking application logs on our servers.
DevOps Team Leader at a financial services firm with 1,001-5,000 employees
A strong application log management solution with a suite of useful features, and a user-friendly UI
Pros and Cons
- "This solution is not vendor-locked, which means that we we are able to use it across all of our resources; this feature is of great value to us."
- "We have found that the auto-secure feature of this solution doesn't always work, and could be improved to be more reliable, particularly when working with business critical applications."
What is our primary use case?
What is most valuable?
This solution is not vendor-locked, which means that we we are able to use it across all of our resources; this feature is of great value to us.
We also like that the UI for this solution has been improved, which has made it easier to use.
What needs improvement?
We have found that the auto-secure feature of this solution doesn't always work, and could be improved to be more reliable, particularly when working with business critical applications.
For how long have I used the solution?
We have been using this solution for two or three years.
Buyer's Guide
Rancher Labs
December 2024
Learn what your peers think about Rancher Labs. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.
What do I think about the stability of the solution?
The stability of this solution is good, except for the auto-secure feature, whose use impacts the performance of the product.
How was the initial setup?
We found the initial setup for this solution to be easy.
What about the implementation team?
We implemented this solution using our in-house DevOps team.
What's my experience with pricing, setup cost, and licensing?
This is an open-source solution, so there are no licensing costs involved.
What other advice do I have?
We would definitely recommend this solution to other organizations.
I would rate this solution a nine out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Principal Engineer at a financial services firm with 5,001-10,000 employees
Easy to scale with good capabilities, however, it could be easier to use
Pros and Cons
- "The scalability potential is very good."
- "We're looking for something that is even easier to use. It's a bit complicated."
What is our primary use case?
We're not using it full-blown; the plan is you have the developers to be able to develop an on-prem and then move it over to the cloud. That was a scenario. We stood up these environments so that it would be easier for us to control our internal costs for development so that we're not spitting up these cycles in the cloud and causing more cost versus just building an on-prem and then moving it to the cloud.
What is most valuable?
So far, we are in the POC stage. Overall, it is working well and we are happy with its capabilities.
The product has been quite stable.
They come out with versions regularly and they are pretty simple to update and the updates are pretty straightforward. You don't have to go through a lot of stuff to go through with the gap. You have a rolling upgrade which is nice. The key part about Ranger is that it has a good relation to storage. It has a great feature for persistent storage for Kubernetes and they work extremely well with one another. Otherwise, you've got OpenShift that uses Cipher and that's yet another infrastructure you have to build out.
The scalability potential is very good.
What needs improvement?
We're looking for something that is even easier to use. It's a bit complicated. When you're dealing with Kubernetes, it is easier, however, there's still a lot of convoluted types of commands.
The situation goes pretty deep and when things go South, you spent a lot of time trying to figure things out, and it takes a certain amount of skillsets. To ramp up those skillsets takes time. Unfortunately, we don't have the time to ramp up those skillsets to bring those things in. There are other solutions out there such as HashiCorp, which offers its own version of managing containers. It doesn't use Kubernetes; is a different way of doing it.
The product could use just a little bit more Federation-type capabilities going forward when you're going to the cloud. That's the kind of stuff I can use. You've got different regions within the cloud, and just from that, we that kind of support.
For how long have I used the solution?
I've been using the solution for about a year now.
What do I think about the stability of the solution?
The stability of the solution has been good overall. It's reliable and offers good performance. There aren't bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
The solution will scale well. That said, we haven't tested it, however, it's pretty straightforward. You just run a couple of commands to build out another node and you scale.
Currently, we don't have too many people on the product. It's just a very few people, just the Unix team, which is about six people right now.
How are customer service and technical support?
Technical support is very good. They're very helpful and responsive. We are quite please with the level of assistance we receive.
How was the initial setup?
The initial setup wasn't simple. It was a bit difficult and a bit complex. We had to get a little help from the Rancher folks to set it up initially, as we really didn't know what the hell we were doing.
The solution doesn't need a lot of maintenance; we have a team of six people working on the solution currently and any one of us could handle it.
What about the implementation team?
Rancher helped us a lot at the outset. We didn't know how to manage the initial setup by ourselves.
What's my experience with pricing, setup cost, and licensing?
I don't handle contracts or licensing costs. I can't speak to how much the solution costs.
That said, it is my understanding that the pricing is very comparable to what else is in the market.
Which other solutions did I evaluate?
We're starting to look at Amazon EKS. We haven't begun to work with it, however, since we use Kubernetes, it may be an option in the future.
What other advice do I have?
We're using the latest version of the solution at this time. I can't recall the exact version number, however.
Currently, the solution not fully in production just yet. It's still kind of like a POC. The value it brings to us is that it's a great tool. We're able to use it. It seems to be able to do the job, however, we are still looking around.
I have no negative thoughts about Rancher. It's a great product for what it is. As far as getting support, the support has been very good. There are some good price points. Ever now since they were acquired by SUSE there's been plenty of opportunities there as well.
In general, I would rate the product at a seven out of ten.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Rancher Labs
December 2024
Learn what your peers think about Rancher Labs. Get advice and tips from experienced pros sharing their opinions. Updated: December 2024.
824,067 professionals have used our research since 2012.
Solution Architect | Head of BizDev at Greg Solutions
Self-contained with a great UI and very good integrations
Pros and Cons
- "A great UI with very good integrations."
- "Could be more intuitive."
What is our primary use case?
Rancher has two main versions which are completely different products. They have some similarities because they have a similar UI and similar concept but are different under the hood. The original Rancher was an orchestration platform for Docker containers based on Cattle and we used that solution for three years extensively for different products and on different projects. We're also now using the Rancher 2 on top of the Kubernetes to manage Docker containers for different customers, for projects, to seize logs, to seize mentorings, to downscale or upscale applications. They provide a great catalog of applications that can be created. We recently used Rancher two for another project that was hosted on top of AWS and on-premise servers. It provides and deploys infrastructures, providing UI for the dev team, the management team, QA team, and enables us to see everything that's going on.
How has it helped my organization?
The solution has saved us a lot of time by not requiring us to configure the all details including monitoring, logging, Kubernetes node provisioning on top of public cloud services.
What is most valuable?
This product has a great UI and because the products are all self-contained in the solution, it provides great features and is easily deployable with a very good integrations.
What needs improvement?
I'd like to see this solution become more stable and have more integrations with other Rancher Labs products, such as Rancher Longhorn.
For how long have I used the solution?
We've used Rancher products for the last four years.
What do I think about the stability of the solution?
We have had some issues as a result of the complexity but it's stable overall.
What do I think about the scalability of the solution?
The scalability is great, it very much depends on the underlying infrastructure.
Which solution did I use previously and why did I switch?
We have used Kubernetes without Rancher so we've used different approaches for our needs. We switched for several reasons: Rancher has a great UI, its operational costs were less, and there were not too many competitors on the market when we switched to use the first Rancher. It was really, I believe, the best on the market in terms of managing containers. Since Rancher 2.0 migrated to Kubernetes, we found that we could manage this directly using dashboards and tools from the community.
How was the initial setup?
It's definitely easy to deploy, easy to connect to existing clusters or to provide new clusters, scaling of applications, application logs, and multi cluster setup. The initial setup is variable depending on the size of the company and the project. It can take anywhere from 15 minutes to two days.
What was our ROI?
The ROI for us has been improved visibility, speed of deployment, reliability, and we have great feedback. We were able to save on time in marketing the applications.
What's my experience with pricing, setup cost, and licensing?
We used the free open source version so there were no costs associated with licensing. I know it's possible to get support but I don't know the cost. I think it's minimal.
Which other solutions did I evaluate?
We evaluated a lot of other products including Elastic Container Service, its Azure App Services, Google App Engine and DigitalOcean hosting options, which is an Oracle application, and many more. We did market research and carried out evaluations and took a look at all available free and open source solutions. When we decided to use the first version of Rancher, it provided the best UI, the best scalability and stability. It's better than ECS which uses other tools for monitoring and logging. There is a different UI and the cloud tools are not as user friendly. When we took a look at other tools each of them had something wrong from our point of view.
What other advice do I have?
We immigrated from Rancher 2.0 to the AWS ECS. The idea behind initially using Rancher was as an option to native cloud services. Because it provides all features we could configure it in less time than it would take to use the public cloud services. By using this solution we've learned how to manage complex infrastructures and microservices, and how to provide visibility and audit for different teams.
Rancher has established partnerships and they have tightly integrated it in the public cloud, such as AWS or Google cloud. I would recommend that anyone wanting to try it, install it, play with it, and see the pros and cons. It's something that anyone should do with all the other competitors and solutions.
I would rate this solution a nine out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
DevOps Engineer at a financial services firm with 501-1,000 employees
Well designed dashboards, user friendly, and easy to manage
Pros and Cons
- "The solution has a lot of good features, such as you can access the console and edit through the GUI. The dashboard and the UI are designed well, user-friendly, and easy to manage, and access."
- "The solution could improve by adding more features in the dashboard, such as monitoring, scanning, and security. This would be a great benefit."
What is our primary use case?
We are using Rancher Labs' for the overall management of our Kubernetes cluster. For example, we manage the production and UAT environment of all our applications or containers.
What is most valuable?
The solution has a lot of good features, such as you can access the console and edit through the GUI. The dashboard and the UI are designed well, user-friendly, and easy to manage, and access.
What needs improvement?
The solution could improve by adding more features in the dashboard, such as monitoring, scanning, and security. This would be a great benefit.
For how long have I used the solution?
I have used Rancher Labs for approximately one year.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
We have not had any issues with scalability.
How are customer service and technical support?
We have not paid for the support for the solution.
How was the initial setup?
The initial setup is easy.
What about the implementation team?
We did the implementation of the solution.
What's my experience with pricing, setup cost, and licensing?
The solution is free and open source but there is a fee for support.
Which other solutions did I evaluate?
We have been evaluating Red Hat OpenShift, Kubernetes, Tanzu, and Nirmata.
What other advice do I have?
I rate Rancher Labs an eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Automation Engineer at FPT Telecom
Easy to install product with an efficient log management feature
Pros and Cons
- "The product is simple to use for a beginner."
- "They should improve application visibility along with code visibility."
What is our primary use case?
We use the product to manage Kubernetes licensing, the flow of the containers, and monitoring purposes.
What is most valuable?
The product is simple to use for a beginner. It has an efficient log management feature.
What needs improvement?
They should improve application visibility along with code visibility.
For how long have I used the solution?
We have been using Rancher Labs for four years.
What do I think about the stability of the solution?
It is a stable platform. I rate its stability a seven out of ten.
What do I think about the scalability of the solution?
A team of ten DevOps executives uses Rancher Labs in our organization.
Which solution did I use previously and why did I switch?
We used Ansible platform. We switched to Rancher Labs as it is simpler to use.
How was the initial setup?
It is easy to install and integrate with VMware and OpenShift. It takes around a few minutes to complete the process.
What other advice do I have?
I rate Rancher Labs an eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer:
Chief Executive Officer at a tech services company with 11-50 employees
Stable and scalable, but more pricing flexibility needed
Pros and Cons
- "The solution is stable."
What is our primary use case?
Rancher Labs is used to deliver containerized applications over a containerized architecture.
For how long have I used the solution?
I have been using this solution for a couple of months.
What do I think about the stability of the solution?
The solution is stable.
What do I think about the scalability of the solution?
Rancher Labs is scalable.
We have approximately 10 people using this solution in my organization.
What about the implementation team?
We use engineers for the implementation and maintenance of the solution.
What's my experience with pricing, setup cost, and licensing?
There is an annual subscription. The price of the solution should be cheaper and have better pricing flexibility.
Which other solutions did I evaluate?
We evaluated VMware Tanzu before choosing Rancher Labs.
What other advice do I have?
I would recommend this solution to others.
I rate Rancher Labs a seven out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Rancher Labs Report and get advice and tips from experienced pros
sharing their opinions.
Updated: December 2024
Popular Comparisons
VMware Tanzu Platform
Red Hat OpenShift Container Platform
Amazon EKS
Kubernetes
Nutanix Kubernetes Engine NKE
Google Kubernetes Engine
Docker
Splunk Infrastructure Monitoring
Amazon Elastic Container Service
HashiCorp Nomad
Portainer
HPE Ezmeral Container Platform
Mirantis Container Runtime
Komodor
Diamanti
Buyer's Guide
Download our free Rancher Labs Report and get advice and tips from experienced pros
sharing their opinions.
Thank you for the review. Lokman's review mentions main points that many firms want to know about rancher.