Try our new research platform with insights from 80,000+ expert users
reviewer1947159 - PeerSpot reviewer
CTO at a tech services company with 11-50 employees
Reseller
Exceptional support, helpful for compliance, and fantastic for containers
Pros and Cons
  • "The Red Hat support is most valuable. My team and I are really good at Linux, and we can do almost everything in any kind of Linux solution, but sometimes, we have a really nasty problem, and the Red Hat engineering support at the third level has been fantastic. They know how to fix almost everything. The reason why I pay so much money to them is to have this kind of service and assurance."
  • "Network virtualization resources could be better. When you have any kind of trouble with network virtualization, such as with OVS, which is like a switch in a virtual environment, it takes many hours to find what is happening. Other vendors, such as VMware, and even other Linux implementations for network virtualization have better resources. It is much easier to escalate, and there is better documentation."

What is our primary use case?

I use it for almost everything. I run a company in South Texas and Mexico. We are a cloud service provider, and we have implementations for almost everything. We are using it for websites, virtualization, orchestration, and containers, and we are also using it a lot for telecommunications. We use almost all of its features.

We have many versions. We have versions 8, 9, 9, 9.1, 9.2, etc. 

How has it helped my organization?

When we implemented all the security frameworks with RHEL three years ago, that was the first time we had a non-issue audit. It was a great implementation.

It helps with the headcount. With the kind of orchestration and automation that we have, we don't need a lot of engineers. We can have fewer engineers on site.

There is reliability. We can rely not only on their operating system but also on their server. Red Hat not only has operating systems; it also has many different servers.

It helps to achieve security standards certification. It is one of the most important things that I do every single day. We need to comply with a lot of frameworks of security, such as ISO2701, ISO2717, ISO2721, PCI compliance, and HIPAA for the health sector. We also have some local compliance requirements. For example, in Texas, there is one for financial entities, and in Mexico, there are several based on GDPR. It is very important for us.

It is helpful when it comes to building with confidence and ensuring availability across physical, virtual, and cloud infrastructures. There are many features to ensure or enforce high availability.

It helps us to centralize development with OpenShift. We don't do a lot of DevOps, but we have a supply chain where everything goes to the on-premises cloud, and then it is pulled to the public cloud.

What is most valuable?

The Red Hat support is most valuable. My team and I are really good at Linux, and we can do almost everything in any kind of Linux solution, but sometimes, we have a really nasty problem, and the Red Hat engineering support at the third level has been fantastic. They know how to fix almost everything. The reason why I pay so much money to them is to have this kind of service and assurance.

Containers are the strongest feature that they have. In terms of the quality, between VMs and containers, Red Hat with OpenShift is fantastic. I have more than a million containers right now in my cloud, and it works fantastically.

What needs improvement?

Network virtualization resources could be better. When you have any kind of trouble with network virtualization, such as with OVS, which is like a switch in a virtual environment, it takes many hours to find what is happening. Other vendors, such as VMware, and even other Linux implementations for network virtualization have better resources. It is much easier to escalate, and there is better documentation.

I don't use Ceph, which is their software-defined storage, because they don't have the best price. It doesn't make sense when you compare it in terms of the hardware cost, better performance, and better capabilities. That's my main complaint at any meeting with Red Hat. I want to use Red Hat Ceph, but it costs so much money.

Buyer's Guide
Red Hat Enterprise Linux (RHEL)
May 2025
Learn what your peers think about Red Hat Enterprise Linux (RHEL). Get advice and tips from experienced pros sharing their opinions. Updated: May 2025.
857,028 professionals have used our research since 2012.

For how long have I used the solution?

I have been using it for about 20 years.

What do I think about the stability of the solution?

If you have the correct hardware, it is stable, but if you do not, you will have a problem any time soon.

It is reliable. If you don't know how to secure your Linux implementation, Red Hat can do it for you with two or three simple clicks, and you will be very secure without any kind of knowledge.

What do I think about the scalability of the solution?

It is scalable. It is not the most scalable in the Linux area, but for 99% of the companies, it is scalable enough for any kind of workload.

We have plenty of clusters, and we probably have more than 400 servers. We are a private cloud solution provider. We don't have anything in the hyper-scale, such as AWS, Azure, etc. We own everything: the data center servers, racks, networking, and storage. That's our competency, and this way, we can provide a better solution to the kind of customers we are focused on.

