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
3rd
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
41st
Average Rating
8.6
Reviews Sentiment
3.5
Number of Reviews
2
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of June 2026, in the Build Automation category, the mindshare of GitHub Actions is 6.3%, 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 Actions6.3%
Split0.6%
Other93.1%
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.
AmitGupta1 - PeerSpot reviewer
SDE 1 at a outsourcing company with 1,001-5,000 employees
Experimentation has boosted conversion rates and guides faster, safer feature decisions
The best features Split offers include A/B experimentation itself, multivariant experiments, and a limit exposure feature that allows us to manipulate the traffic going through the split. We can decide to send only 10% of the traffic or 100%, depending on our limit exposure design. Additionally, we have a tracking mechanism and live trail monitoring, making these tools really good. The limit exposure feature in Split decides if the experiment is healthy or not. For example, we enroll the experiment for 5% of users and check the experiment's healthiness from that. We verify if the on variant is working properly and if the off variant is functioning well to ensure that extra users are not affected if something goes wrong. That is the main feature of limit exposure. I would say Split has impacted us a lot because we use it for gating new features while going into production, ensuring that those features are not rolled out prematurely. Overall, our organization is positive about using Split.

Quotes from Members

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

Pros

"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."
"We can trigger files manually or automate processes."
"The product's most beneficial feature is the ability to create workflows within the solution."
"I am familiar with the entire life cycle of the product."
"The solution has saved us approximately 20% in terms of efficiency and productivity."
"GitHub Actions helps automate the deployment process, eliminating manual copying and testing, which saves time and minimizes errors."
"It offers numerous built-in features for pipeline management, release management, and even work item tracking on boards, which makes it a versatile tool that seamlessly integrates with hardware and facilitates optimization."
"I have optimized job execution time by running test scripts in parallel and creating multiple pipelines; we've significantly reduced execution times. What could take 50 minutes can be cut down to just 8 to 10 minutes through these optimizations."
"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 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

"Improvements could be made in terms of time-saving capabilities and resolving potential complexities in centralized workflows."
"The solution's integration capabilities and UI are areas of concern where improvement is required to make the product more user-friendly."
"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."
"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."
"There is a part that detects outdated libraries. If that feature could be more intuitive and informative, that would be nice."
"In our company, procedures or rules need to be completed, which is not a problem with GitHub Actions but with our process."
"Sometimes it is quite complex to commit code from our local system to the GitHub repository; creating a folder in GitHub can be tedious."
"The main improvement would be to add support for more programming languages and frameworks."
"The UI of split.io can be improved."
"Additionally, we tend to move towards other issues related to Split due to flickering issues, which we observed because of latency."
 

Pricing and Cost Advice

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

Top Industries

By visitors reading reviews
Financial Services Firm
21%
Manufacturing Company
9%
Comms Service Provider
7%
University
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 Business6
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 is your experience regarding pricing and costs for Split?
I have used Split for setup, cost, licensing, and pricing.
What needs improvement with Split?
Split is a strong feature management platform, but there are opportunities for improvement. Simpler onboarding with guided workflows and beginner-friendly documentation would help new users get sta...
What is your primary use case for Split?
Split has helped streamline our cloud-native application delivery by enabling safe feature rollouts and controlled releases through feature flags. The ability to separate deployment from release re...
 

Comparisons

No data available
 

Overview

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