Try our new research platform with insights from 80,000+ expert users

Azure Red Hat OpenShift vs Red Hat OpenShift comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Dec 15, 2024

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

Azure Red Hat OpenShift
Ranking in PaaS Clouds
16th
Average Rating
8.4
Reviews Sentiment
6.7
Number of Reviews
11
Ranking in other categories
No ranking in other categories
Red Hat OpenShift
Ranking in PaaS Clouds
3rd
Average Rating
8.4
Reviews Sentiment
7.0
Number of Reviews
64
Ranking in other categories
Server Virtualization Software (9th), Container Management (9th), Hybrid Cloud Computing Platforms (5th), Agile and DevOps Services (1st)
 

Mindshare comparison

As of March 2026, in the PaaS Clouds category, the mindshare of Azure Red Hat OpenShift is 1.1%, up from 0.6% compared to the previous year. The mindshare of Red Hat OpenShift is 8.2%, down from 12.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
PaaS Clouds Mindshare Distribution
ProductMindshare (%)
Red Hat OpenShift8.2%
Azure Red Hat OpenShift1.1%
Other90.7%
PaaS Clouds
 

Featured Reviews

DeepakMishra - PeerSpot reviewer
CEO, Head of Sales and Business Development at a tech services company with 51-200 employees
Integrated cloud platform has streamlined app delivery and supported certified marketplace products
A potential area for improvement for Azure Red Hat OpenShift is to see managed identity support and ensure that some of the security features are not conflicting with Azure or Azure product features. I am sure in the future it will be more templatized so that we need not depend on Azure security features. Azure Red Hat OpenShift should be independent of Azure security features with respect to container scan and all that. Why would it use an Azure security feature? That is what I find. It is still yet to be GA and commonly available, but that is a strong reason for improvement.
Pratul Shukla - PeerSpot reviewer
Vice President at a financial services firm with 10,001+ employees
Adopting a flexible and efficient approach with noticeable improvements in operational costs and continued challenges in job management
Currently, one of the biggest challenges we face is with services and jobs. For spawning batches, although it has crons, it is not easy to integrate with enterprise systems such as Autosys. The entire company uses Autosys, but we are not able to integrate it effectively. We need intermediate servers to run OC utility commands and initiate the cron job. We have to do a lot of modifications to ensure our batches work properly. With physical or virtual servers, even in AWS, we are able to write and manage multiple jobs. Managing batches in Red Hat OpenShift has been a significant challenge. Integrating third parties is a challenge with Red Hat OpenShift. For example, with Elasticsearch, onboarding itself was difficult, running file beats and dealing with routing issues. It is not straightforward, especially since we have some components in AWS as. AWS has many capabilities that come out of the box and are easier to work with compared to Red Hat OpenShift. Red Hat OpenShift's biggest disadvantage is they do not provide any private cloud setup where we can host on our site using their services. The main reason we went with Red Hat OpenShift was because it is a private cloud, and we have regulatory requirements that prevent us from using public cloud.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"The most valuable features of the solution are accessibility and scalability."
"The solution's support and its automation tool that ensures we are secure and appropriately configured are the most valuable features of Azure Red Hat OpenShift."
"It has a feature to automatically scale up or scale down. If my application is running in peak hours, it will automatically increase."
"It supports AKS and other projects like Kubernetes or EKS."
"As a consulting company, we implement Azure Red Hat OpenShift for our clients, who appreciate its integration capabilities for enhancing cloud operations. While we handle implementation, build processes, and automation, the operational responsibility lies with the customer. The service provides basic processes and support from Red Hat and Microsoft, which benefits clients by allowing them to focus on their business rather than regular operations like cluster upgrades."
"In Kubernetes, when traffic goes out of a pod, it has to have its own IP address. Every service that's going out requires another IP. But with OpenShift, you don't have to deal with any of those IPs because they use NAT."
"The functions and features in Azure Red Hat OpenShift that I have found most valuable are that it is a platform that is baked into Azure, and since it is baked into Azure, it is managed operation by Azure, which takes out the complexity of the infrastructure management and day two operations when compared with on-premise OpenShift."
"Technical support from Red Hat is very good."
"The virtualization of my APIs means I no longer have to pay VMware large amounts of money to only run in-house solutions."
"In terms of implementation, OpenShift is very user-friendly, which is an advantage. We are using it along with GitLab for implementing CI/CD pipelines. That's a feature that other products also have, but in OpenShift, we find it good."
"I am impressed with the product's security features."
"I like OCP, and the management UI is better than the open-source ones."
"The solution provides a lot of flexibility to the application team for running their applications in the container platform, without needing to monitor the entire infrastructure all the time. It automatically scales and automatically self-heals. There is also a mechanism to alert the team in case it is over-committing or overutilizing the application."
"OpenShift is based on Kubernetes and we try to use all the Kubernetes objects of OpenShift. We don't use features that are specific to OpenShift, except internal certificates for the services. The one feature that is missing from Kubernetes and that is really useful in OpenShift is the lifecycle of the cluster and the ease of installation. We use VMware and VMware integration internally with the OpenShift installer, which is very good. With OpenShift it's easy to spin up or scale out a cluster."
"The most valuable feature is the high availability for the applications."
"Its security is most valuable. It's by default secure, which is very important."
 

Cons

