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

Split vs Tekton 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

Split
Ranking in Build Automation
21st
Average Rating
8.4
Reviews Sentiment
4.0
Number of Reviews
3
Ranking in other categories
No ranking in other categories
Tekton
Ranking in Build Automation
4th
Average Rating
7.8
Reviews Sentiment
6.8
Number of Reviews
37
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of July 2026, in the Build Automation category, the mindshare of Split is 0.6%, up from 0.0% compared to the previous year. The mindshare of Tekton is 4.7%, down from 11.8% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Build Automation Mindshare Distribution
ProductMindshare (%)
Tekton4.7%
Split0.6%
Other94.7%
Build Automation
 

Featured Reviews

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.
reviewer2741265 - PeerSpot reviewer
Software engineer at a manufacturing company with 10,001+ employees
Benefit from a smooth learning curve and efficient adaptability
After seeing Jenkins and Tekton, I think Tekton is quite built on top of Kubernetes, so the learning curve is minimal. If you are working with Kubernetes, then OpenShift created Tekton on top of that, making it easily adaptable. Tekton is highly customizable. With Kubernetes, we can customize on our own and create custom builders. If teams have time and want to make enhancements, they can do it themselves. Whatever OpenShift is providing regarding Tekton is sufficient. It is easy to use because we don't need to write every pod step every time. A proper DevOps engineer can help once or twice, and development teams can easily adapt to that, make small shell script changes in the steps, understand the process, and work with it.

Quotes from Members

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

Pros

"Split facilitated a culture of data-driven decision-making, allowing us to validate our ideas and providing measurable outcomes for decisions."
"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."
"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."
"Its seamless integration with Kubernetes, being built on top of it and utilizing Custom Resource Definitions, ensures a smooth experience within Kubernetes environments exclusively."
"The platform's most valuable feature is its cloud-native and Kubernetes-ready design."
"The tool offers flexibility and compatibility."
"The most valuable features of Tekton include the reusability of tasks, the clean UI interface, and the binding of services and secrets."
"Tekton has a user interface that facilitates time savings, making it more user-friendly than Jenkins."
"We just have some configuration files, and it will handle the deployments smoother and faster compared to CI/CD 2.0."
"I find it beneficial to show data from Tekton to another GitHub or Bitbucket pipeline."
"Tekton's inclusion in Kubernetes deployment offers better visibility on how Tekton is performing within a cluster. It is lightweight and not as heavy as Jenkins to maintain."
 

Cons

"Additionally, we tend to move towards other issues related to Split due to flickering issues, which we observed because of latency."
"There are areas where Split can be improved, particularly around advanced reporting and visualization capabilities."
"The UI of split.io can be improved."
"There might be occasional issues with storage or cluster-level logging, which can affect production."
"Improvements could include introducing a UI-based pipeline development feature, such as drag and drop, which would help individuals with limited technical knowledge start building pipelines."
"Initially, working with YAML configuration can be challenging using the solution."
"I'm a bit worried about scaling Tekton from the point of view of big CI/CD processes."
"RBAC is really needed for Tekton."
"One area for improvement is the number of CRDs created during installation. Tekton currently creates 10 to 11 CRDs, which can be overwhelming."
"It would be better if Tekton could show the YAML file while it is running, similar to GitHub pipelines, to provide more visibility on what's happening."
"Compared to traditional tools like Jenkins, Tekton lacks a lot of features. It's not efficient in managing conflicts between multiple pipelines."
 

Pricing and Cost Advice

Information not available
"The tool is open-source and free to use."
"The solution is open-source."
"The product is free and open-source."
"It is entirely open source and free of charge."
"Tekton is an open-source tool."
"The product is free of cost."
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.
 

Top Industries

By visitors reading reviews
No data available
Financial Services Firm
22%
Manufacturing Company
10%
Computer Software Company
7%
University
6%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
By reviewers
Company SizeCount
Small Business6
Large Enterprise4
By reviewers
Company SizeCount
Small Business11
Midsize Enterprise4
Large Enterprise23
 

Questions from the Community

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...
How does Tekton compare with Jenkins?
When you are evaluating tools for automating your own GitOps-based CI/CD workflow, it is important to keep your requirements and use cases in mind. Tekton deployment is complex and it is not very e...
What needs improvement with Tekton?
I didn't get the intention of scalability. Scalability means based on the load, it will automatically gain resources and run. The question of pipeline scalability remains unclear. It's quite easy t...
What is your primary use case for Tekton?
We use Tekton for build and deployments. For LMP testing, we use the Tekton pipeline. We also use GitHub CI/CD. For infrastructure pipelines and Infrastructure as Code (IaC), we use Tekton. Previou...
 

Comparisons

No data available
 

Overview

 

Sample Customers

Information Not Available
The Home Depot, PayPal, Target, HSBC, McKesson, Oncology Venture
Find out what your peers are saying about Split vs. Tekton and other solutions. Updated: June 2026.
902,988 professionals have used our research since 2012.