CircleCI

Overview
ProductRatingMost Used ByProduct SummaryStarting Price
CircleCI
Score 9.5 out of 10
N/A
CircleCI is a software delivery engine from the company of the same name in San Francisco, that helps teams ship software faster, offering their platform for Continuous Integration and Continuous Delivery (CI/CD). Ultimately, the solution helps to map every source of change for software teams, so they can accelerate innovation and growth.
$0
for up to 6,000 build minutes and up to 5 active users per month
Pricing
CircleCI
Editions & Modules
Server
Contact Sales
Performance
starting at $15
per month
Scale
starting at $2000
per month
Offerings
Pricing Offerings
CircleCI
Free Trial
No
Free/Freemium Version
Yes
Premium Consulting/Integration Services
No
Entry-level Setup FeeNo setup fee
Additional Details
More Pricing Information
Community Pulse
CircleCI
Considered Both Products
CircleCI
Chose CircleCI
CircleCI shines with its specialized infrastructure. Its dedicated macOS runners ensure blazing-fast iOS builds, while intelligent Docker layer caching significantly reduces backend build times and costs. The ability to SSH directly into failed builds dramatically accelerates …
Chose CircleCI
Based on the cost for feature set that we needed we went with CircleCI. There were also more people on our team that knew how to use CircleCI already compared to other products which made it a preferred choice for ramp up. Other products were not as robust and quick to …
Chose CircleCI
CircleCI is the only product we've used.
Chose CircleCI
We use CircleCI when we need a good, independent CI/CD provider in an existing workflow. That said, we've begun investing more heavily in GitHub actions as it's closer to where our code is stored. CircleCI is a feature of a workflow, and can be filled by many different service …
Chose CircleCI
CircleCI is a sass product which means you don't need to maintain your own servers. This can also be a negative as you are dependent on their service. This also means you can't ssh into a machine to see what went wrong like you can with Jenkins. However for most users this …
Chose CircleCI
Because the Travis CI features are not very good, it has a lot of problems with concurrency and the uptime of the on-cloud solution was the worst we have ever tried.
Chose CircleCI
CircleCI is still being developed and worked on continually while TravisCI is not.
Chose CircleCI
CircleCI seemed to have a quicker setup than other similar products, with a good integration with GitHub repos. Projects are quick and easy to set up within the UI, and workflows can then be created off the back of those fairly intuitively. Clever interpretation of commit …
Chose CircleCI
CircleCI is the company that is innovating compared to the other ones. I think it's a great piece of software compared to other open source options that don't have as much functionality and improved capability over time.
Chose CircleCI
While the UI on CircleCI is not my favorite, it's leagues better than Travis CI. I really like Heroku CI much better, but the functionality is much more limited there. If Heroku CI had the same functionality as CircleCI, I probably wouldn't use CircleCI.
Chose CircleCI
Jenkins and Teamcity both have additional features that maybe you require, but they are also a lot more work to get set up and working. There's a much longer learning curve to getting these configured for a simple build. They're not hosted, so you have to maintain the …
Chose CircleCI
CircleCI does a lot of what we need it to do; however, I believe Jenkins is a better Continuous Integration tool. Jenkins has more capabilities and integrations. In addition, Jenkins is a much more widely used tool, which means more developers are familiar with it and have …
Chose CircleCI
Not having to manage / deal with a Jenkins server is fantastic. I don't have much personally against Jenkins. I've set up and run a Jenkins server before. It's just complexity that doesn't really have much to do with the business beyond getting our software to our customers. My …
Chose CircleCI
Since CircleCI gave us its infrastructure we don't have to worry about servers, provisioning and maintenance. Also CircleCI provides us great features to increase speed of builds by adding more containers to the build. Jenkins is the best open source alternative but it requires …
Chose CircleCI
Jenkins is usually self-hosted, Travis CI's infrastructure is largely unreliable (lots of tests time out for no discernable reason), and Semaphore encourages you to configure your CI/CD from a web UI. We like CircleCI because its hosted, our tests run largely as expected on …
Chose CircleCI
It was our CTO who did the evaluation, not me, but as I recall other services weren't as parallelizable. We knew we wanted to run on many containers simultaneously for fast test results.
Chose CircleCI
For us it really came down to CricleCI being the fastest and simples tool to get started with. The GitHub integration is slick and seamless and the scripting config file allowed us to configure our entire build system, including tests, in less than a day. It's very light weight …
Chose CircleCI
Circle was the first CI with simple setup, great documentation, and tight integration with GitHub. Using Jenkins was too much maintenance and overhead, TeamCity was limited in how we could customize it and run concurrent builds, TravisCI was not available for private repos when …
Chose CircleCI
Travis has full YML configuration in areas where CircleCI is slightly lacking still, which is great, but CircleCI offers more features, settings, and potential performance.