We have three different locations: one in the states and two in Mexico. At each location, we have at least three different clusters for three different market verticals. We have one for the financial, one for the healthcare system, which has a lot of compliance requirements, and one for the general public, which doesn't have too much sophistication.

We plan to increase its usage, but it is not my decision. If I sell more, I will buy more.

How are customer service and support?

They are exceptional. We have a lot of experience in these matters. Usually, when we have any kind of issue, it is a really difficult one, and I need to talk to somebody at level two or three in the support area. They skip the line for us because we send everything perfectly documented to open the PR. They put us in touch with the best engineer to solve the issue. If the engineer isn't able to understand what is happening, usually, he calls the RHEL developer or engineer that handles that part of the code. They are usually able to fix a complex problem in less than eight hours.

Their support is fantastic. I have dealt with many different vendors, but Red Hat is the only one that does it in this way. They do it in a simple and fast way. They understand you, and they are willing to help you and fix everything. If you have a problem or situation that is causing downtime for the customer, they understand that it has an impact on your business, and they are affecting the revenue of the company. They are really committed to fixing it as soon as possible. I would rate them a 10 out of 10.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

We use RHEL and Canonical. We have some SUSE implementation in the Linux area. In hypervisors, we use VMware and Hyper-V. So, we are in many different technologies, and we are not always on RHEL. RHEL has almost 45% of all our hardware. It is the biggest one, but we use almost all the solutions. In terms of security, Red Hat and Canonical have almost the same level of security.

How was the initial setup?

I am no longer involved in its deployment. I last deployed it about four years ago.

In terms of maintenance, every server requires some kind of maintenance, but we have everything automated. We don't put any effort into it. 

What about the implementation team?

We have 8 to 12 people for deployment and maintenance. They handle the deployment and change of the environment in the data center. For DevOps, I have another team of probably 30 people. They develop solutions for customers.

What was our ROI?

We have definitely seen an ROI. The return on investments comes in the 14th or 15th month.

What's my experience with pricing, setup cost, and licensing?

For the basic operating system, its price is fair. It is not cheap, and it is also not expensive. For the OpenShift or OpenStack implementation, the cost is a little higher than what I would expect, but it is doable. For a storage solution, it is almost impossible to pay.

In comparison to open-source competitors, RHEL has the most cost-effective open-source subscription model. The way I pay for everything, such as Ubuntu or RHEL, is very similar. When you compare how much money I put in for a customer, in terms of licensing, or even support, my margins with RHEL are really good. If I compare it with VMware or Hyper-V, which are not open source, the difference is totally insane.

Which other solutions did I evaluate?

I am a vendor-agnostic solution provider. If my customer needs something with RHEL or something that's specifically with another vendor, I use that. If they don't know, or there is a new implementation, I surely send everything to the RHEL implementation. In the end, this is not my decision. It is a market decision. If my customer is telling me that they should be on RHEL, I will bring in RHEL for them.

What other advice do I have?

I would advise paying for the enterprise-level support at least for the first year.
For sure, it is expensive, but it would be helpful. With experience, you can downgrade to the second level.

We have had some issues with container compression that broke everything. So, I don't recommend using it if you don't know how to fix everything.

The biggest lesson that I've learned from using this solution is to read before starting the implementation.

I would rate it a 9 out of 10 because there is nothing perfect.

Disclosure: My company has a business relationship with this vendor other than being a customer: Reseller
PeerSpot user
reviewer1006923 - PeerSpot reviewer
Systems Architect at a university with 1,001-5,000 employees
Real User
It's easier to maintain and more agile than our previous solution
Pros and Cons
  • "RHEL been stable, and we could do anything we wanted with it. OpenShift is a concise environment, and RHEL is one of the most stable Linux distros on the market."
  • "The only issue for us was the cost. RHEL is expensive."

What is our primary use case?

In the past, we ran almost everything on Red Hat Enterprise Linux, but now we use it for applications that are only supported on Red Hat Enterprise Linux, LDAP servers, and other stuff that runs better on Red Hat Enterprise Linux. We've migrated the rest to Ubuntu. We don't use it for containerization yet, but I'm learning about OpenShift. 

We are considering Red Hat Enterprise Linux for some AI projects at the university, some for researchers and research groups, and others for administration or student enrollment. There are many opportunities to use AI. 

How has it helped my organization?

Red Hat Enterprise Linux has made us more agile, and more applications were ready-made for Linux. It was also easier to maintain the environment. 

