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

Depot vs GitHub Actions comparison

Why PeerSpot?
 

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
21st
Average Rating
7.4
Reviews Sentiment
5.0
Number of Reviews
3
Ranking in other categories
No ranking in other categories
GitHub Actions
Ranking in Build Automation
2nd
Average Rating
8.4
Reviews Sentiment
5.2
Number of Reviews
24
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of November 2026, in the Build Automation category, the mindshare of Depot is 0.8%. The mindshare of GitHub Actions is 6.7%, down from 9.7% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
GitHub Actions6.7%
Depot0.8%
Other92.5%
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.
Bharadwaj Deepak Mohapatra - PeerSpot reviewer
DevOps Engineer at ENTERPRISE SYSTEM SOLUTIONS LIMITED
Has supported repository management and demonstrates potential in workflow flexibility
While GitHub Actions offers a range of functionalities, it is newer compared to more established tools such as Jenkins and Azure DevOps. There is still room for improvement, especially in areas concerning deeper capabilities akin to those provided by Jenkins and Azure DevOps. Given the evolving nature of technology, there are potential improvements GitHub Actions can focus on, including enhancing support and reliability to match its competitors.

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 our organization by ensuring that everything works fully, which makes other clients really happy."
"Depot has positively impacted my organization by helping us manage our code better where multiple developers are working on the system."
"GitHub Actions can be easily configured, especially for environment variables and secrets. The UI is understandable and user-friendly for setting up CI/CD pipelines. I prefer tools like GitLab, where the pipeline starts quickly and is accessible near the commits for easy access. However, many CI/CD tools are interchangeable due to similar features of GitHub Actions and other similar tools."
"GitHub Actions is valuable for its ease of use and integration."
"It is easy to use, especially if you are accustomed to using GitHub."
"We can trigger files manually or automate processes."
"It is user-friendly, with clear and organized processes, making it easy to navigate and work with."
"The level of automation achievable is really good. So, the custom workflow creation and Marketplace Actions improved our project's efficiency."
"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 product's most beneficial feature is the ability to create workflows within the solution."
 

Cons

"However, they need improvement with older servers due to storage space issues, which prevents me from giving a perfect score of ten."
"Depot needs improvement as it was stable but also very slow."
"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."
"In our company, procedures or rules need to be completed, which is not a problem with GitHub Actions but with our process."
"The minor drawback of GitHub Actions is the management of the dashboard and pipeline runs, which needs improvement. The dashboard for running pipelines could be better."
"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."
"The UI could be better."
"The reporting capabilities are somewhat limited."
"While GitHub Actions offers a range of functionalities, it is newer compared to more established tools such as Jenkins and Azure DevOps. There is still room for improvement, especially in areas concerning deeper capabilities akin to those provided by Jenkins and Azure DevOps."
"The main improvement would be to add support for more programming languages and frameworks."
"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."
 

Pricing and Cost Advice

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

Top Industries

By visitors reading reviews
Construction Company
38%
Manufacturing Company
13%
Comms Service Provider
13%
University
6%
Financial Services Firm
19%
Manufacturing Company
9%
Comms Service Provider
8%
Outsourcing Company
8%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
By reviewers
Company SizeCount
Small Business10
Midsize Enterprise4
Large Enterprise11
 

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 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?
While GitHub Actions offers a range of functionalities, it is newer compared to more established tools such as Jenkins and Azure DevOps. There is still room for improvement, especially in areas con...
What is your primary use case for GitHub Actions?
The main use case for GitHub Actions is maintaining enterprise repositories in private for security reasons, because we have multiple enterprise clients. We're using the premium GitHub service for ...
 

Comparisons

 

Overview

Find out what your peers are saying about Depot vs. GitHub Actions and other solutions. Updated: November 2026.
920,769 professionals have used our research since 2012.