I would advise organizations or individual developers who are trying to use CircleCI to begin with basic pipelines and gradually move to advanced workflows such as deployment automation, parallel jobs, and approvals. You should avoid overcomplicating from day one. You need to plan workflows properly, use caching, parallelism, and reusable components to optimize performance and reduce execution time. Since CircleCI uses a usage-based pricing model, you should regularly monitor pipeline usage and optimize long-running or unnecessary jobs. I rate CircleCI an eight out of ten because I think some points can be improved, such as better debugging and error insights, a more intuitive UI for complex workflows, and enhanced cost visibility and optimization recommendations.
I always follow the official documentation provided for CircleCI, and it is comprehensive. CircleCI's official documentation is sufficient and covers everything I need. As I mentioned, we are only users of CircleCI, so I am uncertain how to describe the specific benefits for the customer's organization in their environment. I have provided this review with a rating of 8.
I rate CircleCI 8 out of 10 overall. It is a reliable and efficient CI/CD platform that significantly helps with automation, faster feedback, and improved release quality. It has strong capabilities such as parallel execution, integration, and scalable pipelines. I give it an 8 because there is still room for improvement in areas such as easier onboarding and smarter debugging. I specifically chose 8 because the onboarding steps can be easier. Some areas still feel they can be more refined in day-to-day usage. For example, I once spent considerable time debugging failed pipelines longer than expected. For CircleCI to become a 9 or 10, I would appreciate more intelligent troubleshooting, simpler pipeline setup for new users, stronger analytics around test stability, and if they can provide some trends or a graphical interface, it would help significantly. My advice is that it is easier to use CircleCI than traditional Jenkins. If anyone wants to simplify their pipelines, choosing CircleCI instead of overloading with Jenkins would be a smart move. In summary, I have shared much about CircleCI according to my experience. I feel it is a faster tool compared to traditional Jenkins, and as a QA, I feel more tech-aligned and product quality-aligned using CircleCI. My overall review rating for CircleCI is 8 out of 10.
I would rate CircleCI a nine out of ten. I pick nine out of ten because most of the things are already there. It is very easy to use, easy to configure, integrations are available, and most of the time, most of the features are user-friendly. For others looking into using CircleCI, I would advise they can definitely use CircleCI for CI/CD purposes, potentially doing a POC, identifying their use cases, and checking the integration features, which is a significant advantage. If everything goes well, they can try using CircleCI for their production environment. We are using CircleCI on the cloud. My overall rating for this review is nine.
CircleCI is an amazing tool. It is fast, modern, and integrates with most systems, whether repositories or notification systems. CircleCI is a very powerful tool and you should at least try it once to see how powerful, amazing, and fast it is. I believe CircleCI is one of the best platforms in its category due to how amazing, fast, and scalable it is. This review process represents one of the most modern technical ways of gathering feedback. I gave this product a rating of nine out of ten.
My advice to others looking into using CircleCI is to use it if you want to collaborate with multiple teams and prefer structured, user-friendly solutions with more integrations with tools. CircleCI is a perfect solution for multi-staging and jobs. Regarding compliance or regulatory requirements in my organization, we are not currently focusing on that area, so I am not aware of those concerns. I would rate CircleCI an eight out of ten overall.
My advice to others looking into using CircleCI is to just not get overwhelmed by the complexity, particularly the config complexity. Just try to learn it, as now AI tools will definitely be there to help you out. Start using it, and once you get used to it, ask them to have a conversation over the pricing aspect.
Managing Technical Consultant - Solution Architect at NTT DATA
Real User
Top 10
Jan 24, 2026
I really appreciate the good speed, which is faster and definitely the most important feature for me.To ensure that security and compliance requirements are met while using CircleCI, we utilize restricted contexts for secrets along with short-lived credentials. We follow some regulatory guidelines, ensuring that every job runs in an isolated environment, either in a Docker container or a virtual machine. Furthermore, we maintain secret rotation and use secure API tokens while implementing appropriate access controls. I rate this product six out of ten.
SRE coordinator at a financial services firm with 201-500 employees
Real User
Top 10
Dec 2, 2025
For others looking into using CircleCI, study thoroughly about CircleCI's Orbs because they are quite complicated. The overall review rating for CircleCI is 6 out of 10.
I recommend the product for end-to-end development for highly scalable, distributed, and microservices, where there are more than 100-200 services integrating together to build a platform. Overall, I rate the solution a seven out of ten.
CircleCI is a continuous integration and delivery platform that automates software development, streamlining the process for engineers and developers. It's valued for its ability to enhance development speed while maintaining high software quality. Known for its robust CI/CD capabilities, CircleCI supports a wide range of programming languages and integrations, allowing teams to build and deploy code with efficiency and reliability. Its flexibility and automation features help teams quickly...
I would advise organizations or individual developers who are trying to use CircleCI to begin with basic pipelines and gradually move to advanced workflows such as deployment automation, parallel jobs, and approvals. You should avoid overcomplicating from day one. You need to plan workflows properly, use caching, parallelism, and reusable components to optimize performance and reduce execution time. Since CircleCI uses a usage-based pricing model, you should regularly monitor pipeline usage and optimize long-running or unnecessary jobs. I rate CircleCI an eight out of ten because I think some points can be improved, such as better debugging and error insights, a more intuitive UI for complex workflows, and enhanced cost visibility and optimization recommendations.
I always follow the official documentation provided for CircleCI, and it is comprehensive. CircleCI's official documentation is sufficient and covers everything I need. As I mentioned, we are only users of CircleCI, so I am uncertain how to describe the specific benefits for the customer's organization in their environment. I have provided this review with a rating of 8.
I rate CircleCI 8 out of 10 overall. It is a reliable and efficient CI/CD platform that significantly helps with automation, faster feedback, and improved release quality. It has strong capabilities such as parallel execution, integration, and scalable pipelines. I give it an 8 because there is still room for improvement in areas such as easier onboarding and smarter debugging. I specifically chose 8 because the onboarding steps can be easier. Some areas still feel they can be more refined in day-to-day usage. For example, I once spent considerable time debugging failed pipelines longer than expected. For CircleCI to become a 9 or 10, I would appreciate more intelligent troubleshooting, simpler pipeline setup for new users, stronger analytics around test stability, and if they can provide some trends or a graphical interface, it would help significantly. My advice is that it is easier to use CircleCI than traditional Jenkins. If anyone wants to simplify their pipelines, choosing CircleCI instead of overloading with Jenkins would be a smart move. In summary, I have shared much about CircleCI according to my experience. I feel it is a faster tool compared to traditional Jenkins, and as a QA, I feel more tech-aligned and product quality-aligned using CircleCI. My overall review rating for CircleCI is 8 out of 10.
I would rate CircleCI a nine out of ten. I pick nine out of ten because most of the things are already there. It is very easy to use, easy to configure, integrations are available, and most of the time, most of the features are user-friendly. For others looking into using CircleCI, I would advise they can definitely use CircleCI for CI/CD purposes, potentially doing a POC, identifying their use cases, and checking the integration features, which is a significant advantage. If everything goes well, they can try using CircleCI for their production environment. We are using CircleCI on the cloud. My overall rating for this review is nine.
CircleCI is an amazing tool. It is fast, modern, and integrates with most systems, whether repositories or notification systems. CircleCI is a very powerful tool and you should at least try it once to see how powerful, amazing, and fast it is. I believe CircleCI is one of the best platforms in its category due to how amazing, fast, and scalable it is. This review process represents one of the most modern technical ways of gathering feedback. I gave this product a rating of nine out of ten.
My advice to others looking into using CircleCI is to use it if you want to collaborate with multiple teams and prefer structured, user-friendly solutions with more integrations with tools. CircleCI is a perfect solution for multi-staging and jobs. Regarding compliance or regulatory requirements in my organization, we are not currently focusing on that area, so I am not aware of those concerns. I would rate CircleCI an eight out of ten overall.
My advice to others looking into using CircleCI is to just not get overwhelmed by the complexity, particularly the config complexity. Just try to learn it, as now AI tools will definitely be there to help you out. Start using it, and once you get used to it, ask them to have a conversation over the pricing aspect.
I really appreciate the good speed, which is faster and definitely the most important feature for me.To ensure that security and compliance requirements are met while using CircleCI, we utilize restricted contexts for secrets along with short-lived credentials. We follow some regulatory guidelines, ensuring that every job runs in an isolated environment, either in a Docker container or a virtual machine. Furthermore, we maintain secret rotation and use secure API tokens while implementing appropriate access controls. I rate this product six out of ten.
For others looking into using CircleCI, study thoroughly about CircleCI's Orbs because they are quite complicated. The overall review rating for CircleCI is 6 out of 10.
I recommend the product for end-to-end development for highly scalable, distributed, and microservices, where there are more than 100-200 services integrating together to build a platform. Overall, I rate the solution a seven out of ten.
I rate CircleCI an eight out of ten.