It enabled us to centralize development, but we had some issues with cost, so we migrated off. We use the Linux security heavily.  I'm unfamiliar with the new security stuff incorporated in Red Hat Enterprise Linux, but SELinux and all the security features are good. It doesn't particularly reduce risks, but there are some added layers of security for internet-facing applications we like

What is most valuable?

Red Hat Enterprise Linux been stable, and we could do anything we wanted with it. OpenShift is a concise environment, and it is one of the most stable Linux distros on the market. 

What needs improvement?

The only issue for us was the cost. Red Hat Enterprise Linux is expensive.

For how long have I used the solution?

We have used Red Hat Enterprise Linux for a long time. We started using it on version 4, and now we are on 7, but we migrated most of our environment to Ubuntu a few years ago.

What do I think about the stability of the solution?

It is stable and mature.

What do I think about the scalability of the solution?

Red Hat Enterprise Linux can scale to fit our needs. 

How are customer service and support?

I rate Red Hat support nine out of 10. I was happy with it. Their expertise and technical knowledge were good. It was one of the best support experiences I've had. 

How would you rate customer service and support?

Positive

How was the initial setup?

When Oracle acquired Sun, we migrated from Sun Solaris to Red Hat Enterprise Linux. It wasn't easy, but it was a light effort.

What's my experience with pricing, setup cost, and licensing?

Red Hat Enterprise Linux is expensive.

What other advice do I have?

I rate Red Hat Enterprise Linux nine out of 10. If you're purchasing commercial Linux, I would look into Red Hat Enterprise Linux because it's highly stable and mature overall. It's a true enterprise OS. 

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.
Flag as inappropriate
PeerSpot user
Buyer's Guide
Red Hat Enterprise Linux (RHEL)
May 2025
Learn what your peers think about Red Hat Enterprise Linux (RHEL). Get advice and tips from experienced pros sharing their opinions. Updated: May 2025.
857,028 professionals have used our research since 2012.
reviewer2399145 - PeerSpot reviewer
Ansible Specialist at a energy/utilities company with 5,001-10,000 employees
Real User
An enterprise solution for standardization, compliance, and great support
Pros and Cons
  • "The enterprise aspect of it is valuable. There is security patching, security scanning, and compliance. There are all kinds of features around managing and keeping it up-to-date and secure. Everything is in a box for us from Red Hat which makes it very easy to manage them."
  • "It is constantly improving. It is important to continue to improve."

What is our primary use case?

When we are looking for Linux servers or developers need Linux, we have standardized around Red Hat Enterprise Linux. We do not use Ubuntu or any random flavors of the day. If it is a Linux deployment, it is Red Hat.

How has it helped my organization?

It helps with standardization. If someone comes to us and requests a Linux server, we have one product offering. We have a couple of different flavors of it, but people know what they are getting from us. The consistency, reproducibility, and standardization of it have been fantastic.

We are using Red Hat Enterprise Linux on-prem and on the cloud. We have it in Azure, VMware, and on-prem. We have it on bare metal. It is all over the place. Our operations are simpler, more efficient, and easier to handle. Our Linux team now supports one OS rather than a whole bunch of flavors that everyone has brought in. It has just made things more efficient and simplified.

Red Hat Enterprise Linux has enabled us to centralize development. Those developers are now developing on Red Hat Enterprise Linux. Previously, we had people who were developing on Ubuntu and trying to push Ubuntu to production, but we did not necessarily support it. Red Hat Enterprise Linux gave us a clear path to production. Our developers also get an easier experience. They know which OS to use and what they are using from day to day. There is less confusion for developers.

We are using Red Hat Enterprise Linux for containerization projects. It has helped with simplification. We do not have to create too many of our own custom container definitions and do our own thing. We use minimal images and whatever is provided is supported under our subscription. It simplifies things and puts guidelines around things.

Red Hat Enterprise Linux's built-in security features are good when it comes to risk reduction, business continuity, and maintaining compliance. We use Red Hat Satellite to manage our Linux. That makes it all very simple. There is a feature called OpenSCAP. We use it for security scanning. All the features that they provide on top of the base OS make it very easy to manage.

The portability of applications and containers built on Red Hat Enterprise Linux is great for keeping our organization agile. We know we can rely on that middle layer. We can start with the container and then build on top of that. Having a solid and standard foundation makes it all easy to do.

What is most valuable?

