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

Azure Kubernetes Service (AKS) vs Threat Stack Cloud Security Platform [EOL] comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Aug 10, 2025

Review summaries and opinions

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

ROI

Sentiment score
8.1
The ROI from Azure Kubernetes Service depends on specific use cases, duration of use, and challenges with cost-effectiveness.
Sentiment score
7.3
Threat Stack Cloud Security boosted compliance and revenue, reduced staffing needs, enhanced security, and expanded infrastructure dramatically.
 

Customer Service

Sentiment score
6.0
AKS support ranges from excellent to inadequate, with mixed reviews on response times and issue resolution efficiency.
Sentiment score
7.4
Threat Stack Cloud Security Platform's support is praised for responsiveness, precise solutions, and effective communication with technical representatives.
 

Scalability Issues

Sentiment score
8.1
Azure Kubernetes Service offers high scalability and ease of expansion but can be costly for extensive scaling needs.
Sentiment score
8.2
Threat Stack Cloud Security Platform is scalable, easy to deploy, and efficient across AWS accounts, with minor configuration concerns.
AKS offers excellent scalability due to its adaptation from Kubernetes.
 

Stability Issues

Sentiment score
7.2
Azure Kubernetes Service is stable, self-healing, with occasional sync issues, and concerns typically arise from external factors.
Sentiment score
7.5
Threat Stack Cloud Security Platform [EOL] is stable and efficient, with minor GUI and agent issues for some users.
From my usage, I would rate its stability as eight to nine out of ten.
 

Room For Improvement

AKS requires faster alerts, better support, improved cost-efficiency, enhanced UI, streamlined integration, security, monitoring, and simplified deployment.
Threat Stack Cloud Security Platform needs UI improvements, better API alignment, and enhanced integrations, especially for serverless and container environments.
When purchasing support directly from RHEL, the price is significantly high.
The costs are rising rapidly, and we have not seen any cost reductions by moving to Azure.
 

Setup Cost

Azure Kubernetes Service is costly, with potential $10,000 monthly fees, but offers flexible pricing and valued platform flexibility.
Threat Stack Cloud Security Platform offers value with transparent pricing, ranging $15-$20 monthly, seen as competitively priced by users.
Transitioning to Azure did not bring cost reductions; in fact, costs are rising rapidly.
The pricing for Azure Kubernetes Service seems to be around the average, which I would rate as a five out of ten.
 

Valuable Features

Azure Kubernetes Service excels in integration, scalability, ease of use, security, cost management, and operational efficiency.
Threat Stack Cloud Security platform is esteemed for its configurability, integration, monitoring capabilities, and effective alert management.
The most valuable features of Azure Kubernetes Service are its integration with Kubernetes, offering similar features for a seamless experience.
Since pricing is not a major concern, we chose the best fit for our application, which was specifically designed for this particular platform.
 

Categories and Ranking

Azure Kubernetes Service (AKS)
Average Rating
8.2
Reviews Sentiment
7.4
Number of Reviews
40
Ranking in other categories
Container Security (19th)
Threat Stack Cloud Security...
Average Rating
8.2
Reviews Sentiment
7.1
Number of Reviews
8
Ranking in other categories
No ranking in other categories
 

Featured Reviews

Shaijith KB - PeerSpot reviewer
Professional services boost confidence but pricing and user-friendliness need attention
We have multiple solutions such as SimpliVity, Nutanix, and DXRail, which are all part of our Ansible-based system. It gives us more confidence and we can control our groups effectively. The solution is not particularly user-friendly for novice administrators, making it challenging to understand certain aspects. Templates are not readily available, requiring users to build their own worksheets and everything from scratch. This is a main decentralization we observe compared to VMware. We have tested various solutions including Rancher, RHEL, Canonical from SUSE, and the bare metal version from RHEL direct. Since pricing is not a major concern, we chose the best fit for our application, which was specifically designed for this particular platform.
SC
SecOps program for us, as a smaller company, is amazing; they know what to look for
They could give a few more insights into security groups and recommendations on how to be more effective. That's getting more into the AWS environment, specifically. I'm not sure if that's Threat Stack's plan or not, but I would like them to help us be efficient about how we're setting up security groups. They could recommend separation of VPCs and the like - really dig into our architecture. I haven't seen a whole lot of that and I think that's something that, right off the bat, could have made us smarter. Even as part of the SecOps Program, that could be helpful; a quick analysis. They're analyzing our whole infrastructure and saying, "You have one VPC and that doesn't make a lot of sense, that should be multiple VPCs and here's why." The architecture of the servers in whatever cloud-hosting provider you're on could be helpful. Other than that, they should continue to expand on their notifications and on what's a vulnerability. They do a great job of that and we want them to continue to do that. It would be cool, since the agent is already deployed and they know about the server, they know the IP address, and they know what vulnerability is there, for them to test the vulnerability and see if they can actually exploit it. Or, once we patch it, they could double-check that it can't be. I don't know how hard that would be to build. Thinking on it off the top off my head, it could be a little challenging but it could also be highly interesting. It would also be great if we could test a couple of other features like hammering a server with 100 login attempts and see what happens. Real test scenarios could be really helpful. That is probably more something close to what they do with the SOC 2 audit or the report. But more visualization of that, being able to test things out on our infrastructure to make sure we can or can't hit this box could be interesting.
report
Use our free recommendation engine to learn which Container Security solutions are best for your needs.
867,349 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
25%
Computer Software Company
11%
Manufacturing Company
8%
Government
6%
Performing Arts
13%
Manufacturing Company
10%
University
7%
Comms Service Provider
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business15
Midsize Enterprise6
Large Enterprise22
By reviewers
Company SizeCount
Small Business2
Midsize Enterprise5
Large Enterprise2
 

Questions from the Community

What do you like most about Azure Kubernetes Service (AKS)?
The platform's high scalability is one of its biggest advantages.
What needs improvement with Azure Kubernetes Service (AKS)?
Could you please tell what areas of Azure Kubernetes Service (AKS) you think could be improved or enhanced? It doesn't necessarily have to be something advanced. Perhaps there are some minor things...
What is your primary use case for Azure Kubernetes Service (AKS)?
Could you please describe your customers' usual use cases for Azure Kubernetes Service (AKS)?
Ask a question
Earn 20 points
 

Also Known As

No data available
Threat Stack, CSP,
 

Overview

 

Sample Customers

Information Not Available
StatusPage.io, Walkbase, Spanning, DNAnexus, Jobcase, Nextcapital, Smartling, Veracode, 6sense
Find out what your peers are saying about Palo Alto Networks, Wiz, SentinelOne and others in Container Security. Updated: August 2025.
867,349 professionals have used our research since 2012.