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

Kubernetes vs Palette comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 29, 2026

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.3
Number of Reviews
81
Ranking in other categories
No ranking in other categories
Palette
Ranking in Container Management
21st
Average Rating
7.0
Reviews Sentiment
4.9
Number of Reviews
1
Ranking in other categories
Agile and DevOps Services (7th), Edge Computing Platforms (2nd)
 

Mindshare comparison

As of August 2026, in the Container Management category, the mindshare of Kubernetes is 10.1%, up from 6.2% compared to the previous year. The mindshare of Palette is 1.0%, up from 0.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Container Management Mindshare Distribution
ProductMindshare (%)
Kubernetes10.1%
Palette1.0%
Other88.9%
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.
SH
Controller at a consultancy with 11-50 employees
Workflow automation has boosted invoice processing but still needs finer approval routing
Palette can be improved as it does not have the ability to do very specific routing for invoices; in my case, I had multiple offices with multiple paths, and you had to know which particular office it was for. Depending upon the type of vendor invoice it was, sometimes it was difficult to know what path to put it on, so you need more detail in the approval matrix when you can set it up. I chose a 7 out of 10 because the approval matrix and the routing of invoices with specific customization were a bit lacking; I feel I needed more of that to be able to go into more detail on a per vendor basis or a per dollar value basis. Regarding Palette's AI capabilities, I definitely experienced some automation features related to accuracy. Due to the lack of flexibility in the building of the approval matrix, there was no way for it to code things 100% correctly, so intervention and review from a person were always necessary.

Quotes from Members

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

Pros

"The solution is extremely scalable; it also works for businesses of any size, from small to large."
"It is a stable and scalable product."
"Offers a crucial feedback process"
"The tool's most valuable feature is the auto-scaling feature. However, Kubernetes is not used alone; it is part of a complete deployment pipeline integrated with DevOps. This pipeline includes automation and deployment capabilities."
"Auto-scaling and self-healing features are very good."
"It's scalable."
"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 most valuable features of Kubernetes are the integration with Docker and there is plenty of documentation available. We work with Docker as a container, and it is more integrated with Docker than VMware Tanzu."
"Palette has positively impacted my organization by increasing the ability to process more accounts payable invoices, stopping the reliance on emails and paper trails."
 

Cons

"They need to focus on more security internally."
"There are several areas where Kubernetes could improve."
"Management features could be simplified."
"I'm a beginner, and I recently started working with Kubernetes. As of now, I don't see any bugs. However, it would be better if it could be deployed without coding."
"Absence of a built-in feature for local API creation"
"It increases developers' overhead."
"The first adoption was hard because the Kubernete's learning curve is pretty high."
"One thing I noticed is when you have multiple deployments and your node count increases beyond eight or nine, the container creation process doesn't copy properties correctly."
"Due to the lack of flexibility in the building of the approval matrix, there was no way for it to code things 100% correctly, so intervention and review from a person were always necessary."
 

Pricing and Cost Advice

"The solution is affordable."
"This is an open-source solution, so there are no licensing costs associated with its use."
"I would say the solution is worth the money, but it depends on the required workloads, the type of workload, and the scaling requirements etc."
"We use the solution's open-source version."
"In addition to Kubernetes, you have to pay for support."
"Kubernetes is an open-source solution that can be free. We have some distribution with licenses, such OpenShift and Tucows in Amazon. They are billing services."
"There are no licensing fees."
"Kubernetes is open-source. Kubernetes is free, but we're charged for AWS utilization."
Information not available
report
Use our free recommendation engine to learn which Container Management solutions are best for your needs.
908,800 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
11%
Manufacturing Company
9%
Computer Software Company
8%
Financial Services Firm
8%
Insurance Company
37%
Manufacturing Company
19%
Construction Company
10%
Media Company
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business27
Midsize Enterprise10
Large Enterprise49
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?
Pod management can be improved, as sometimes there is a memory outage in one pod that stops production. Regarding Kubernetes governance and security, I believe Kubernetes detects failures effective...
What is your primary use case for Kubernetes?
Kubernetes is the primary platform on which the services that run in my company are deployed. I run a couple of services on Kubernetes, including the payment service and the loan management service...
What is your experience regarding pricing and costs for Palette?
I was not involved in Palette's pricing, setup cost, and licensing, but given that it had already been set up in our European entity, I do not believe we had additional costs to set it up in our of...
What needs improvement with Palette?
Palette can be improved as it does not have the ability to do very specific routing for invoices; in my case, I had multiple offices with multiple paths, and you had to know which particular office...
What is your primary use case for Palette?
I used Palette for accounts payable workflow approval processing at my previous company. A specific example of how I used Palette for accounts payable workflow or approval processing is that OCR br...
 

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: July 2026.
908,800 professionals have used our research since 2012.