The enterprise aspect of it is valuable. There is security patching, security scanning, and compliance. There are all kinds of features around managing and keeping it up-to-date and secure. Everything is in a box for us from Red Hat which makes it very easy to manage them.

What needs improvement?

It is constantly improving. It is important to continue to improve. That is another reason I like it. They are using newer kernels, which gives us access to newer hardware. They are already doing that. I cannot pretend to tell them what to do better. They can just keep on doing what they are doing.

For how long have I used the solution?

Personally, I have been using it for about 12 years. I have only been with my company for about four months, but I know they also have been using it for years.

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

It is scalable. They define scalability. I am a basic user. I just deploy more VMs if I need to. It is easy to do. Its scalability is great.

How are customer service and support?

They are great. I would rate them a ten out of ten. A big selling point is that when you submit a support ticket, you know you are reaching out to experts. That is great, and that is one of the primary reasons we went with Red Hat.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

In my company, they were using AWX for automation, and we moved them to AAP. For Linux, I was a part of a project to migrate some of the other operating systems over to Red Hat Enterprise Linux. I am on the tail end of the move or standardization to Red Hat Enterprise Linux.

There were a lot of Ubuntu operating systems in the environment, but they had challenges standardizing around it. There were different versions. There was also CentOS, but it was old CentOS. They are naturally moving that to Red Hat Enterprise Linux.

The support and the standardization around it were the main reasons for going for Red Hat Enterprise Linux. CentOS is more of a community thing now, whereas we can call Red Hat and they help us with everything. The support and the enterprise features we needed pointed at Red Hat Enterprise Linux rather than CentOS. It is a better choice for production.

How was the initial setup?

We deploy them from AAP and then we deploy them into VMware. We deploy them into Azure, which is our main provider. We do that all orchestrated through Ansible and Satellite.

What about the implementation team?

We have outsourced support. TCS is a general contractor, but for Red Hat deployments, we generally go with Red Hat Consulting. We just finished a consulting engagement with them for that. I know they have used them in the past prior to me being here. We generally just use Red Hat Consulting.

What was our ROI?

We have standardization. I know what I am walking into every day. I know there is support behind it. There is the support of Red Hat and the community behind it. I feel confident using Red Hat Enterprise Linux. I might use other Linux operating systems at home, but a lot of the time, there is no documentation for them. There might be three guys in a forum from ten years ago who may have talked about my problem. With Red Hat Enterprise Linux, when I am going to work, I know what I am walking into. I can feel safe and assured using something industry standard that works, and I can get help with it very easily. It makes life a lot easier.

Our total cost of ownership across our enterprise landscape has gone up because we were using a lot of mixed and free open-source solutions. However, there was an extra cost of operations and extra cost of hiring for specialized skills and things like that. With the Red Hat portfolio, I feel that we spend more on subscriptions, and we save in terms of efficiency and operations. I feel that we spent some money to save money on the backend, and I hope that is how it ended up.

What's my experience with pricing, setup cost, and licensing?

I do node counts for the Red Hat Enterprise Linux system. I am gathering data for our decision-makers about how many nodes we need and how many things we need. Once or twice a year, they ask us to true up and find out how many nodes we are using and what the actual consumption is. I then report that, and then the account team usually works on the money part of it. I just work on the count.

What other advice do I have?

We use Red Hat Insights a little bit. I am more of an Ansible guy, and we use Red Hat Insights for our licensing and a few other things. We have not been using Red Hat Insights as much as we wanted to. I know that on the Linux side, they are using it a lot for license count, monitoring, and other things.

I feel we are underutilizing Red Hat Insights. Our account executive has shown how it works and where it is, but we have not committed to it yet. That is coming soon. As we gain more Red Hat products and standardize more, we will have to rely on a single pane like that, so we will be using it more. I know that Red Hat Insights provides vulnerability alerts and targeted guidance, but we are not utilizing it right now.

To a colleague who is looking at open-source, cloud-based operating systems for Linux instead of Red Hat Enterprise Linux, I would say to go for whatever they find to be the best. My standard for an enterprise solution is Red Hat Enterprise Linux. It works very well, but they have to make sure that it fits their use case. Fortunately, Red Hat Enterprise Linux fits most use cases. They might end up there, but if there are licensing or cost restrictions, there are other free options, such as CentOS. The ecosystem of Red Hat Enterprise Linux is healthy, so I would recommend it, but if they want to use something else, they need to come up with all the standards around that.

