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

Harness vs Travis CI 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

Harness
Ranking in Build Automation
7th
Average Rating
7.8
Reviews Sentiment
7.8
Number of Reviews
7
Ranking in other categories
Static Application Security Testing (SAST) (16th), Cloud Cost Management (9th), Feature Management (2nd)
Travis CI
Ranking in Build Automation
20th
Average Rating
6.0
Reviews Sentiment
3.1
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2026, in the Build Automation category, the mindshare of Harness is 5.8%, up from 5.6% compared to the previous year. The mindshare of Travis CI is 2.1%, up from 0.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Market Share Distribution
ProductMarket Share (%)
Harness5.8%
Travis CI2.1%
Other92.1%
Build Automation
 

Featured Reviews

reviewer2787357 - PeerSpot reviewer
Site Reliability Engineer at Granicus Inc.
Automated delivery has made production releases safer and has reduced deployment incidents
The first point for improvement is the steep learning curve, where concepts such as services, environment, pipelines, and templates take time to understand. New users often need training before becoming productive, resulting in slower initial onboarding compared to simpler CD tools. An improvement idea is better guided onboarding with more opinionated defaults and examples. The second improvement can be on UI complexity and navigation; the UI can feel cluttered with many options and finding past executions, logs, or specific settings sometimes takes extra clicks, leading to small but noticeable productivity loss. Simplified UI views for common workflows and improved search and filtering could help. I also see cost and licensing as potential areas for improvement, as pricing can feel high for small teams and advanced features are tied to higher tiers, which may limit adoption for startups or smaller organizations. Flexible pricing models and more essential features in lower tiers could address this issue.
Pravar Agrawal - PeerSpot reviewer
Senior SRE at a tech vendor with 10,001+ employees
YAML-based configuration and simple deployment but user interface needs modernizing
Travis CI is an okay tool, and I am forced to use it as part of my job. I don't maintain it; it is running somewhere else, and I don't have control over it. The interface is very basic and not user-friendly; it feels like it was stuck in 2010. It is very basic and designed for lightweight CI work, and it cannot handle heavy CI. You cannot do branched flows, and you will have to write shell scripts to send calls here and there. The pipelines are not as detailed as some other CI/CD tools. If Travis is down, you don't have any control over it and need to reach out to their customer support.

Quotes from Members

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

Pros

"Harness integrates all functions like execution pipelines, environment checks, and log monitoring in one place."
"Production deployments are faster and more reliable, especially for Kubernetes and cloud-based services, with significant reduction in deployment-related incidents, faster recovery when issues occur, faster, more confident releases, increased deployment frequency with higher confidence, and better governance and compliance that improved visibility and coordination across Dev, QA, Ops, and SRE teams."
"By adopting templates and various different pipelines across our own IDP platform, we have saved upwards of 30 to 40% of development time and also reduced risks of failures or error rates by upwards of 70%."
"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."
"Everything in Harness is configured and runs smoothly."
"Harness starts integrating with organizations, making everything automated without the need for manual interruption."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"When integrating Harness with more than twenty applications in one place, it becomes less stable, causing improvements to be necessary."
"Harness setup and configurations could be made easier to configure, which would be helpful."
"There's also room for improvement in debugging pipeline issues, which can sometimes become complex."
"The first point for improvement is the steep learning curve, where concepts such as services, environment, pipelines, and templates take time to understand."
"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."
"I prefer the previous less compact UI version of Harness, which showed more details on the screen."
"Infrastructure as code or pipeline as code is something that Harness severely lacks."
"The interface is very basic and not user-friendly; it feels like it was stuck in 2010."
report
Use our free recommendation engine to learn which Build Automation solutions are best for your needs.
880,844 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
29%
Computer Software Company
9%
Manufacturing Company
7%
Government
5%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Large Enterprise7
No data available
 

Questions from the Community

What do you like most about Harness?
It's a highly customizable DevOps tool.
What needs improvement with Harness?
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,...
What is your primary use case for Harness?
Harness has been implemented in our organization for one of our clients for approximately 8 to 10 months. Harness is particularly utilized for our infrastructure provisioning pipelines and our RITM...
What is your experience regarding pricing and costs for Travis CI?
I'm not too sure about the pricing of Travis or how the agreement works.
What needs improvement with Travis CI?
Travis CI is an okay tool, and I am forced to use it as part of my job. I don't maintain it; it is running somewhere else, and I don't have control over it. The interface is very basic and not user...
What is your primary use case for Travis CI?
Travis CI is mainly used to run integration tests as part of the deployment, which I do on Kubernetes. The Travis workflows are integrated with any changes in my code. It will have different jobs, ...
 

Comparisons

 

Also Known As

Armory
No data available
 

Overview

 

Sample Customers

Linedata, Openbank, Home Depot, Advanced
Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
Find out what your peers are saying about GitLab, Google, GitHub and others in Build Automation. Updated: January 2026.
880,844 professionals have used our research since 2012.