Codeship is simpler to use, you can use it entirely from their UI without modifying your Git repository at …
Chose CircleCI
Travis CI is great for open source projects – it's completely free, but CircleCI offers some support for closed projects as well. CircleCI has cheaper pricing plans, and you are able to customize them as much as you want. At Travis CI you can select only a predefined amount of …
Chose CircleCI
The biggest downside to CircleCI is that it doesn't support parameterized builds, that is testing your code against language version X and Y, or framework version A and B. Beyond that, it is really a great product.
Chose CircleCI
I had used Travis CI in some of my open source projects. However, it was too expensive for us so I looked for an alternative that was in our budget. Scrutinizer is also very useful, but also out of our budget. When we get larger I could see myself using Scrutinizer for quality …
Chose CircleCI
I think these three tools are just as good as the other except that Travis CI supports mobile a lot better but price wise, CircleCI is the best that I have found and is supports the need for a startup. For a long while, CircleCI had Docker support before Codeship but now, Codesh…
Best Alternatives
CircleCI
Small Businesses
GitLab
GitLab
Score 8.7 out of 10
Medium-sized Companies
GitLab
GitLab
Score 8.7 out of 10
Enterprises
GitLab
GitLab
Score 8.7 out of 10
All AlternativesView all alternatives
User Ratings
CircleCI
Likelihood to Recommend
8.0
(26 ratings)
Usability
10.0
(1 ratings)
Performance
7.8
(3 ratings)
Support Rating
6.9
(6 ratings)
User Testimonials
CircleCI
Likelihood to Recommend
CircleCI
Based on our experience, CircleCI is well-suited for automating mobile app release cycles. For example, to release an iOS app, you would need to build, sign, and upload it to TestFlight, which requires a dedicated Mac in the office. But with CircleCI, you can have macOS executors, so you don't have to manage a physical build machine. Another benefit is that CircleCI's certified AWS Orbs abstract away complex authentication and deployment logic, allowing us to build, push, and deploy Docker containers to Amazon ECS with minimal configuration and high reliability. CircleCI is less suited for smaller projects where the development and deployment are not that extensive, for example, a static site. Once you have built a static site, you probably won't make any further changes, so there's no point in paying for it.
Read full review
Pros
CircleCI
  • Automated builds! This is really why you get CircleCI, to automate the build process. This makes building your application far more reliable and repeatable. It can also run tests and verify your application is working as expected.
  • Simple. Unlike Jenkins, Teamcity, or other platforms, CircleCI doesn't need a lot of setup. It's completely hosted, so there's no infrastructure to set up. The config file does take a bit to understand, but if you follow their example and start with something small and add to it, you can get it up and going quicker than it first looks.
  • Scales easily. Again, since it's all cloud-based, you don't have to manage or scale infrastructure. Simply subscribe to the number of containers you want, and scaling up just means buying more containers.
Read full review
Cons
CircleCI
  • While configuration is easy, the config files can get very very long.
  • Price compared to some alternatives that are cheaper / free. Especially so if you are running multiple containers in parallel.
  • Have experienced numerous outages (3-5) in the last few months where CircleCI has been down.
  • Web documentation and tutorials haven't been as good as some of the competitors.
Read full review
Usability
CircleCI
The reliability & speed, it just works. The ability to spin up macOS runners and Docker containers on demand without managing hardware is a huge win. The Orbs system makes integrating with AWS and Slack incredibly easy, saving us weeks of custom scripting and providing real-time updates in our Slack channel. This makes it easy for us to track and ensures that everyone involved knows the status. Of course, it has drawbacks related to configuration complexity and, in some cases, cost transparency, but overall, it is an industry-standard, robust tool that solves our core infrastructure problems well.
Read full review
Performance
CircleCI
It's pretty snappy, even with using workflows with multiple steps and different docker images. I've seen builds take a long time if it's really involved, but from what I can tell, it's still at least on par if not faster than other build tools.
Read full review
Support Rating
CircleCI
Unless you have a reasonably large account, you're going to be mainly stuck reading their documentation. Which has improved somewhat over the years but is still extremely limited compared to a platform like Digital Ocean who invested in the documentation and a community to ensure it's kept up to date. If you can't find your answer there, you can be stuck.
Read full review
Alternatives Considered
CircleCI
Jenkins is usually self-hosted, Travis CI's infrastructure is largely unreliable (lots of tests time out for no discernable reason), and Semaphore encourages you to configure your CI/CD from a web UI. We like CircleCI because its hosted, our tests run largely as expected on their infrastructure, and we can configure it from a config file that we track in GitHub.
Read full review
Return on Investment
CircleCI
  • We pay over $5K/ month and we have high expectations for service. Sometimes I feel that we don't get the value, but only sometimes.
  • We have had to build our own application to keep state and broker releases and deployments. We call our app deployer. I feel that CircleCI could do more to understand our needs and possibly build additional features that would enable us to invest less in build and deployment infrastructure and justify paying more for Circle.
Read full review
ScreenShots