

Find out in this report how the two Build Automation solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI.
Before Codefresh, we had to plan the strategy, write the configuration file, and run everything; it used to take two to three days to plan and implement, but now it is a one-time job, so it can be done in ten to fifteen minutes.
In terms of dollars, considering both engineering cost and infrastructure cost, I would say the savings are more than at least $10,000 to $15,000.
They actually understand Kubernetes and container architecture, which makes a huge difference.
One of the team members had a few configurations that we suggested to Codefresh, and they took it and applied those configurations within Codefresh's product.
Unlike our old Jenkins setup where adding more builds often meant the master node would struggle and we would run out of executors, Codefresh is Kubernetes-native, so it scales horizontally by design.
Codefresh's scalability is 10 out of 10; it is very scalable.
Codefresh handles scalability as my workloads grow by allowing us to implement techniques such as HPA.
Codefresh is generally very quick, and the experience is very pleasant and good.
My environment is very secure and stable, and the accuracy needed during a process of AI capabilities does not disappoint me.
In my experience, Codefresh is stable with not many challenges in hiccups or in clusters, but it is somewhat complex.
Stability-wise, it is very stable, and we can seamlessly integrate.
I gave it a nine because it has automated Kubernetes deployments, which are not easy to achieve through CI/CD, and it is centralized, integrating GitOps, Argo CD, and Docker-based containerized application deployment, making it a useful tool.
Although the visibility into Kubernetes is excellent, I would love to see out-of-the-box cost optimization metrics.
Some design decisions made us move away from Codefresh to another vendor for pipelines.
Scalability means based on the load, it will automatically gain resources and run.
Since we are an enterprise-level team, we moved past the basic tier onto a custom contract.
Codefresh is nice because we used to share the licensing, cluster creation, and those accounts around products.
Codefresh eliminates the manual process and provides a centralized platform for continuous integration, continuous delivery, and GitOps-based release management.
The best feature of Codefresh is the GitOps control plane, which provides a single unified view of all Argo CD runtimes and clusters on the dashboard.
In my opinion, the best features Codefresh offers are extensibility, flexibility, a lot of features, and it is also very fast.
Tekton is highly customizable. With Kubernetes, we can customize on our own and create custom builders.
| Product | Mindshare (%) |
|---|---|
| Tekton | 4.7% |
| Codefresh | 0.9% |
| Other | 94.4% |
| Company Size | Count |
|---|---|
| Small Business | 11 |
| Midsize Enterprise | 4 |
| Large Enterprise | 23 |
Codefresh is a progressive tool tailored for enhancing DevOps teams, enabling swift deployments with its Kubernetes-native architecture while supporting GitOps control to provide a centralized view of Argo CD runtimes and clusters.
Codefresh stands out by integrating real-time application health monitoring, efficient artifact management, and smart deployment strategies. Automation features reduce manual efforts allowing seamless version control integration. While users appreciate its extensibility and quick third-party tool integrations, there is room for improvements in UI performance with large logs and the promotion process between environments. Suggested enhancements include more features for cost optimization and capabilities within GCP. Taking advantage of Kubernetes and YAML proficiency for setup can be challenging, despite comprehensive documentation.
What are the key features of Codefresh?In industries relying on microservices and Kubernetes, Codefresh serves as a control plane integrated with Argo CD, facilitating the management of CI/CD pipelines. It automates Docker image builds and updates, decreasing manual errors and delays. Widely utilized for deploying containerized applications across environments like production and staging, it aids in infrastructure management and enhances the developer platform experience.
Tekton is a cloud-native CI/CD tool preferred for its integration with Kubernetes. It offers customizable pipelines and efficient management of tasks, appealing to those handling complex deployments. Its open-source design and ease of use support its widespread adoption.
Designed for Kubernetes, Tekton provides a robust environment for continuous integration and deployment. It supports cloud-native design, allowing seamless automation of building, testing, and deployment processes. Users benefit from customizable solutions with reusable tasks and parallel execution capabilities, optimizing CI/CD processes via a user-friendly dashboard. Despite its challenges with storage and logging, Tekton remains an adaptable tool that integrates well with other applications, like Argo CD. However, its deployment accessibility, scalability in complex environments, and documentation need enhancement to improve user onboarding and security management.
What features make Tekton stand out?Industries often employ Tekton within Kubernetes and OpenShift for its automation capabilities in CI/CD pipelines. Its use extends to automating build, test, and deployment processes in microservices management. Tekton's integration with tools like Argo CD facilitates superior deployment, making it the preferred choice for efficient orchestration in cloud-native environments over competitors such as Jenkins.
We monitor all Build Automation reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.