No more typing reviews! Try our Samantha, our new voice AI agent.

Kubernetes vs Replicated comparison

Why PeerSpot?
 

Comparison Buyer's Guide

Executive Summary

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

Kubernetes
Ranking in Container Management
3rd
Average Rating
8.6
Reviews Sentiment
7.0
Number of Reviews
82
Ranking in other categories
No ranking in other categories
Replicated
Ranking in Container Management
17th
Average Rating
10.0
Reviews Sentiment
5.0
Number of Reviews
1
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2026, in the Container Management category, the mindshare of Kubernetes is 10.0%, up from 5.9% compared to the previous year. The mindshare of Replicated is 0.6%, up from 0.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Container Management Mindshare Distribution
ProductMindshare (%)
Kubernetes10.0%
Replicated0.6%
Other89.4%
Container Management
 

Featured Reviews

RV
DevOps Engineer at a tech services company with 11-50 employees
Automated deployments and self-healing have transformed how I run reliable chat services
For improvements, I would definitely suggest some enhancements to Kubernetes. While Kubernetes is very powerful, there are still a few areas where it could be improved. Our challenge is the learning curve and operational complexity. For new team members, concepts such as networking, RBAC, Ingress, and troubleshooting distributed systems can take time to understand. Better built-in onboarding tools or simplified abstractions would help. Another pain point is debugging and observability. While kubectl provides good basic visibility, deep debugging across multiple services, pods, and nodes often requires external tooling such as Prometheus, Grafana, or centralized logging. Stronger native observability features would be very helpful. Networking and Ingress configuration can also be complex, especially when dealing with certificates, routing rules, and cloud-specific integrations. A more standardized experience across environments could reduce operational overhead. From a cost perspective, managing and optimizing resource usage at scale still requires careful monitoring and tuning. Better built-in cost visibility would be very helpful. For the needed improvements, I think that covers most of my main concerns. The biggest areas for improvement are still around simplifying operations, better native observability, and easier cost visibility. If I had to add one more point, it would be around standardization and developer experience. Sometimes different clusters, cloud providers, or tooling setups behave slightly differently, which increases maintenance efforts. More consistent defaults and opinionated best practices could help teams adopt Kubernetes faster and with fewer surprises. Overall, despite these challenges, Kubernetes is a very mature and reliable platform, and the benefits clearly outweigh the limitations for most production use cases. An additional area that could be improved is upgrade and version management. While managed services help coordinate Kubernetes version upgrades, API deprecations and compatibility with add-ons can still be time-consuming and risky for production environments. Better tooling and clearer migration automation would make upgrades safer and easier. Another improvement could be around documentation, consistency, and discoverability. Kubernetes documentation is very comprehensive, but for beginners, it can sometimes be overwhelming to navigate and identify best practice paths.
Fernando Jacinto Alvarez - PeerSpot reviewer
Senior Database Administrator at Microsoft
Automated updates have streamlined deployments and now support consistent multi‑cloud replication
Replicated offers features that help reduce the implementation time, which is why we are considering using it. I used it for testing the environment with our use case. We were running in a cloud and used the Kubernetes options. We replicated it to host our web page and then removed it to the Kubernetes cluster again, which was working fine. I did not have any problems during that process. The automated update is a good feature because you do not lose a lot of time during the entire process, and there is no stop phase or anything that could fail. When initially installing the product and then applying patches, we do not have any problems. We tried to integrate Replicated with DevOps tools. We tested integrating with Azure DevOps and GitHub, and we did not have any problems at that time. We did not have GitLab or any other tool available.

Quotes from Members

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

Pros

