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

GitHub Actions vs Split 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

GitHub Actions
Ranking in Build Automation
2nd
Average Rating
8.4
Reviews Sentiment
5.4
Number of Reviews
23
Ranking in other categories
No ranking in other categories
Split
Ranking in Build Automation
21st
Average Rating
8.2
Reviews Sentiment
4.9
Number of Reviews
4
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of August 2026, in the Build Automation category, the mindshare of GitHub Actions is 7.0%, down from 11.5% compared to the previous year. The mindshare of Split is 0.6%, up from 0.0% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
GitHub Actions7.0%
Split0.6%
Other92.4%
Build Automation
 

Featured Reviews

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.
PM
Senior Decision Scientist at Tesco
Data-driven experiments have transformed feature rollouts and now validate business impact
I feel that overall my experience with Split has been positive regarding necessary improvements, particularly around user experience and enhancements to the user interface, especially for larger teams. As experimentation programs grow, users must navigate many feature flags and different environments, so making discovery, organization, and lifecycle management more intuitive would be beneficial. While Split integrates well with many tools, additional connectivity with analytics and BI reporting platforms could provide a more seamless experience for organizations. There are areas where Split can be improved, particularly around advanced reporting and visualization capabilities. While the platform manages experiments and feature rollouts effectively, having more robust, out-of-the-box reporting options would allow business stakeholders to interpret results without relying on external tools. Additionally, as organizations grow, managing and overseeing feature flags becomes more challenging, so enhancing governance capabilities would be beneficial. In terms of user experience and integrations, I think the platform could enhance those areas as well. Users often need to navigate through a large number of feature flags as experimentation programs scale, so improvements to the user interface that simplify discovery, organization, and lifecycle management would be valuable, especially for larger teams. While Split integrates effectively with many tools, increasing connectivity with analytics and BI reporting could help organizations enhance their operations.

Quotes from Members

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

Pros

"The most valuable feature of GitHub Actions is the ability to automate various tasks, such as backups and deployments, to ease the development workflow."
"It saves a lot of time with GitHub Actions; especially, the whole process if done manually might cost us a lot, maybe a week or two weeks just for deployment, but now with automation, we automate the deployment effectively."
"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 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."
"It is a very stable solution as we have not faced any issues."
"GitHub Actions helps automate the deployment process, eliminating manual copying and testing, which saves time and minimizes errors."
"The most valuable feature of the solution is that it is a good product that offers stability and performance."
"Creating workflows in YAML format is straightforward and easy to comprehend. This includes both understanding and writing workflows. Additionally, the downloading aspect for third-party instances can also be easily done. It's worth noting that vulnerability analysis and similar tasks should be part of our automation through data workflows. Furthermore, we can break down our processes step by step, starting from building, then moving on to analysis, testing, and finally deploying in production and the clear environment. All of these tasks can be efficiently managed within this platform."
"Split facilitated a culture of data-driven decision-making, allowing us to validate our ideas and providing measurable outcomes for decisions."
"Split has increased some of our CVR; for example, in a recent pop-up model experiment, our conversion was around 15% and once we started the experiment, the on-variant won by increasing the CVR up to 35%, making it a really good tool for determining which particular feature would deliver the expected CVR."
"Split has positively impacted my organization by improving both developer experience and customer experience."
"Split is a great way to handle the config based on checks and in a dynamic way if you want to control your software without doing any deployment."
 

Cons

"In terms of improvements, I think better logging for debugging purposes would be helpful, especially for complex workflows."
"The reporting capabilities are somewhat limited."
"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."
"GitHub Actions lacks a feature for automating the build process for mobile applications."
"Improvements could be made in terms of time-saving capabilities and resolving potential complexities in centralized workflows."
"In our company, procedures or rules need to be completed, which is not a problem with GitHub Actions but with our process."
"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."
"Switching between hosted and self-hosted agents can be a bit complex, as self-hosted agents need to be provisioned in platforms like Azure or AWS."
"The UI of split.io can be improved."
"There are areas where Split can be improved, particularly around advanced reporting and visualization capabilities."
"Additionally, we tend to move towards other issues related to Split due to flickering issues, which we observed because of latency."
"Initially, I had difficulty finding analytics and understanding setup."
 

Pricing and Cost Advice

"It's low-priced. Not high, but definitely low."
"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 is free and open platform, so I would rate it 1 out of 10."
"The product is slightly more expensive than some alternatives."
"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."
"The tool's price is okay and reasonable."
"For our basic usage, we didn't have to pay."
Information not available
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
Financial Services Firm
20%
Manufacturing Company
9%
Comms Service Provider
7%
Outsourcing Company
6%
No data available
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business9
Midsize Enterprise4
Large Enterprise11
By reviewers
Company SizeCount
Small Business7
Large Enterprise4
 

Questions from the Community

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 ...
What needs improvement with Split?
I feel that overall my experience with Split has been positive regarding necessary improvements, particularly around user experience and enhancements to the user interface, especially for larger te...
What is your primary use case for Split?
I have used Split to perform AB tests, controlled releases, and measure business outcomes. While my focus has been on analytics and the decision-making side, I have also used this platform for admi...
 

Comparisons

 

Overview

Find out what your peers are saying about GitHub Actions vs. Split and other solutions. Updated: August 2026.
909,725 professionals have used our research since 2012.