I would rate Red Hat Enterprise Linux a ten out of ten. It is my preferred enterprise operating system. Everywhere I go, they are using it. It has been great. There are no complaints.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
DevOps Engineer at CipherTV Corp.
Real User
Top 5
Offers role-based access and the ability to seamlessly connect multiple systems with ease
Pros and Cons
  • "The Red Hat Linux comes with Anaconda, a fascinating tool that is useful if I need to connect multiple systems. I also like role-based access."
  • "Red Hat Enterprise Linux is a little expensive for some customers who don't have the budget. It depends on the client. They can save money by not purchasing some of the added packages and services. If the client has a budget of $10 million, we can go for the whole bundle."

What is our primary use case?

I work as a consultant for a bank. They were using another type of Linux and facing some scripting issues. We are using Ansible for infrastructure, but they depend on different languages. In this fintech use case, the bank performs transactions between two banks. The transactions were getting stuck, but they detected that the money had been transferred. 

The money comes from the bank. They transport it from the cloud and deliver it to the channels like Visa, MasterCard, etc. The national bank is also involved at that stage, so there is a pause. When we are using auto-scaling, it requires a small amount of time, so your application will have an error. This is a millisecond process. That is the duration. We were looking for issues like bank fraud. You need to conduct an analysis and restart the service. The data is on Red Hat Linux, and we use EKS for containerization. 

We have a hybrid solution combining AWS with an on-premise environment. Moving data to the cloud requires a stable connection because we have multiple systems on-premises and on the cloud. This platform helped us communicate among multiple clouds and our private cloud network. 

How has it helped my organization?

Using Red Hat Enterprise Linux enables us to subscribe to other Red Hat services from our portal. We can connect to Satellite with single sign-on logins. We can use the Spring CLI call and the Docker hub. We have a direct subscription.  

Red Hat Enterprise Linux has helped us avoid cloud vendor lock-in. We could easily migrate between cloud services from AWS to Azure if we wanted to. Everything is an SCL, so we could deploy the same thing on another cloud. It's highly useful. We can make a script and move the entire infrastructure. 

What is most valuable?

The Red Hat Linux comes with Anaconda, a fascinating tool that is useful if I need to connect multiple systems. I also like role-based access. 

What needs improvement?

Red Hat Enterprise Linux is a little expensive for some customers who don't have the budget. It depends on the client. They can save money by not purchasing some of the added packages and services.  If the client has a budget of $10 million, we can go for the whole bundle. 

For how long have I used the solution?

I have used Red Hat Enterprise Linux for four or five years.

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 it depends on the deployment. 

How are customer service and support?

I rate Red Hat support 10 out of 10. I'm a big fan. 

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I have used Ubuntu, which has its own cloud service. Red Hat Enterprise Linux is a better option if the client has a budget. Red Hat Enterprise Linux can be certified and meet compliance requirements. 

How was the initial setup?

Deploying Red Hat Enterprise Linux is straightforward, but the complexity and time required depend on whether we are deploying on a virtual machine or a desktop. If we have the correct documentation, the total process can be completed in three to five days.

I have used the Image Builder Tool, but in the latest deployment, I pulled down the repository from the Docker hub. We use our own XML file and create the repository. It's a two or three-day design process for Red Hat Linux. We need one data resource for that process and a second engineer on the support side if we want to set up more servers from their on-site services.

What's my experience with pricing, setup cost, and licensing?

It's affordable, but everything costs money. At the same time, everything adds value for our clients.  For example, I was working on a machine-learning project, and they needed more team resources, and all the projects used computing power. By running multiple clusters, the client exceeded the rate for that data. We buy services from AWS, the Azure Marketplace, or directly from Red Hat. 

What other advice do I have?

I rate Red Hat Enterprise Linux nine out of 10. I recommend buying the services in a package if you can afford it. If the client doesn't have the budget, we can find alternatives. It depends on the client's needs. 

Disclosure: My company has a business relationship with this vendor other than being a customer: partner
PeerSpot user
reviewer2298882 - PeerSpot reviewer
System Administrator at a government with 501-1,000 employees
Real User
Rock solid, secure, and good documentation and support
Pros and Cons
  • "I like most of the features. I like its stability. I like its views. It provides a very stable environment."
  • "The upgrade procedures are a little bit cumbersome. It would be nice if they are not because every three or four years we have to update, and I find that to be a bit on the cumbersome side. We have been able to automate most of it, but we still run into things where the job does not finish. There are things that require additional steps. There are things that need to be removed and that always require manual intervention."