"The auto-repair function in Kubernetes is perfect; when something breaks, the auto-repair function automatically repairs it, and if you are running the content in Kubernetes, you have a good setup and do not need to do anything for the management of this, so the automation of Kubernetes is number one."
"Kubernetes allows us to update without downtime and to easily deploy new software, which is very beneficial for our operations."
"This is a good product and I can recommend it."
"The product offers security, scalability, high availability deployment, and scheduling mechanisms."
"I like the replication center and the configuration."
"It is a very good solution for deploying microservices in an application. It has a lot of freedom in it, which makes it very interesting. It is also web-enabled. You can run services in other virtual applications and virtual machines."
"With the use of our blueprint, my experience with the initial setup has been a ten out of ten where one is difficult and ten is easy."
"The best thing about Kubernetes is orchestration. It is very good. We will not see much downtime unless there are some human errors. We do not see much downtime or issues with the container or automation."
"Replicated is a good tool that enables all software vendors that want to package over the web."
 

Cons

"There are several areas where Kubernetes could improve."
"It would be very interesting if they could introduce a template engine to set dynamic values in the deployment time. It would be ideal if it could be native in Kubernetes as it would be much easier."
"Honestly, there is not much I like about Kubernetes. It's very complicated to deal with. I just do it because I have to."
"One feature I would actually like to see is the network monitoring part. When we talk about communities, it's mostly the computer side. But it does have some enhancements on the networking side which they have recently released. I would like to see more enhancement where we can monitor the networks of the Kubernetes cluster or the Kubernetes workloads."
"The solution could be more stable."
"The setup and operation of the product should be simplified."
"Currently, in Kubernetes, all of the health deployments or monitoring, and the discrete tools need to be configured. Changing this would make it much easier. Otherwise, we have to rely on a external tool to implement the monitoring."
"The platform could be more convenient to use."
"The licensing cost could be improved, as some of the entitlements do not fit with the copies."
 

Pricing and Cost Advice

"If you have a solid AKS and a solid DevOps process, you'll automatically get an ROI, not just in terms of cost but also in how quickly you can see your business application progress."
"Kubernetes is open source and is an orchestration platform. It is a cost effective solution and its pricing depends on your company and how you use it"
"We use the solution's open-source version."
"Kubernetes is open-source. Kubernetes is free, but we're charged for AWS utilization."
"There are no licensing fees."
"The management layer is free, which is perfect. You don't need to pay money for the management layer, but in AWS develop service, you need to pay. I think it is €75 per month for the management layer. It is free here, so you can have as many Kubernetes clusters as you need. You are paying just for the workload, that is, for the machine, CPU, memory, and everything."
"The solution itself is open-source, so there is no cost attached to it. However, it requires a virtual machine to operate, which does come at a cost; a choice of a pay as you go model, or a monthly charge via an enterprise agreement. There is a pricing calculator available, where organizations can determine the level and number of virtual machines required, and how much that will cost."
"It's an affordable solution"
Information not available
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
920,929 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Manufacturing Company
11%
Outsourcing Company
11%
Construction Company
10%
Computer Software Company
7%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business27
Midsize Enterprise10
Large Enterprise50
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Kubernetes?
My experience with the pricing, setup cost, and licensing of Kubernetes is that it is well-priced, and the features it offers are very good, making the price worth it.
What needs improvement with Kubernetes?
Kubernetes has a fairly steep learning curve. Concepts including networking, RBAC, Ingress, storage, controllers, and troubleshooting can be very difficult for beginners. Better built-in diagnostic...
What is your primary use case for Kubernetes?
In our organization, we primarily use Kubernetes for running and managing containerized applications in production environments. I use it for deploying microservices, service discovery, scaling app...
What is your experience regarding pricing and costs for Replicated?
We got Replicated from the AWS website. I remember we had most of the workloads on the Azure cloud. The reason we did not continue is because sometimes AWS is more expensive than the Azure cloud. R...
What needs improvement with Replicated?
The licensing cost could be improved, as some of the entitlements do not fit with the copies. Replicated could add new features that would make life easier or fix problems that need addressing. The...
What is your primary use case for Replicated?
I use Replicated to copy some information or replicate from one source to different environments.
 

Also Known As

K8
No data available
 

Overview

 

Sample Customers

China unicom, NetEase Cloud, Nav, AppDirect
Information Not Available
Find out what your peers are saying about Amazon Web Services (AWS), Red Hat, Kubernetes and others in Container Management. Updated: October 2026.
920,929 professionals have used our research since 2012.