"I would like Azure Red Hat OpenShift to be more open to new frameworks and languages. Currently, if I create a pod with Rust, it doesn't work in OpenShift, and I must create a layer of interpretation."
"I would rate the technical support from Microsoft as six."
"There is room for improvement in terms of orchestration. While Azure orchestration offers valuable features, it's worth noting that it may not match the level of orchestration provided by Kubernetes itself."
"Technically, Azure Red Hat OpenShift is fine. However, its marketing could be improved, especially when compared to the robust marketing efforts of Azure, HPE, and Nutanix."
"They need to improve the core licensing model."
"Azure Red Hat OpenShift's support should be improved."
"Regarding room for improvement, there's always room, but it's mainly about Azure itself rather than Azure Red Hat OpenShift. Azure is not as advanced as AWS in terms of supported services. AWS is the leader in this area. However, there's no need for service improvement in Azure Red Hat OpenShift as the service is excellent. I don't need additional features because I can customize it according to the customer's needs."
"The product is expensive."
"OpenShift requires a very expensive and complex infrastructure."
"We experienced issues around desktop security, that stopped us implementing a new feature that had been developed."
"One glaring flaw is how OpenShift handles operators. Sometimes operators are forced to go into a particular namespace. When you do that, OpenShift creates an installation plan for everything in that namespace. These operators may be completely separate from each other and have nothing to do with each other, but now they are tied at the hip. You can't upgrade one without upgrading all of them. That's a huge mistake and highly problematic."
"Areas where Red Hat OpenShift can be improved include the licensing being a bit complex and maybe expensive, as that is something in the hands of the organization's higher management, especially when those licensing agreements are done, and I think Red Hat OpenShift is quite resource-heavy because the control plane and default monitoring stack consume significant resources, meaning for small clusters, a large percentage of compute goes just to running Red Hat OpenShift itself, not our apps."
"Room for improvement is around the offerings that come as a bundle with the container platform. The packaging of the platform should be done such that customers do not have to purchase additional licenses."
"Managing batches in Red Hat OpenShift has been a significant challenge."
"The interface could be simplified a bit more."
"OpenShift could be improved if it were more accessible for smaller budgets."
 

Pricing and Cost Advice

"Azure Red Hat OpenShift is not a low-price solution; it's expensive. Pricing depends on the strategy and whether you buy it directly from Red Hat or the Azure portal. Additionally, some customers may need a complete disaster recovery solution, which requires additional licensing and software products for implementation, such as backups."
"It is expensive compared to a similar product."
"I rate the product's price an eight on a scale of one to ten, where one is cheap, and ten is expensive."
"Compared to other cloud environments like Amazon or Google, Azure Red Hat OpenShift is an expensive solution."
"I don't deal with the cost part, but I know that the cost is very high when compared to other products. They charge for CPU and memory, but we don't worry about it."
"It's important to start small because the solution is scalable. We can build our cluster and look at the bundle option, not the external subscriptions. Talking to the people at Red Hat can save us money."
"We use the license-free version of Red Hat Openshift but we pay for the support."
"The licensing cost for OpenShift is expensive when compared to other products. RedHat also charges you additional costs apart from the standard licensing fees."
"This solution is fairly expensive but comes at an average cost compared to other solutions in the market."
"The price depends on the type and the nature of the organizations, along with the types of projects that are of considerable range."
"The pricing for OpenShift includes support and licensing, which costs approximately $400."
"The cost is quite high."
report
Use our free recommendation engine to learn which PaaS Clouds solutions are best for your needs.
884,873 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
19%
Manufacturing Company
14%
Computer Software Company
10%
Comms Service Provider
7%
Financial Services Firm
23%
Manufacturing Company
10%
Government
7%
Computer Software Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise3
Large Enterprise7
By reviewers
Company SizeCount
Small Business17
Midsize Enterprise4
Large Enterprise43
 

Questions from the Community

What is your experience regarding pricing and costs for Azure Red Hat OpenShift?
The pricing for OpenShift is similar to other solutions like Docker ( /products/docker-37146-reviews ) Studio. The plans with ARO and AWS are standard in the market. However, using OpenShift on-pre...
What needs improvement with Azure Red Hat OpenShift?
A potential area for improvement for Azure Red Hat OpenShift is to see managed identity support and ensure that some of the security features are not conflicting with Azure or Azure product feature...
What is your primary use case for Azure Red Hat OpenShift?
My use case for Azure Red Hat OpenShift is for an employee engagement application and HR, and I have also used it for an agentic bot.
How does OpenShift compare with Amazon AWS?
Open Shift makes managing infrastructure easy because of self-healing and automatic scaling. There is also a wonderful dashboard mechanism to alert us in case the application is over-committing or ...
Which would you recommend - Pivotal Cloud Foundry or OpenShift?
Pivotal Cloud Foundry is a cloud-native application platform to simplify app delivery. It is efficient and effective. The best feature is how easy it is to handle external services such as database...
What needs improvement with OpenShift?
Areas where Red Hat OpenShift can be improved include the licensing being a bit complex and maybe expensive, as that is something in the hands of the organization's higher management, especially wh...
 

Overview

 

Sample Customers

Information Not Available
UPS, Cathay Pacific, Hilton
Find out what your peers are saying about Azure Red Hat OpenShift vs. Red Hat OpenShift and other solutions. Updated: March 2026.
884,873 professionals have used our research since 2012.