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

Codefresh vs Travis CI comparison

 

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

Codefresh
Ranking in Build Automation
15th
Average Rating
8.8
Reviews Sentiment
5.7
Number of Reviews
5
Ranking in other categories
No ranking in other categories
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 July 2026, in the Build Automation category, the mindshare of Codefresh is 0.9%, up from 0.3% compared to the previous year. The mindshare of Travis CI is 3.3%, up from 0.9% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Codefresh0.9%
Travis CI3.3%
Other95.8%
Build Automation
 

Featured Reviews

US
DevOps Engineer at a manufacturing company with 51-200 employees
GitOps control plane has transformed deployments and now enables proactive Kubernetes visibility
While using Codefresh, I still don't see many downsides, but I would say the UI performance with large logs is an area for improvement. When a complex pipeline generates a high volume of logs, the user interface can occasionally become sluggish, jittery, or take extra seconds to render. The only downside I would say is the UI experience and its smoothness. Although the visibility into Kubernetes is excellent, I would love to see out-of-the-box cost optimization metrics. Argo CD knows how a pod is performing, its status, and its state. There should be some kind of cost optimization metrics shown on the GitOps application where we could save money or perhaps reduce the resources of a particular pod application. One improvement I would say is a promotion process between environments, from lower to upper environment. Currently, the model with complex promotion logic such as specific concurrency strategies or smart rollbacks when multiple commits hit at once can feel quite manual. I would like to see more automated promotion gates that can handle multi-cluster dependencies without needing as much custom YAML configuration.
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

"Codefresh impacts my organization positively by improving security and making the time of releases much shorter and faster than the previous scenario with CI/CD implementations."
"Codefresh has positively impacted my organization; it has been amazing."
"Before Codefresh, we had to plan the strategy, write the configuration file, and run everything; it used to take two to three days to plan and implement, but now it is a one-time job, so it can be done in ten to fifteen minutes, which has reduced a lot of time and sped up the automation and CI/CD, requiring fewer employees."
"Codefresh has helped save time, reduce errors, and improve collaboration across teams."
"Since switching to Codefresh, our organization has definitely seen approximately a 30 percent reduction in deployment times."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"Codefresh can be improved with more capability inside the GCP ecosystem."
"The reason it is not a ten is because our developers who do not have Kubernetes and Docker knowledge cannot use Codefresh easily, and the configuration file we have to write is very complex, requiring prior knowledge of Kubernetes and Docker-based deployments."
"At this moment, I cannot think of anything about needed improvements for Codefresh."
"The challenge that we faced with Codefresh is that it is a complex setup."
"While using Codefresh, I still don't see many downsides, but I would say the UI performance with large logs is an area for improvement."
"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.
902,988 professionals have used our research since 2012.
 

Questions from the Community

What needs improvement with Codefresh?
The challenge that we faced with Codefresh is that it is a complex setup. Kubernetes and Docker are somewhat complex. However, the cluster needs many computer resources to have Kubernetes and Docke...
What is your primary use case for Codefresh?
My main use case for Codefresh is for build and release. For build and release with Codefresh, we maintain the version-controlled file of the pipeline. Once a commit happens, the build will trigger...
What advice do you have for others considering Codefresh?
The advice I would give to others looking into using Codefresh is that they need to have that budget. Whoever wants to use Codefresh needs to have the budget and a return on investment. They need t...
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

 

Overview

 

Sample Customers

Information Not Available
Facebook, Heroku, Mozilla, Zendesk, twitter, Rails
Find out what your peers are saying about GitLab, Jenkins, GitHub and others in Build Automation. Updated: May 2026.
902,988 professionals have used our research since 2012.