CircleCI Reviews in June 2026: User Ratings, Pros & Cons

Good. But lagging behind Github Actions

What do you like best? Good conceptual model for doing CI, good features, good UI. Better CI concepts. It offered simple integration with Github (obviously industry standard), good permission controls, especially across organizations. A relatively good UI and straightforward billing model (discounted when activated from Github). What do you dislike? Lack of sharable library and buy in for said feature from community. Seems "heavy". Multiple workflows would be really nice. ...

Great product

What do you like best? The integration with my testing suite and github What do you dislike? Nothing so far, I'm still figuring out all the features What problems are you solving with the product? What benefits have you realized? Testing automation, automating processes, reducing bugs.

Efficient, parallel continuous integration services

Fully-featured product with awesome UI/UX

What do you like best? I really love CircleCI's UI / UX. Being able to see builds spin up and run in real-time is perfect. I find everything very intuitive and useful. Whenever builds fail, I can very quickly find the problem and re-run the build. My favorite feature is begin able to SSH into the machine which has come in handy for some very tough to track down build failures. What do you dislike? When it comes to core features, there's really nothing I dislike. CircleCI does a great ...

Overall, the service is fine, only small items that might be improved

What do you like best? We are able to develop and test all of our apps, from Scala and Go to iOS and Android applications! It is built with a yaml file such that developers can add or change the build process without an comprehensive administrative CircleCI access. What do you dislike? The interface is often a bit complicated, as can be expected from any extremely configurable operation. But there are some tutorials available so you won't have to update the file again for a while ...

Best continuous integration platform, the most compleate, fast and with great support

What do you like best? The improvements on Cicle CI 2.0 lowered our build times by half and the workflow approach allows us to save even more time when rebuilding since the tests phase of an specific commit don't re-run, that's awesome! What do you dislike? Actually nothing I like it a lot maybe the overall build time can be improved Recommendations to others considering the product: The platform has been live long enough and constantly improving, that gives confidence in its ...

CircleCI the Best

What do you like best? Easy to manage even for non - developers. I got introduced CircleCI last year for my Android Application. Before that we used to have Jenkins for build porcess. After CircleCI I would prefer to go with CircleCI for my future apps as well. Recommended other teams to get into it. What do you dislike? User and application mapping may not happen for sometime Recommendations to others considering the product: Try it and find its best. What problems are you ...

Best CI tool with free plan

What do you like best? Free plan, lots of prebuilt orbs. Simple configuration. What do you dislike? Free plan limitations. No mac os enviroment in free plan. What problems are you solving with the product? What benefits have you realized? Not so powerful secrets and passwords manager. No first party terraform provider.

One of the best CI/CD platforms on the market

What do you like best? It's easy to start, a lot of resources, manual approval, quick, low cost and a very good resource management. Friendly YML and UI/UX. What do you dislike? The user-seat feature is a little overpriced, could be a little bit lighter. Recommendations to others considering the product: Simply the best one of the market. A lot to offer, ready-to-start, really good solution for those who need agility and a lot to explore. You can use any kind of OS (like linux, ...

CircleCi

What do you like best? The configuration was the only thing we had to do. After that It just runs and reports back to us via github seamlessly. It was very easy to write a config file and once it is in the repo it just works every time. The only tricky part was setting up custom env variables in the build... but even that was not hard What do you dislike? From time to time there are hiccups where Circle processes will just crash and run out of memory. It gives us the false impression ...