What is our primary use case?

We have an older environment with a lot of servers. They are development servers for a lot of in-house development. We have a lot of things. We have Ruby on Rails, Java, and a lot of Oracle applications

Red Hat Enterprise Linux is mostly on-prem in my current job. In my previous jobs, we have had it on AWS or Azure.

How has it helped my organization?

Red Hat Enterprise Linux's built-in security features are good when it comes to simplifying risk reduction and maintaining compliance. It is something that they do very well. It is one of the reasons why we like running it. It is rock solid in all areas. Red Hat does a really good job of keeping on top of vulnerabilities and making the patching process easy.

Red Hat Enterprise Linux has impacted our uptime and security. We have had no breaches, and our systems are usually up.

Red Hat Enterprise Linux has not yet enabled us to achieve security standards certification because that is not a requirement for where we are, but I am pretty confident that we would meet those standards. Our security teams are usually chasing problems on the other side of the house.

What is most valuable?

I like most of the features. I like its stability. I like its views. It provides a very stable environment. There is not a lot of downtime. There are not a lot of issues. Primarily, we are deploying things and configuring things, and occasionally, we add new things for developers as needed, but it does not require much troubleshooting or break fixing. That is rare.

The knowledge base offered by Red Hat Enterprise Linux is another thing I like about it. It is particularly easy to find an answer to your problem online. There is very good documentation, very good user communities, and good support when you need it.

What needs improvement?

The upgrade procedures are a little bit cumbersome. It would be nice if they are not because every three or four years we have to update, and I find that to be a bit on the cumbersome side. We have been able to automate most of it, but we still run into things where the job does not finish. There are things that require additional steps. There are things that need to be removed and that always require manual intervention. I do not know how they can get rid of that, but it is cumbersome in an environment where you have hundreds or thousands of servers.

For how long have I used the solution?

I have been using Red Hat Enterprise Linux for ten years.

How are customer service and support?

I would rate their support a nine out of ten. I just do not give tens. I am sure there are some areas where they can improve, but they are good. They are responsive.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

I have got experience with Windows and Solaris before that. Red Hat Enterprise Linux is my favorite. With Solaris, that stream stopped a long time ago, but Red Hat Enterprise Linux has all of the nice things about it, and they have continued to develop and build many new things. For instance, when you had to patch on a Solaris box, you had to take the server down into single-user mode and apply the patching. I like it better than Windows in every way. It is more intuitive to me. I like that I can do more things from the command line. It is easier to automate things.

How was the initial setup?

I have been involved in the upgrades and some migrations for migrating things from Solaris. We also had CentOS, which was converted to DevStream, so we have had to change those to Red Hat. The upgrades and migrations were not terribly difficult. Usually, the tools were there. We called support when we ran into problems, but for the most part, it worked.

I have used Convert2RHEL. It was a bit helpful. It did the job.

We mostly use Ansible for deployment, patching, and managing the system in general. Our experience has been good. I am looking at some of the newer things they have at the conference that we have not had a chance to play with, but it meets our needs.

What was our ROI?

We have seen a return on our investment. We are able to do what we need to do without any problems or interruptions, and we are able to do it quickly.

What's my experience with pricing, setup cost, and licensing?

For me, it is not too bad, but my company pays the bill, so I do not worry too much about it. 

What other advice do I have?

I would rate Red Hat Enterprise Linux a nine out of ten.

