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

Depot 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

Depot
Ranking in Build Automation
22nd
Average Rating
7.4
Reviews Sentiment
5.0
Number of Reviews
3
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 August 2026, in the Build Automation category, the mindshare of Depot is 0.5%. The mindshare of Travis CI is 3.3%, up from 1.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Travis CI3.3%
Depot0.5%
Other96.2%
Build Automation
 

Featured Reviews

RS
Senior Technical Lead at HCLSoftware
Managing complex code branches has been challenging but has improved team collaboration
Depot needs improvement as it was stable but also very slow. Depot's slow speed arises when we perform different integrations. On the positive side, it provides mono-repo scalability, meaning it can handle multiple users at any given time without crashing, which is a strong point. Depot should be improved for remote work because it functions poorly in that regard. Depot's branching style is also poor and could be improved. There is a steep learning curve that makes it difficult for people who previously worked on decentralized systems to adapt. It would be beneficial if Depot could become more similar to Git.
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

"Depot has positively impacted my organization in an awesome way, and the fact that I can save time gives me the possibility to have more clients during the day, saving at least 20% each day because of Depot."
"Depot has positively impacted my organization by helping us manage our code better where multiple developers are working on the system."
"Depot has positively impacted our organization by ensuring that everything works fully, which makes other clients really happy."
"The only thing I like about Travis CI is that you have a YAML file to define a Travis flow."
 

Cons

"Depot needs improvement as it was stable but also very slow."
"However, they need improvement with older servers due to storage space issues, which prevents me from giving a perfect score of ten."
"Depot is a useful tool and there is space for improvement, but I can't figure out what can be done, which is why I chose eight out of ten."
"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.
909,725 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Construction Company
42%
Manufacturing Company
13%
Comms Service Provider
9%
University
5%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
No data available
 

Questions from the Community

What is your experience regarding pricing and costs for Depot?
Regarding my experience with pricing, setup cost, and licensing for Depot, I have faced many challenges with cost optimization. We need to manage what services we can use and optimize the cost, whi...
What needs improvement with Depot?
Depot needs improvement as it was stable but also very slow. Depot's slow speed arises when we perform different integrations. On the positive side, it provides mono-repo scalability, meaning it ca...
What is your primary use case for Depot?
My main use case for Depot was for storing production code and deploying it through pipelines. A specific example of how I used Depot for storing production code and deploying through pipelines inv...
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 Jenkins, GitHub, GitLab and others in Build Automation. Updated: August 2026.
909,725 professionals have used our research since 2012.