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

GitHub Actions vs Harness comparison

 

Comparison Buyer's Guide

Executive SummaryUpdated on Mar 5, 2025

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

GitHub Actions
Ranking in Build Automation
3rd
Average Rating
8.6
Reviews Sentiment
6.6
Number of Reviews
22
Ranking in other categories
No ranking in other categories
Harness
Ranking in Build Automation
9th
Average Rating
7.8
Reviews Sentiment
7.9
Number of Reviews
4
Ranking in other categories
Static Application Security Testing (SAST) (26th), Cloud Cost Management (12th)
 

Mindshare comparison

As of September 2025, in the Build Automation category, the mindshare of GitHub Actions is 10.1%, up from 8.8% compared to the previous year. The mindshare of Harness is 7.1%, up from 4.5% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Market Share Distribution
ProductMarket Share (%)
GitHub Actions10.1%
Harness7.1%
Other82.8%
Build Automation
 

Featured Reviews

MuhammadAzhar Khan - PeerSpot reviewer
Integration with various environments and cloud providers enhances automation
I use GitHub Actions for CI/CD pipelines. I automate infrastructure, deployment, and all processes. Most companies use CI/CD pipelines, and GitHub Actions is one of the tools available for this purpose The most valuable feature of GitHub Actions is that it is completely free. It can be integrated…
Linwei Yuan - PeerSpot reviewer
Streamline microservices deployment with integrated execution pipelines and comprehensive monitoring
Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place. It is very convenient since we have many microservices, so having one platform for all of them is beneficial. The dashboard allows me to monitor all core services' deployment status in one place, making it easier to find bugs and check logs.

Quotes from Members

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

Pros

"Creating workflows in YAML format is straightforward and easy to comprehend. This includes both understanding and writing workflows. Additionally, the downloading aspect for third-party instances can also be easily done. It's worth noting that vulnerability analysis and similar tasks should be part of our automation through data workflows. Furthermore, we can break down our processes step by step, starting from building, then moving on to analysis, testing, and finally deploying in production and the clear environment. All of these tasks can be efficiently managed within this platform."
"The level of automation achievable is really good. So, the custom workflow creation and Marketplace Actions improved our project's efficiency."
"It improves efficiency as it involves no downtime and is managed by GitHub."
"The product's most beneficial feature is the ability to create workflows within the solution."
"GitHub Actions is a beautiful tool that integrates smoothly with all major tools, reducing CI/CD work by 30% to 40%."
"The most valuable feature of the solution is that it is a good product that offers stability and performance."
"I am familiar with the entire life cycle of the product."
"I find the automation feature of GitHub Actions most valuable for our building processes. It integrates seamlessly with GitHub, so there's no extra configuration needed, making the building process easy and efficient. GitHub Actions handles scalability well, automatically managing execution infrastructure without requiring additional configurations. We haven't yet explored GitHub Actions' support for AI projects, as we haven't used its AI capabilities."
"The features of Harness are valuable, supporting rolling deployments, basic deployments, and blue-green deployments with zero downtime."
"Harness starts integrating with organizations, making everything automated without the need for manual interruption."
"It's a highly customizable DevOps tool."
"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place."
"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place, making it convenient."
 

Cons

"Sometimes incremental steps should be taken during deployment instead of trying to execute all tasks simultaneously, particularly when dealing with AWS EKS clusters and Helm charts."
"Sometimes it is quite complex to commit code from our local system to the GitHub repository; creating a folder in GitHub can be tedious."
"The solution's integration capabilities and UI are areas of concern where improvement is required to make the product more user-friendly."
"The main improvement would be to add support for more programming languages and frameworks."
"My company would want to see some AI features in the tool as it can add value to the product."
"The UI could be better."
"The main challenge I've experienced is with integration, particularly uploading to OneDrive, which was more complex compared to Google Drive or AWS S3 bucket."
"The primary area for improvement I see is in artifact management, especially for saving screenshots or videos from failed tests or data-driven actions. Currently, the configuration for saving these artifacts is complex."
"I prefer the previous less compact UI version of Harness, which showed more details on the screen."
"Even with automation, there's a requirement for manual change requests for approvals."
"When deploying multiple components to multiple environments, like production and BCP, failures sometimes occur. Improvements are needed when deploying one component to one environment."
"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."
"When integrating Harness with more than twenty applications in one place, it becomes less stable, causing improvements to be necessary."
 

Pricing and Cost Advice

"It's low-priced. Not high, but definitely low."
"The cost for GitHub Actions may be around $45 dollars per user."
"It is free and open platform, so I would rate it 1 out of 10."
"The tool's price is okay and reasonable."
"The product is slightly more expensive than some alternatives."
"Price-wise, GitHub Actions is okay. If I want to use the product's advanced features, then I need to pay the licensing charges for the solution."
"For our basic usage, we didn't have to pay."
"Regarding cost, as an enterprise, we negotiate our license and expenses, so I can't provide a specific rating for that."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
867,497 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
18%
Manufacturing Company
11%
Computer Software Company
11%
Comms Service Provider
7%
Financial Services Firm
31%
Computer Software Company
11%
Government
6%
Retailer
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise3
Large Enterprise11
No data available
 

Questions from the Community

What do you like most about GitHub Actions?
I have optimized job execution time by running test scripts in parallel and creating multiple pipelines; we've significantly reduced execution times. What could take 50 minutes can be cut down to j...
What is your experience regarding pricing and costs for GitHub Actions?
I would rate pricing a seven, which leans toward the expensive side. However, there is still value for money, and that's why we continue using it.
What needs improvement with GitHub Actions?
Frankly, I cannot imagine something that could be improved in GitHub Actions; there's a lot of capabilities, and the feature set is more advanced than we use. The pricing is high for the advanced s...
What do you like most about Harness?
It's a highly customizable DevOps tool.
What needs improvement with Harness?
When deploying multiple components to multiple environments, like production and BCP, failures sometimes occur. Improvements are needed when deploying one component to one environment.
What is your primary use case for Harness?
Our primary use case for Harness ( /products/harness-reviews ) is as a deployment tool. Although I am not a DevOps engineer, my team uses Harness ( /products/harness-reviews ) for deployment purpos...
 

Comparisons

 

Also Known As

No data available
Armory
 

Overview

 

Sample Customers

Information Not Available
Linedata, Openbank, Home Depot, Advanced
Find out what your peers are saying about GitHub Actions vs. Harness and other solutions. Updated: September 2025.
867,497 professionals have used our research since 2012.