Disclosure: My company does not have a business relationship with this vendor other than being a customer.
PeerSpot user
reviewer2298825 - PeerSpot reviewer
Senior Software Engineer at a energy/utilities company with 501-1,000 employees
Real User
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?

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.

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. 

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.
PeerSpot user
Principal Infrastructure Engineer at a logistics company with 10,001+ employees
Real User
Top 5
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.
    PeerSpot user
    reviewer2197374 - PeerSpot reviewer
    Solution Architect at a consultancy with 10,001+ employees
    Real User
    Provides a cohesive ecosystem and has an excellent support team
    Pros and Cons
    • "The solution's operating systems are phenomenally resilient and stable. The good part is that Red Hat has backing and support. Also, combined with IBM, it gives more confidence to my customers."
    • "The solution's ecosystem is good but it would be better to create cohesive components in all of the development tools."

    What is our primary use case?

    RHEL is a phenomenal operating system for three primary reasons: 

    • Support compared to the rest of the Linux ecosystem
    • Cohesive ecosystem 
    • Application platform

    The combination of these three aspects has proven to me from an advising perspective that it is key in decision-making.  

    How has it helped my organization?

    Our clients purchase the use cases via cloud provider and hyper-scale. It's a combination of both. Mostly, new clients prefer going for hyper scalers. Whereas the clients with Red Hat licenses, predominantly those from the banking sector, transfer the licenses to the cloud depending on their hyper scaler plan.

    The main benefits my clients have seen are the supportability, maintenance of the operating system, security, and the ecosystem that ties it all together.

    What is most valuable?

    The solution has a phenomenal operating system. Its support features are best compared to the rest of the Linux ecosystem. Generally, applications don't rely on operating systems per se. When combined with the container ecosystem, security is the paramount feature that is most asked for.

    The problems our clients try to solve by implementing Red Hat Enterprise Linux vary. The main ones include containerization, cloud transformation, and visual transformation in terms of how you get to the cloud in a hybrid mode. The key aspect that I give advice about is how for the operating system in terms of the scalability to bridge the cloud to the on-prem world, so where they could have the OpenShift ecosystem that it runs into and helps them manage both systems together. 

    The solution's operating systems are phenomenally resilient and stable. The good part is that Red Hat has backing and support. Also, combined with IBM, it gives more confidence to my customers.

    What needs improvement?

    The solution's ecosystem is good but it would be better to create cohesive components in all of the development tools. 

    A developers' hub feature would help. 

    OpenShift already provides excellent visibility, but bridging the gap with Kubernetes would be key because Red Hat Enterprise Linux drives OpenShift.

    For how long have I used the solution?

    I'm a big open-source user. I've been using different forms of Linux for quite some time. For my enterprise purpose, I use the RHEL for other purposes and a few other different Linux operating systems. We have been using Red Hat Enterprise Linux for more than ten years.

    What do I think about the stability of the solution?

    I have experience working with Ubuntu, Fedora, Canonical, etc. From that perspective, the solution's stability is good. The security feature plays a key role in terms of the pace at which it receives updates for operating systems to maintain it.

    What do I think about the scalability of the solution?

    In terms of the architectural perspective, the nature of the solution is scalable.

    How are customer service and support?

    The solution's technical support is very good. My clients generally manage it, and I have received positive feedback. They have a responsive support organization to communicate with.

    Which solution did I use previously and why did I switch?

    I have used Canonical and Ubuntu. In comparison with Red Hat Enterprise Linux, Ubuntu's ecosystem consists of multiple operating systems and container platforms like MicroK8s. The partnership with hyper scalers in terms of deployment is one of its benefits as well. On the flip side, it has some drawbacks regarding licensing and export control, where Red Hat shines well.

    What's my experience with pricing, setup cost, and licensing?

    The solution's pricing and licensing are good. Although the open-source space is becoming more competitive, Red Hat brings value in terms of support. At the same time, different operators like Canonical Kubernetes are catching up. Thus, the price would become the differentiation factor regarding packages for support, and container ecosystem combined with Ansible. All these key elements would add more value to the pricing.

    What other advice do I have?

    The solution's key element is its cohesive ecosystem between hybrid and cloud environments. It helps clients such as giant banks create a single space for managing workloads in different hyper scalers. This way, it helps in cost management and visibility. It creates a single platform to manage work. It helps in saving costs, especially with subscription plans. It provides them with a consistent cost structure. Also, being an open-source solution has benefits that fit within the ecosystem.

    I rate it an eight out of ten, primarily for the support and licensing terms. It helps some of our enterprise clients navigate open-source licensing and export control complexities.

    There are areas of improvement, such as the cycle of updates and the ecosystem as a whole. Also, the elements like Ansible are priced separately. For automation, there is an opportunity to combine everything. Even though they are different products, they shouldn't be charged separately from the ecosystem perspective.

    Which deployment model are you using for this solution?

    Hybrid Cloud
    Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
    PeerSpot user
    Buyer's Guide
    Download our free Red Hat Enterprise Linux (RHEL) Report and get advice and tips from experienced pros sharing their opinions.
    Updated: May 2025
    Buyer's Guide
    Download our free Red Hat Enterprise Linux (RHEL) Report and get advice and tips from experienced pros sharing their opinions.