We use Red Hat Enterprise Linux to run quite a few pieces of software. It's mostly for jPOS, but we also run some Apache solutions and some security applications.
Senior Software Engineer at a energy/utilities company with 501-1,000 employees
I like the speed of the OS data and the ease of Ansible automation
Pros and Cons
- "I like the speed of the OS data and the ease of Ansible automation. I don't need to spend much time managing everything."
- "I use Linux on Satellite with Ansible infrastructure. It would be great if there were a universal interface to control RHEL's policy from Satellite. It could be a dashboard showing which policies were enabled on what system and allow you to apply them from the dashboard."
What is our primary use case?
How has it helped my organization?
Red Hat Enterprise Linux has streamlined a lot of the support issues. When we've had problems, Red Hat has been proactive about solving the problem with us. Support is always an issue with open-source platforms. By providing this support, Red Hat makes it much easier to adopt Linux.
I love Red Hat Enterprise Linux's built-in security. You can see who is trying to do what and who isn't allowed. You get an alert for that. We also use a product from Symantec on the Linux system for real-time threat detection, but I think we probably don't need that. Red Hat already has these capabilities, but the security team needs something they can centrally manage. They need to know whether the system is protected and the agent is running.
We use it on VMware, and we have a multi-site deployment, so it's very easy to patch and keep the servers up. We use Ansible automation for patching, which has really helped with the service uptime.
What is most valuable?
I like the speed of the OS data and the ease of Ansible automation. I don't need to spend much time managing everything. The provisioning and patching using Ansible is seamless. Ansible automation gives you almost a cloud-like capability on-premise. Most of my group doesn't have cloud skills. I learned it on my own and got my Kubernetes certification. I'm familiar with the automation infrastructure, how to build the execution environment and implement the private automation hub. Others still need training.
I've used Red Hat Enterprise Linux Image Builder for testing and development, but I haven't put it into production. We have a VMware template, and we've been doing training on VMware, but we are not there yet. I think they might move from VMware to another product. They are looking at other options, such as OpenShift, but we don't have training for OpenShift yet. They should try to have a salesman come and get OpenShift training for customers. If they make training free for the customers, more would switch to OpenShift from VMware.
What needs improvement?
I use Linux on Satellite with Ansible infrastructure. It would be great if there were a universal interface to control Red Hat Enterprise Linux's policy from Satellite. It could be a dashboard showing which policies were enabled on what system and allow you to apply them from the dashboard.
I think Red Hat training could be cheaper. A company can move fast technologically with enough training. They will be stagnant without training and remain unable to fully leverage the technology. I have been encouraging the group to get a subscription to the training course for five years, but we haven't been able to take advantage of it because of the cost. They should make it cheaper for clients and offer big discounts at scale.
When people lacked training for the technology we use, we migrated away from it. I worry that if we don't have enough training available to the client, they will eventually migrate away from Red Hat. More affordable training on key technologies like Satellite and Ansible automation will help us retain customers on those products. Downstream it will help them migrate to the latest and greatest Red Hat Enterprise Linux, as well.
Buyer's Guide
Red Hat Enterprise Linux (RHEL)
January 2026
Learn what your peers think about Red Hat Enterprise Linux (RHEL). Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
881,114 professionals have used our research since 2012.
For how long have I used the solution?
I have used Red Hat Enterprise Linux since 2005.
How are customer service and support?
I rate Red Hat support 10 out of 10. I've been very impressed with the knowledge base and the support from Red Hat. When I create a ticket, they respond and resolve the issue quickly or they point us to the correct resources. For example, we had an NFS issue with ISO, so they helped us with the mounting options. We also had an issue with IBM AIX and Red Hat integration. Red Hat referred us to the IBM support stack, and we were able to get IBM to help us out.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Initially, I used Solaris because I liked it the best, but Red Hat Enterprise Linux has improved so much that it has overtaken Solaris. Red Hat Enterprise Linux is easier to use and has better documentation. I also like having the ability to use Satellite and Ansible automation to manage Red Hat Enterprise Linux.
How was the initial setup?
The deployment is straightforward because we use Ansible automation to spin up a new system and install applications directly from the Ansible workflow. We were planning to have Red Hat Enterprise Linux 8 online last year, but Red Hat Enterprise Linux 9 came out, so we decided to wait for a bit, and we're almost ready to upgrade to Red Hat Enterprise Linux 9. The application folks still haven't had enough time and money to migrate everything over, and we need a project manager.
What other advice do I have?
I rate Red Hat Enterprise Linux 10 out of 10. It comes with all of these nice tools like the Satellite automation web console.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
IT Consultant at a manufacturing company with 10,001+ employees
Good patching and automation capabilities with excellent support
Pros and Cons
- "The features and tools help us to maintain security overall."
- "If they can make the integration with Ansible easier, that would be ideal."
What is our primary use case?
We primarily use it for OS purposes.
How has it helped my organization?
It's very good for support compared to other operating systems. For decades, it's been providing good support and service. Even during implementation, there's a dedicated team to answer any queries. We are a very big company running critical applications and having that support is very important.
What is most valuable?
The patching tool is good. We're also introducing the possibility of automation.
The built-in security features are okay when it comes to simplifying risk reduction. It makes life easier, especially in regards to the lifecycle and what we need to install, et cetera. The features and tools help us to maintain security overall.
It is easy to maintain compliance.
The portability of applications and containers is good. Now we are just starting with the containers and anything related to Kubernetes.
Red Hat is always providing security on time. Any vulnerabilities are immediately dealt with to fill the gap and deal with the issue.
It's a good tool. I'm very confident with this product.
The system role features for automation security configurations, et cetera, for Ansible, we started using it. We are new in terms of automation. We'll start to use it heavily in the near future. Ansible is another great tool from Red Hat.
It enables us to maintain consistency across systems over time. My role is to maintain stability, even during upgrades and patches. So far, it's been a positive experience. We use the entire ecosystem around Red Hat.
We use Red Hat Insights. From a security perspective, we may stop using it. With Insight, if you have Red Hat Satellite, it gives you an in-depth view of everything. The only thing missing is the insights related to performance. We may not continue with it. We'll see if we'll push it and have everything on the cloud.
What needs improvement?
In the area we are using it, we are satisfied.
Maybe in OpenShift, which is our next step, there can be more improvements with integration with Kubernetes. We're not experts there yet.
Maybe it could have a better user experience and less coding. Reducing the effort for the end user or administrator would be ideal to make daily operation and maintenance easier.
If they can make the integration with Ansible easier, that would be ideal.
They should offer more in terms of learning materials to make learning easier.
They need to make things more affordable or accessible.
What do I think about the stability of the solution?
The solution is stable. We barely have any issues with a server setup. So far, it's manageable. The biggest challenge is the criticality of releasing patches. When we have any critical alerts we action them. We tend to try to wait for the release of a stable version.
What do I think about the scalability of the solution?
How many people use the solution depends on the application. We likely have thousands of users. We do have some products that maybe only have a few or a few hundred.
We've had no challenges with scaling. It can support any type of load within the data center.
How are customer service and support?
Support is excellent.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We did use a different OS. I have used Unix in the past. I started with Unix 30 years ago. I've also used SUSE. Red Hat offered more service and support.
How was the initial setup?
I was involved in the deployment. Our team managed the process. It's pretty straightforward. We handle implementation, tuning, and patching.
How long it takes to implement the product depends. We're trying to mitigate the time by automating with Ansible. We want to handle one VM or server in five or fewer minutes, however, it can take days. At this point, we can provision servers in a few minutes. It's becoming faster.
We have a team of ten to run the infrastructure on the OS level.
What was our ROI?
I'm not an expert on ROI. We are paying to use the solution, however, the utilization we get and the support both offer good value.
What's my experience with pricing, setup cost, and licensing?
The pricing model isn't something I deal with directly. The pricing is fair, especially compared to virtualization like VMware. We do use VMware and are thinking about moving sandboxes and testing over to Red Hat. This may end up being a big cost savings with our CAPEX and OPEX.
From the price level, the cost is almost the same for us, if we look at Red Hat versus SUSE, however, we get a higher level of support with Red Hat.
Which other solutions did I evaluate?
Red Hat was always our first choice.
What other advice do I have?
We're a Red Hat customer.
I'd rate the solution nine out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Red Hat Enterprise Linux (RHEL)
January 2026
Learn what your peers think about Red Hat Enterprise Linux (RHEL). Get advice and tips from experienced pros sharing their opinions. Updated: January 2026.
881,114 professionals have used our research since 2012.
IT at a computer software company with 1-10 employees
Allows us to easily identify numerous vulnerabilities in malware and facilitates simpler patching, as well as maintaining compliance
Pros and Cons
- "Red Hat has introduced a fast server, where Red Hat Enterprise Linux can be integrated or connected to via a client."
- "The performance component is available on Red Hat Enterprise Linux, but we need to maintain the dashboard on-premises, which requires us to switch between systems instead of performing all tasks from a single location."
What is our primary use case?
We are a telecommunications operator using Red Hat Enterprise Linux for our technical applications due to its supportability and robust management features.
How has it helped my organization?
Red Hat Enterprise Linux's built-in security features aid in simplifying risk reduction. In the past, patches fortified the security features, but now, with playbooks, we can automate and address any findings for any Common Platform Enumeration. When integrated with Red Hat Insights, the solution can identify the CPE and provide the remediation playbook. This expedites detection, remediation, and testing by Red Hat, thanks to the playbooks provided by satellite as well as malware detection.
Maintaining compliance with Red Hat Enterprise Linux is easy because it supports various out-of-the-box compliance policies, such as CIS. Whether we are running OpenSCAP on-premises or Insights, we can perform compliance testing using OpenSCAP to verify adherence to the Red Hat Enterprise Linux security guidelines, as well as other well-known guidelines and framework compliance. I have found that all the compliance policies I required were already included out of the box.
Red Hat Enterprise Linux is ready to help keep our organization agile when it comes to the portability of applications and containers because all the applications are developed by the vendor. Red Hat Enterprise Linux is the preferred choice in our industry because the applications we use are swiftly certified by the vendor, so we don't have to verify them ourselves.
Red Hat Enterprise Linux provides enhanced security for our servers, and we are aware of patching requirements in advance. Additionally, the pre-certification of Red Hat Enterprise Linux applications expedites deployment as we no longer need to go through the certification process ourselves. Moreover, Red Hat Enterprise Linux offers excellent support, ensuring that any issues that may arise are promptly addressed, which is crucial for our environment where we must maintain an uptime of 99.99999 percent.
Red Hat Enterprise Linux enables us to achieve security standards certification because it is driven by various compliance policies that include everything we need out of the box. This makes it easy to enforce security rules, and security patches are applied regularly. With Insights, we have malware detection, CPE filings, and remediation capabilities. In addition to the reactive approach, we also benefit from a proactive approach, allowing us to stay informed about the events around us, which helps us implement temporary solutions if needed until a permanent fix becomes available.
With Red Hat Enterprise Linux, we can build with confidence, knowing that it is available across physical, virtual, and cloud infrastructures. The operating system provides certifications, ensuring that we can deploy with 100 percent certainty, knowing that the applications will work. Additionally, it offers identity security and excellent support from the Red Hat team. Without this support, we would have to rely on searching within the community and downloading untested patches, which may function in small environments but not for larger ones with sensitive applications.
Red Hat Insights helps us prevent emerging issues related to security or noncompliance settings. One of the steps we take before going live is using OpenSCAP to ensure compliance with our standards. This is followed by our own security scanning and verification process. If any issues are not known within Red Hat, we can always refer to all the findings. Once the system is in production, regular monitoring allows us to use Insights to identify any new findings and apply necessary patches or workarounds. The knowledge base available on the servers enables us to take proactive measures even before a security patch becomes available. The new malware detection feature in Insights helps protect end-user information.
Insights provide vulnerability alerts and specific guidance. With each system, we can view the detected Common Platform Enumeration and receive advice on how to address it. These features have protected our systems from potential attacks, thereby increasing our uptime.
What is most valuable?
Red Hat has introduced a fast server, where Red Hat Enterprise Linux can be integrated or connected to via a client. This connection allows us to identify numerous vulnerabilities in malware easily and facilitates simpler patching. Activating the Red Hat addons on this server creates a perfect match when seeking a well-hardened OS using the gold image, as it eliminates the need to address issues from an existing image. Additionally, Red Hat Insights is a valuable and essential tool. In the telecom industry, we rely on basic products that necessitate an OS with robust security support and regular patches.
What needs improvement?
We have not succeeded in creating an image from Red Hat Insights for Red Hat Enterprise Linux, including custom partitioning and custom scripts. This would have been helpful.
Red Hat Insights reporting can be enhanced by incorporating performance components, making it a central tool for vulnerability assessment, compliance monitoring, and much more. The performance component is available on Red Hat Enterprise Linux, but we need to maintain the dashboard on-premises, which requires us to switch between systems instead of performing all tasks from a single location.
Managing the destination for netting on the Netserver using Red Hat Enterprise Linux could be made more user-friendly.
I would like to have enhancements in the data files to help with deployments.
For how long have I used the solution?
I have been using Red Hat Enterprise Linux for over ten years. I started in 2012 using version five.
What do I think about the stability of the solution?
Red Hat Enterprise Linux is stable.
What do I think about the scalability of the solution?
Red Hat Enterprise Linux is scalable, but the scalability is achieved at a different layer compared to adding memory to a virtual machine or container.
How are customer service and support?
Compared to other support departments for Red Hat products, the Red Hat Enterprise Linux support team stands out as one of the fastest, most cooperative, and understanding teams.
How would you rate customer service and support?
Positive
How was the initial setup?
The initial setup is straightforward. In the past, it was complex when Red Hat acquired Ansible because many of the modules were community resources that lacked full support. As a result, creating a playbook to deploy the OS was a painful process, as there was a chance it would not work, and we would not have the necessary support. However, currently, deploying Red Hat Enterprise Linux is easy. We have never deployed only one operating system at a time, but it would take less than one hour to do so.
What other advice do I have?
I would rate Red Hat Enterprise Linux an eight out of ten due to the complexity of its network boost management issue.
We have Red Hat Enterprise Linux deployed in one location.
Red Hat Enterprise Linux is used in our environment to run the application for all of our customers, and only around ten people have access to it.
Red Hat Enterprise Linux requires maintenance for applying new patches, releases, and debugging.
Which deployment model are you using for this solution?
On-premises
Disclosure: PeerSpot 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.
Principal Infrastructure Engineer at a logistics company with 10,001+ employees
Has good security, management, stability, and hardening features
Pros and Cons
- "For us, its security, management, stability, and hardening are most valuable."
What is our primary use case?
My organization has different departments. In my department, we mostly work with containerization. I am using Red Hat Enterprise Linux as a part of OpenShift. I use the basic package and base image of Red Hat Enterprise Linux.
For scale-up in our platform, we use CoreOS as the master, and for the workers, we use the Red Hat Enterprise Linux service. From OpenShift version 4.10 onwards, we cannot use Red Hat Enterprise Linux 7 worker nodes. We were using Red Hat Enterprise Linux 7 worker nodes, so we upgraded to Red Hat Enterprise Linux 8.
For OpenShift, there are some recommendations from Red Hat in terms of what needs to be used for the control plane and what needs to be used for the worker nodes. When you are using CoreOS and Red Hat Enterprise Linux worker nodes, there are some difficulties in managing them. For example, when you upgrade OpenShift, you need to upgrade two times. The control plane is upgraded separately because it uses CoreOS. The control plane has a lot of certificate updates that will in turn be updated on the worker nodes, so you have one restart of all worker nodes, and then when you need to upgrade your worker nodes, there will be one more restart.
Overall, you have two reboots in your production environment, which is an issue, but it is related to your choice of product in your environment. We have this issue because we opted to use Red Hat Enterprise Linux 7 or Red Hat Enterprise Linux 8 worker machines, whereas Red Hat recommends using CoreOS because it is pretty fast in terms of rebooting and functionality. When you upgrade the control plane, that itself will update the worker nodes, so you are done in one shot. When you need to upgrade your Red Hat Enterprise Linux machines, you need to use the Ansible Playbook. You can then upgrade to Red Hat Enterprise Linux 7, 8, or any other version. Regardless of the versions, you can upgrade the operating system and the OpenShift version. For this purpose and for some ad-hoc activities, we are using Ansible Playbooks.
What is most valuable?
For us, its security, management, stability, and hardening are most valuable. All of these features are better in Red Hat Enterprise Linux as compared to Microsoft Windows.
Red Hat Enterprise Linux is very good in terms of risk assessment. It is also good for maintaining compliance. It is better than Microsoft Windows.
What needs improvement?
From the administration perspective, I do not have any issues with Red Hat Enterprise Linux. For me, it is more convenient than Microsoft Windows.
For how long have I used the solution?
My organization has been using Red Hat Enterprise Linux for a long time. They have been using it before I joined the organization.
What do I think about the stability of the solution?
It is pretty good in terms of stability. It is a stable product. I would rate it a nine out of ten in terms of stability because sometimes the packages can have bugs.
What do I think about the scalability of the solution?
Its scalability is good. I would rate it a nine out of ten in terms of scalability.
How are customer service and support?
We never encountered any issues while using OpenShift.
Which solution did I use previously and why did I switch?
I have mostly been working with Red Hat Enterprise Linux.
How was the initial setup?
I have been involved in the deployment of OpenShift. It is pretty straightforward. We just need to get the licensing, and we just need to create a pool for our containers session in Red Hat Satellite. We can do the configuration from there. It does not take long because we are adding the nodes to OpenShift. During the scale-up process, we only need to subscribe to the nodes with the Red Hat subscription. It does not take much time. If we have a good spec, the scale-up would not take much time. It would take less than twenty minutes. It is pretty fast.
In terms of maintenance, when we have the bug report, we need to do the security assessments. Over time, there might be some bugs related to some packages. At that time, if it is critical, we will be scheduling a maintenance activity on our platform.
Red Hat provides high availability from the application perspective. You get high availability when you are using OpenShift, so when you are doing a maintenance activity on the OpenShift side, there would not be any downtime. The high availability is very good. For the end-users, there would not be any application outages if you configure your application with proper replicas. They would not even realize that there is a maintenance activity happening to the underlying workers.
What about the implementation team?
It was implemented in-house.
Which other solutions did I evaluate?
We did not evaluate other solutions. Red Hat Enterprise Linux is the choice of most of the companies.
What other advice do I have?
If you want to integrate with OpenShift or build an OpenShift cluster with the master Red Hat Enterprise Linux and worker Red Hat Enterprise Linux, you can do that, but you need to plan your upgrade or maintenance activities. It would be better if you choose CoreOS for both. CoreOS would be a better choice in terms of maintenance activities or upgrade activities in the future. If you cannot afford that, you can go with the Red Hat Enterprise Linux operating system, but you need to do two upgrades. You first need to upgrade the control plane and then you need to separately update your worker nodes. That is the only thing you need to keep in mind.
I would rate Red Hat Enterprise Linux a ten out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Lead System Engineer at a tech services company with 10,001+ employees
Its consistency in patch upgradation is great
Pros and Cons
- "The most valuable feature is Satellite. Its consistency in patch upgradation is great. For the ten-year lifecycle, we have been able to rely on it and not worry if the patch will break. We do not need additional patching features since it covers everything."
- "The solution's modules feature could be better."
- "The Modules feature is awesome but it could be even better."
What is our primary use case?
We use the solution majorly for JBoss, Apache, Java workload, and Comcast. We also use it for Apache Sattelite to do all the patching and database management. We use it for almost everything. We were a pure RHEL shop, up until recently.
What is most valuable?
The most valuable feature is Satellite. Its consistency in patch upgradation is great. For the ten-year lifecycle, we have been able to rely on it and not worry if the patch will break. We do not need additional patching features since it covers everything.
What needs improvement?
The Modules feature is awesome but it could be even better.
For how long have I used the solution?
We have been using the solution for 25 years.
What do I think about the stability of the solution?
The solution is stable. I have never remotely questioned its stability. The downtime is rare. It is usually a vendor's application issue unrelated to it.
My company only has one complaint; we have been using it for more than seven years out of its ten-year lifespan and have yet to receive any version update. The drivers have become stale. We are trying to upgrade them manually. It would be nice if they had updated the drivers. If they do not update them, the solution will end soon. They should prevent it from crashing every time we try to update it. We are still rolling Ansible to automate some of the functions but, it is complicated to process with a vast sync of firmware and drivers.
What do I think about the scalability of the solution?
The solution is scalable. I am a Satellite owner and we've had scaling issues with it. Those issues are mostly because my company didn't make it scalable in the right way.
They have their own expectations of how to make something highly available. And Satellite doesn't fit into that.
How are customer service and support?
I rate the solution's technical support as nine out of ten, as there is always room for improvement. I never had an issue with the support services. It is good and worth the value.
I don't usually put up a ticket for every minor error. I am an expert and know the technicalities required to resolve the issues. So, whenever I contact them, I expect it to get somewhere. Because most of the time, the executives put more than one problem in the same ticket unrelated to another. It becomes more complex and confusing.
How would you rate customer service and support?
Positive
What was our ROI?
Red Hat Enterprise Linux generates a return on investment. We have everything on it. We have Windows servers for SharePoint and multiple cloud providers as well. In addition, we have OpenShift and Docker Enterprise, and some other open-source applications.
What's my experience with pricing, setup cost, and licensing?
The solution is a good value for money. They keep adding up essential features to the specific subscription plan. I am also not a big proponent of top-level open-source applications as they do not provide support services. Whereas, with Red Hat, I can call them for queries and get answers immediately. In comparison, open source doesn't have that facility. Even if you hire a support vendor, they just give their opinions and try to help but they don't own the project.
At the end of the day, we have a 999.99% reliability of only 20 minutes a year of downtime with Red Hat. It is impossible to get that with open-source vendors as sometimes the applications might break if it doesn't notify about the changes on time. Conversely, Red Hat Enterprise Linux has a ten-year life cycle assurance, so we don't have to worry much. Also, we are in a TAM program. Thus, we can call the support team immediately for any issue.
Which other solutions did I evaluate?
Our organization constantly evaluates other options, as Red Hat Enterprise Linux's cloud version doesn't offer new features. Other than that, we go back and forth using Centralized and Rocky Linux. We prefer the ones we don't have to pay for the licenses.
What other advice do I have?
It has a strong security posture. I did a SELinux contract for my current company. Compared with open-source alternatives, Red Hat Enterprise Linux provides better support services and reliability. Also, we are rolling out a new Ansible platform for insights. It gathers information about how many jobs we have, how long they take to complete, etc.
We need to manage vulnerabilities for a massive base of clients' systems. We don't use open-source apps for it like Red Hat. We have a third-party tool as we straddle different compliances. However, Red Hat is great about security announcements. I can call them anytime for an update as well. But it is challenging to work with the vendor for scanning machines. It does not know how to work with Red Hat packaging version numbers.
I rate the solution a nine out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Senior Platform Engineer at a tech services company with 11-50 employees
A stable and reliable product that provides great support
Pros and Cons
- "The solution is stable and reliable."
- "The solution lacks proper documentation."
What is our primary use case?
Our customers use the product primarily for application servers, authentication apps, and tool servers. If a feature is available in Red Hat Enterprise Linux, they're most likely using it. The product allows us to use applications that run on open-source software. The product also provides on-site support that helps us if we have any issues.
What is most valuable?
The solution is stable and reliable. Being able to move back and forth between systems, products, and middleware is a huge boon.
What needs improvement?
The solution lacks proper documentation. There have been times when I found a document that was supposed to fix an issue, but I realized it was wrong. Then, I would send it to support, and they would fix it.
For how long have I used the solution?
Our customers have been using the solution for six or seven years.
What do I think about the stability of the solution?
The product’s stability is good. It has minimal downtime when it comes to generic deployments. Once you start adding complexity, there are other issues.
What do I think about the scalability of the solution?
The product’s scalability is good. Our customers are able to scale out thousands of instances in minimal amounts of time.
How are customer service and support?
The support team is great. I have friends that work on the support side. I can count on one hand the times I've been dissatisfied with support. Usually, when that happens, it's because it's something that either couldn't be fixed or something too old. I rate the support a nine and a half out of ten.
How would you rate customer service and support?
Positive
How was the initial setup?
My involvement in deployment depends on which systems are being deployed. My organization constantly rolls out new systems via OpenStack, on-premise, or other cloud providers. I help build their base images.
The product’s deployment is pretty straightforward. Everything we build is automated and kicked out from there. Once the base image is built, there's really not much to do.
What was our ROI?
My customers have seen an ROI from the product. They have an on-site support team that is able to help them with issues. It is important to them to have a good team of people to reach back to and to be able to work together.
Which other solutions did I evaluate?
Our customers conduct market research before any purchase. Red Hat Enterprise Linux has consistently been a top contender for us and our customers. We usually support Red Hat Enterprise Linux because our customers choose it.
The biggest push towards Red Hat Enterprise Linux is the ability to have something that's supported and open-sourced. Having transparency is important to my customers. They want to see what they're putting into production, development, and testing. It is important to the customers to see what's going on and what workloads they're handling and to know that what they're putting the workloads on will be solid and secure.
What other advice do I have?
Our customers use the solution on multiple cloud providers, mostly AWS and Azure. Our customers buy a yearly subscription for some equipment, and for short-lived instances, they do on-demand pricing within the cloud provider to buy the ones they offer.
I believe Red Hat Enterprise Linux has helped our organization avoid cloud vendor lock-in. We've been able to pretty reliably and easily lift, shift and redesign our application from on-prem to the cloud. It might not necessarily be a huge benefit for us. However, it is definitely a perk, especially in an environment where we have to go through a certain purchasing cycle and background reviews for everything. It does end up helping us.
As much as I've used Red Hat Image Builder, I really like it. Though, I've only had to build a handful of images out of it. We can't use something like Fedora, where you've got a nightly update. Red Hat Enterprise Linux is tested and reliable. Having something they can work on, develop, and use daily is helpful to our customers.
The sosreports and soscleaner developed in recent years are a huge improvement. My customers tend to be pretty fixed in their ways and what they use, so they continue to work and use things for longer than they should, but that's the beauty of Red Hat Enterprise Linux. It is supported, and we still have the necessary reach back.
Red Hat Enterprise Linux is pretty solid. It's been tested. It has its upstream counterparts that ensure that most of the bugs get worked out, and what makes it down into the final testing is strong and resilient. We've been working on moving workloads between the cloud and data center with the customers. Instead of lift and shifts, we try to redevelop their applications instead of spending $10,000 to give 32 cores in the cloud because they had 32 cores in the system.
We have a fantastic team that works with us and supports us. The team goes out of its way to help find cost savings for both us and our customers.
Overall, I rate the product a nine out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer. Reseller
System Admin for OpenShift at a government with 1,001-5,000 employees
A stable solution that has an extensive knowledge base
Pros and Cons
- "The enterprise support of the product is valuable to us."
- "There's too much information on the support page sometimes."
What is our primary use case?
We use the product as our server's operating system.
What is most valuable?
The enterprise support of the product is valuable to us. When stuff gets difficult, it's nice to have somebody to ask about it.
What needs improvement?
The solution should be updated more with the releases of programming languages. They’re lagging a bit too much. We have a lot of developers complaining about having releases that are too old. For example, if they want Python 3.11, Red Hat Enterprise Linux supports only 3.9. So the product is lagging behind a bit more than our developers would like.
It would be nice if all the features that are available on the cloud, like Image Builder and Insight, would be available on-prem.
For how long have I used the solution?
I have been using the solution for five years.
What do I think about the stability of the solution?
The product is very, very stable and tested. It is like everybody tested everything for five years, and every problem was fixed.
What do I think about the scalability of the solution?
We have never had a problem with the solution’s scalability. We have around 6000 Red Hat Enterprise Linux servers in versions 7, 8, and 9.
How are customer service and support?
Red Hat Enterprise Linux is a lot better compared to all other products. I rate the support an eight or a nine out of ten. There's too much information on the support page sometimes. If we log in to the support pages and try to find information, it's hard to get what we're searching for.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We had a lot of different Linux distributions. The pros of Red Hat Enterprise Linux are that it's the same platform for everybody, and it works for everybody. If you need something very special, you might get issues in Red Hat Enterprise Linux, but you can work around it.
The biggest issue with Red Hat Enterprise Linux is mostly the old packages. It is a con if you have something that you know is a bug that hasn't really been released in Red Hat Enterprise Linux but has been released in the other products.
How was the initial setup?
We do a template, and then we just use it. It's quite great.
What about the implementation team?
We take 30 minutes to deploy the solution. It depends on the size of the machine.
What other advice do I have?
I am using versions 7, 8, and 9. By implementing the solution, we wanted a unified server with a baseline platform that everybody uses. We wanted to have just one server that is enterprise ready.
We do not really have compliances in the same way as an American company has. It's nice to have IT security personnel. You get SELinux from the start. However, we get a lot of support cases because of it. The developers face problems with it. So, we get the security, but we also get lots of support cases. Usually, I end up in the middle of that because I work with support.
We run containers on OpenShift. We run only one platform, so portability isn't a concern. We only have Red Hat Enterprise Linux and OpenShift. We don't really need portability since we are government agencies. Nothing else other than on-prem is allowed for us.
The knowledge base offered by Red Hat Enterprise Linux is extensive. It is a bit hard to find information. However, when you find it, it's good. The packages are a bit old. We have a bit of an issue because of that. But other than that, it's a great operating system.
Overall, I rate the product an eight out of ten.
Which deployment model are you using for this solution?
On-premises
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Cloud Consultant at a tech vendor with 10,001+ employees
Resilient, cost-effective, and has good support
Pros and Cons
- "With regard to security, most companies are moving towards the black box approach and Red Hat. It's much more secure compared to the other vendors."
- "Red Hat Enterprise Virtualization isn't up to the mark as compared to VMware and Hyper-V, but they're moving everything on OpenShift for containers and virtual machines, which is stable. If you go into the virtualization layer, they still need to improve a lot of things, but with regards to OpenShift, containers, Docker, and other things, they are doing well."
What is our primary use case?
We've implemented OpenShift on top of OpenStack. It's a Red Hat OpenStack environment, which is the virtualization layer, and then OpenShift is for the cloud technologies.
It's currently on-prem on a private cloud. In the future, we might utilize a public cloud if the government approves that. Currently, the banking industry isn't allowed to go to the public cloud.
How has it helped my organization?
There is a big move towards digital banking. They prefer to have their solution up and running as soon as possible when the request comes in. They have to have the libraries and all the containers up and running. In a couple of minutes or seconds, they have their whole infrastructure up and running.
With regard to security, most companies are moving towards the black box approach and Red Hat. It's much more secure compared to the other vendors.
What is most valuable?
There's consistency, and it's resilient as well.
With regards to OpenShift, everything is related to cost. If you need a vanilla OS, you have to spend a lot on the licensing that is tagged. You have to spend on the infrastructure and the licensing on a core basis, and whatever is required on your containers, you just have to give minimum hardware specs.
What needs improvement?
Red Hat Enterprise Virtualization isn't up to the mark as compared to VMware and Hyper-V, but they're moving everything on OpenShift for containers and virtual machines, which is stable. If you go into the virtualization layer, they still need to improve a lot of things, but with regards to OpenShift, containers, Docker, and other things, they are doing well.
For how long have I used the solution?
We've been using it for three to four years.
What do I think about the stability of the solution?
Compared to Windows and other operating systems that I've used, it's stable.
What do I think about the scalability of the solution?
I'd rate it a nine out of ten in terms of scalability. We have plans to increase its usage in the future. Our infrastructure will be able to scale. We have a plan to grow it every three years.
How are customer service and support?
Their support is very good. Most of the things are already listed in their knowledge base. Support cases are only raised when you end up with any critical situation. I'd rate their support a nine out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We've used Windows, Solaris, and AIX. The reason for switching to it was that everything is moving to the black box. People want everything to be secured. We got a lot of updates on Red Hat, and it was doing very well in the market.
How was the initial setup?
It was very straightforward. When we did the proof of concept, we had everything ready within two or three days, and then the engineers who came to deploy it did it in a day's time once we had all the infrastructure up and running. This was just for the proof of concept.
With regard to the implementation, they had a timeline, and they did deliver before the timeline.
It has been deployed on Nutanix as well. They are present even in the marketplace for AWS. It's a straightforward installation. They have two categories: UPI and IPI, and the installations are very straightforward, but it requires a lot of expertise if you want to deploy it on a public cloud.
What about the implementation team?
It was implemented by Red Hat. In terms of maintenance, it does require maintenance, but once it is highly available, it's easily done.
What was our ROI?
We've seen an ROI. It has had cost benefits.
It has saved us money. We did a proof of concept with the VMware Cloud Foundation and OpenShift. We saw the feasibility and how fast it can be deployed. There were a lot of considerations. We evaluated it from all perspectives. Compared to the VMware Cloud Foundation, we noted that it was just 50% of the cost. If you go for VMware, they charge you on a core basis, and the licensing costs are huge. You'll have to spend on Microsoft licensing, and then you'll have to spend on the OS as well. Comparatively, it's much cheaper.
What's my experience with pricing, setup cost, and licensing?
We purchased it directly from Red Hat. Compared to open source, it's very pricey, but you get the support, which makes it much better.
What other advice do I have?
You have to deploy it and evaluate it. You can see that there's a lot of difference compared to other operating systems. It also depends on where exactly you're going. There are mainframes and other different places where you can deploy it. Even on the mainframe, it makes a lot of difference.
With Red Hat, there are a couple of things you need to consider while building your infrastructure. You need to have good hardware, and you need to have a compatibility matrix to be able to have a stable environment. It has to be tested in a proper way, rather than deploying it on any box.
In terms of the golden images created by the image builder tool, we have vendors who come with their solutions. They come with the containers, and they deploy them. Most of them are using GitHub, and we just provide the infrastructure. From a technical perspective, there's a solutions department that's into APIs. They handle everything, and we just provide the infrastructure.
Overall, I'd rate it an eight out of ten.
Disclosure: PeerSpot 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:
Buyer's Guide
Download our free Red Hat Enterprise Linux (RHEL) Report and get advice and tips from experienced pros
sharing their opinions.
Updated: January 2026
Product Categories
Operating Systems (OS) for BusinessPopular Comparisons
Ubuntu Linux
Windows Server
Oracle Linux
SUSE Linux Enterprise
openSUSE Leap
Fedora Linux
Oracle Solaris
Google Chrome Enterprise
Alpine Linux
Buyer's Guide
Download our free Red Hat Enterprise Linux (RHEL) Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- What Is The Biggest Difference Between Oracle Linux and Redhat?
- Oracle Linux or RHEL; Which Would You Recommend?
- What Is The Biggest Difference Between RHEL And SUSE Linux Enterprise?
- What are some similarities that you see between Windows 10 and Red Hat Enterprise Linux benchmarks?
- Issue with upgrade of IBM ACM on RHEL 6.10 (hosted on VMWare ESXi-6.7) - looking for advice
- RHEL or SUSE Linux Enterprise?
- Which would you choose - RHEL (Red Hat Enterprise Linux) or CentOS?
- What are the differences between RHEL and Windows 10?
- Oracle Linux or RHEL; Which Would You Recommend?
- What change management solution do you recommend for users to adapt to Windows 10 updates?














