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
4th
Average Rating
8.4
Reviews Sentiment
7.6
Number of Reviews
21
Ranking in other categories
No ranking in other categories
Harness
Ranking in Build Automation
11th
Average Rating
7.8
Reviews Sentiment
7.9
Number of Reviews
4
Ranking in other categories
Static Application Security Testing (SAST) (30th), Cloud Cost Management (13th)
 

Mindshare comparison

As of May 2025, in the Build Automation category, the mindshare of GitHub Actions is 11.4%, up from 5.0% compared to the previous year. The mindshare of Harness is 7.0%, up from 4.2% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation
 

Featured Reviews

MohamedMostafa1 - PeerSpot reviewer
Handles scalability well, automatically managing execution infrastructure without requiring additional configurationsThe automation feature of GitHub Actions is
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.
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

"GitHub Actions is valuable for its ease of use and integration."
"We can trigger files manually or automate processes."
"The main benefit is collaboration. It allows us to easily collaborate with other developers, regardless of location. For example, we can collaborate with both our African and German colleagues seamlessly. It's platform-agnostic, so it is flexible and not tied to any OS, so we can work on Linux, Windows, web, and even Oracle applications. It's flexible, reliable, and overall an excellent tool for our needs."
"The solution has saved us approximately 20% in terms of efficiency and productivity."
"It is easy to use, especially if you are accustomed to using GitHub."
"The most valuable feature of the solution is that it is a good product that offers stability and performance."
"The most valuable features of GitHub Actions include its seamless integration within GitHub, which simplifies the CI/CD pipeline setup. The scalability of using different types of runners—both public and private runners—enhances deployment flexibility."
"GitHub Actions is a beautiful tool that integrates smoothly with all major tools, reducing CI/CD work by 30% to 40%."
"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place."
"Harness starts integrating with organizations, making everything automated without the need for manual interruption."
"It's a highly customizable DevOps tool."
"The features of Harness are valuable, supporting rolling deployments, basic deployments, and blue-green deployments with zero downtime."
"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place, making it convenient."
 

Cons

"GitHub Actions lacks a feature for automating the build process for mobile applications."
"We can leverage this database tool to manage everything within our environment and data burners, allowing for customization and execution. An additional advantage is the capability to modify aspects like file size, making processes more efficient and faster across the pipelines. Regarding improvements or implementations, I believe there should be enhancements made to the deployment tool. It should be integrated as part of the solution. Infrastructure-wise, we already have tools like GitHub and RobSpot, and data enables us to automate various processes, which is quite beneficial. As for further enhancements, I'm uncertain. I've shared everything I know. However, if there's something specific you'd like to see in future releases, a feature that may not exist yet but would be desirable, I can't provide any input on that matter."
"The UI could be better."
"Sometimes it is quite complex to commit code from our local system to the GitHub repository; creating a folder in GitHub can be tedious."
"We still use Jenkins for some tasks, which suggests there may be areas for improvement in GitHub Actions."
"The solution's integration capabilities and UI are areas of concern where improvement is required to make the product more user-friendly."
"Improvements could be made in terms of time-saving capabilities and resolving potential complexities in centralized workflows."
"There is a part that detects outdated libraries. If that feature could be more intuitive and informative, that would be nice."
"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."
"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."
"When integrating Harness with more than twenty applications in one place, it becomes less stable, causing improvements to be necessary."
"I prefer the previous less compact UI version of Harness, which showed more details on the screen."
 

Pricing and Cost Advice

"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."
"It's low-priced. Not high, but definitely low."
"It is free and open platform, so I would rate it 1 out of 10."
"For our basic usage, we didn't have to pay."
"The product is slightly more expensive than some alternatives."
"Regarding cost, as an enterprise, we negotiate our license and expenses, so I can't provide a specific rating for that."
"The cost for GitHub Actions may be around $45 dollars per user."
"The tool's price is okay and reasonable."
Information not available
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
851,604 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
17%
Computer Software Company
12%
Manufacturing Company
11%
Comms Service Provider
6%
Financial Services Firm
33%
Computer Software Company
13%
Government
7%
Manufacturing Company
5%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
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?
I would need to check with my team about specific shortcomings. We still use Jenkins ( /products/jenkins-reviews ) for some tasks, which suggests there may be areas for improvement in GitHub Actions.
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: April 2025.
851,604 professionals have used our research since 2012.