Dev Ops Consultant at a outsourcing company with 1,001-5,000 employees
Real User
Top 5
Jun 24, 2026
The best features Codefresh offers are CI/CD pipelines, and I do not need to use them because in my scenario, GitOps replaced the whole process of CI/CD. This gives me more flexibility and security, eliminating the need for manual implementation and testing of all steps in production. We can reproduce all solutions in different branches using GitOps practices. I have already obtained a certification in GitOps from Argo CD and Codefresh because it helped me gain clarity and direction for what to do and the best approach using GitOps. Codefresh's AI capabilities give me much more visibility in large environments because we can replace some manual tasks with AI capabilities. Codefresh integrates with my existing DevOps toolchain through integration by Argo CD on the GitOps process. It has much more flexibility and gives me much replaceability for all I need in my environment. Codefresh handles compliance requirements in my organization because we do not have manual intervention for developers and other people. We only need to run by using least access security, least privilege, and zero-trust policies. We can organize and provide much more security in the environment. Codefresh supports collaboration across different teams or departments by allowing us to use pull requests by environment on the Git tool. This way, we can funnel things and not have a bottleneck in the environment. We need a parallel and serial utilization of the environments, and we can promote each feature the right way. Codefresh helps me with disaster recovery or rollback scenarios by tag or number of resources. In this case, the number of the branch or version of the commit of the branch. We can promote the least impacted resources, and the self-healing in the environment gives much more maturity to the software. Codefresh helps with cost optimization in my organization by identifying resources that are not created manually, and we can make them auditable by GitOps. Codefresh supports observability and monitoring in my environment by letting us know the exact moment when each team or group is running any deployment or any change on the infrastructure. We have total control over each resource and environment, and this helps us with monitoring and observability, so we do not have surprises during the day. My advice for others looking into using Codefresh is to study your environment. Before implementing GitOps, you need to check exactly what you need and what you do in your environment to get the best advantage you can during the usage of GitOps. I rate Codefresh nine out of ten based on my overall experience.
The advice I would give to others looking into using Codefresh is that they need to have that budget. Whoever wants to use Codefresh needs to have the budget and a return on investment. They need to have money from the client or vendors so that they can invest in Codefresh. Otherwise, it is a nice solution if the money is there. Somebody can log into Codefresh and do the project things. I would rate my overall experience with Codefresh a seven out of ten.
Previously, the process had to be done by three to four DevOps engineers, which included writing the YAML file, managing the containers running in Kubernetes, managing the configuration file, and checking for successful deployments in development and staging before doing blue-green and canary deployments, but now everything has been automated. Codefresh has made the most positive impact by reducing errors; sometimes humans make errors, especially during high-pressure times or with a high workload. It can be hard to configure the files, and we can misconfigure them, leading to wrong deployments, but with the one-time job of configuring the Kubernetes configuration file, it is very easy for repetitive tasks, and it has also reduced repetitive tasks by being triggered automatically once the code is pushed. Initially, we tried the free trial application, and now we are using a team plan which is managed by the upper teams. I would rate this product a nine out of ten.
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...
The best features Codefresh offers are CI/CD pipelines, and I do not need to use them because in my scenario, GitOps replaced the whole process of CI/CD. This gives me more flexibility and security, eliminating the need for manual implementation and testing of all steps in production. We can reproduce all solutions in different branches using GitOps practices. I have already obtained a certification in GitOps from Argo CD and Codefresh because it helped me gain clarity and direction for what to do and the best approach using GitOps. Codefresh's AI capabilities give me much more visibility in large environments because we can replace some manual tasks with AI capabilities. Codefresh integrates with my existing DevOps toolchain through integration by Argo CD on the GitOps process. It has much more flexibility and gives me much replaceability for all I need in my environment. Codefresh handles compliance requirements in my organization because we do not have manual intervention for developers and other people. We only need to run by using least access security, least privilege, and zero-trust policies. We can organize and provide much more security in the environment. Codefresh supports collaboration across different teams or departments by allowing us to use pull requests by environment on the Git tool. This way, we can funnel things and not have a bottleneck in the environment. We need a parallel and serial utilization of the environments, and we can promote each feature the right way. Codefresh helps me with disaster recovery or rollback scenarios by tag or number of resources. In this case, the number of the branch or version of the commit of the branch. We can promote the least impacted resources, and the self-healing in the environment gives much more maturity to the software. Codefresh helps with cost optimization in my organization by identifying resources that are not created manually, and we can make them auditable by GitOps. Codefresh supports observability and monitoring in my environment by letting us know the exact moment when each team or group is running any deployment or any change on the infrastructure. We have total control over each resource and environment, and this helps us with monitoring and observability, so we do not have surprises during the day. My advice for others looking into using Codefresh is to study your environment. Before implementing GitOps, you need to check exactly what you need and what you do in your environment to get the best advantage you can during the usage of GitOps. I rate Codefresh nine out of ten based on my overall experience.
The advice I would give to others looking into using Codefresh is that they need to have that budget. Whoever wants to use Codefresh needs to have the budget and a return on investment. They need to have money from the client or vendors so that they can invest in Codefresh. Otherwise, it is a nice solution if the money is there. Somebody can log into Codefresh and do the project things. I would rate my overall experience with Codefresh a seven out of ten.
Previously, the process had to be done by three to four DevOps engineers, which included writing the YAML file, managing the containers running in Kubernetes, managing the configuration file, and checking for successful deployments in development and staging before doing blue-green and canary deployments, but now everything has been automated. Codefresh has made the most positive impact by reducing errors; sometimes humans make errors, especially during high-pressure times or with a high workload. It can be hard to configure the files, and we can misconfigure them, leading to wrong deployments, but with the one-time job of configuring the Kubernetes configuration file, it is very easy for repetitive tasks, and it has also reduced repetitive tasks by being triggered automatically once the code is pushed. Initially, we tried the free trial application, and now we are using a team plan which is managed by the upper teams. I would rate this product a nine out of ten.