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

Apiiro vs Harness 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

Apiiro
Ranking in Static Application Security Testing (SAST)
23rd
Average Rating
8.6
Reviews Sentiment
6.4
Number of Reviews
4
Ranking in other categories
Software Composition Analysis (SCA) (15th), API Security (14th), Software Supply Chain Security (10th), Risk-Based Vulnerability Management (18th), Application Security Posture Management (ASPM) (10th)
Harness
Ranking in Static Application Security Testing (SAST)
14th
Average Rating
8.0
Reviews Sentiment
7.3
Number of Reviews
11
Ranking in other categories
Build Automation (6th), Cloud Cost Management (17th), Feature Management (2nd)
 

Mindshare comparison

As of November 2026, in the Static Application Security Testing (SAST) category, the mindshare of Apiiro is 1.4%, up from 0.8% compared to the previous year. The mindshare of Harness is 0.8%, up from 0.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Static Application Security Testing (SAST) Mindshare Distribution
ProductMindshare (%)
Harness0.8%
Apiiro1.4%
Other97.8%
Static Application Security Testing (SAST)
 

Featured Reviews

Abimael Ferreira - PeerSpot reviewer
Security at Blaze Information Security
Centralized code analysis has improved my workflow and prioritizes critical vulnerabilities
Apiiro offers several features that I consider the best, such as the ability to have multiple developers and AppSec professionals working on the same project, and through the platform, we can see the number of vulnerabilities, generate reports, and integrate Snyk within our workflow. Before the code goes to production, Apiiro can read all that code and determine if everything is okay or if improvements are needed. The reports generated by Apiiro and its integration with Snyk contribute to my development process by giving us visibility into what is actually vulnerable, as automation like Apiiro makes it much easier to track vulnerabilities without spending too much time manually checking for issues, thus generating meaningful reports afterward. Apiiro manages permissions very effectively, which is interesting from an organizational standpoint because it allows us to separate which people can access a given project and designate project administrators who can approve or reject changes once a fix is made. I found the accuracy and reliability of Apiiro's results to be very good, as it can predict issues based on its existing data.
MK
Technical Associate at ZS
Templatized pipelines have improved efficiency while limitations in code-based development remain
Harness UI can do a lot of good things. Harness's UI should not feel very complicated. At the current stage, it feels very commercialized and compared to other platforms such as Argo CD or Jenkins, which feel much more lively and much more simple. Infrastructure as code or pipeline as code is something that Harness severely lacks. There is not a lot of good support for pipeline as code, and I often find myself not using pipeline as code the way other platforms such as GitHub Actions or Jenkins integrate pipeline as code. Pipeline as code is definitely one of the disadvantages when it comes to Harness. Additionally, the entire platform feels very commercialized, which is something that a lot of developers, especially open-source enthusiasts, might not appreciate even within the organization. One of the very important key factors I observed was that there is no way to execute nested pipelines, which means that we cannot execute child pipelines within child pipelines and child pipelines even within those child pipelines. There is no way to execute nested pipeline execution, which may or may not be required based on the use case, but it is definitely one of those features that I wish the platform had.

Quotes from Members

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

Pros

"The positive impact I have seen from working with Apiiro for my company includes the metrics that we get from Apiiro, which have been extremely helpful."
"Apiiro's secrets detection feature has saved us several times, which we appreciate greatly."
"Apiiro manages permissions very effectively, which is interesting from an organizational standpoint because it allows us to separate which people can access a given project and designate project administrators who can approve or reject changes once a fix is made."
"The workflow automation is likely the best aspect of the solution."
"The features of Harness are valuable, supporting rolling deployments, basic deployments, and blue-green deployments with zero downtime."
"It's a highly customizable DevOps tool."
"Everything in Harness is configured and runs smoothly."
"Harness has impacted my organization positively; we use Harness in most of all deployments, so it is uniform."
"Harness starts integrating with organizations, making everything automated without the need for manual interruption."
"Approximately seventy-five percent time was reduced in case of deployment and around sixty to sixty-five percent time was reduced while troubleshooting it."
"Harness has positively impacted my organization as several teams have already migrated to it, and some are in the process of moving, reducing the dependency on one specific platform and making it faster with shortened build times and much faster deployments."
"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place, making it convenient."
 

Cons

"The UI sometimes helps but can also be a bit confusing."
"User management is a little bit clunky."
"My first feedback for Apiiro is that it is very slow, extremely slow."
"I would like support for our self-hosted Git server, other than GitHub, just regular Git."
"There are some UI components that can be improved."
"The initial setup can be complex and time-consuming, and the advanced features may require some learning time due to a steep learning curve."
"When integrating Harness with more than twenty applications in one place, it becomes less stable, causing improvements to be necessary."
"Harness can be improved by providing more clarity on the credits it issues for Harness Cloud, as it has a tiered pricing structure involving license and credit costs, which can get confusing."
"I prefer the previous less compact UI version of Harness, which showed more details on the screen."
"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."
"Infrastructure as code or pipeline as code is something that Harness severely lacks."
"The licensing cost can be significant for larger teams, which should be taken into account."
report
Use our free recommendation engine to learn which Static Application Security Testing (SAST) solutions are best for your needs.
920,769 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
14%
Manufacturing Company
12%
Construction Company
8%
Comms Service Provider
8%
Financial Services Firm
23%
Outsourcing Company
12%
Comms Service Provider
7%
Manufacturing Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business4
Midsize Enterprise1
Large Enterprise10
 

Questions from the Community

What needs improvement with Apiiro?
One area Apiiro could improve is reporting customization and dashboard flexibility with more advanced filtering and easier communication.
What is your primary use case for Apiiro?
Apiiro is primarily used for code scanning and integration with source code control. The main use cases include code scanning and code snippet analysis. Apiiro provides security and visibility by h...
What advice do you have for others considering Apiiro?
Based on my experience with Apiiro, I would recommend it to organizations looking to strengthen their application security processes and integrate security into their development workflows. One of ...
What needs improvement with Harness?
There are some UI components that can be improved. The needed UI improvements include more graphs, more history, the ability to create pipelines through the UI, and more interactions, with UI compo...
What is your primary use case for Harness?
My main use case for Harness is to create pipelines, deploy applications, and manage security pipelines. I use Harness to deploy applications to EC2 instances and Kubernetes instances, and I create...
What advice do you have for others considering Harness?
My advice for others looking into using Harness is to use AI capabilities, create pipelines, and then use it to deploy. Harness is a good tool. I would rate this review a nine out of ten.
 

Comparisons

 

Also Known As

Apiiro Control Plane (ASOC), Apiiro API Security (SAST), Apiiro Open Source (SCA)
Armory
 

Overview

 

Sample Customers

Morgan Stanley, Rakuten, Jack Henry, SoFi, Colgate, Navan
Linedata, Openbank, Home Depot, Advanced
Find out what your peers are saying about Apiiro vs. Harness and other solutions. Updated: November 2026.
920,769 professionals have used our research since 2012.