CircleCI vs Concourse

Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

CircleCI
CircleCI

3.3K
1.9K
+ 1
939
Concourse
Concourse

128
109
+ 1
38
Add tool

CircleCI vs Concourse: What are the differences?

CircleCI: Automate your development process quickly, safely, and at scale. Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp; Concourse: Pipeline-based CI system written in Go. Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control.

CircleCI and Concourse can be primarily classified as "Continuous Integration" tools.

"Github integration" is the top reason why over 218 developers like CircleCI, while over 8 developers mention "Real pipelines" as the leading cause for choosing Concourse.

Concourse is an open source tool with 3.92K GitHub stars and 472 GitHub forks. Here's a link to Concourse's open source repository on GitHub.

Instacart, Lyft, and StackShare are some of the popular companies that use CircleCI, whereas Concourse is used by Starbucks, DigitalOcean, and HelloFresh. CircleCI has a broader approval, being mentioned in 925 company stacks & 372 developers stacks; compared to Concourse, which is listed in 18 company stacks and 17 developer stacks.

- No public GitHub repository available -

What is CircleCI?

Continuous integration and delivery platform helps software teams rapidly release code with confidence by automating the build, test, and deploy process. Offers a modern software development platform that lets teams ramp.

What is Concourse?

Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose CircleCI?
Why do developers choose Concourse?

Sign up to add, upvote and see more prosMake informed product decisions

What are the cons of using CircleCI?
What are the cons of using Concourse?
What companies use CircleCI?
What companies use Concourse?

Sign up to get full access to all the companiesMake informed product decisions

What tools integrate with CircleCI?
What tools integrate with Concourse?
    No integrations found

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to CircleCI and Concourse?
    Jenkins
    In a nutshell Jenkins CI is the leading open-source continuous integration server. Built with Java, it provides over 300 plugins to support building and testing virtually any project.
    Travis CI
    Free for open source projects, our CI environment provides multiple runtimes (e.g. Node.js or PHP versions), data stores and so on. Because of this, hosting your project on travis-ci.com means you can effortlessly test your library or applications against multiple runtimes and data stores without even having all of them installed locally.
    Codeship
    Codeship runs your automated tests and configured deployment when you push to your repository. It takes care of managing and scaling the infrastructure so that you are able to test and release more frequently and get faster feedback for building the product your users need.
    Azure DevOps
    Azure DevOps provides unlimited private Git hosting, cloud build for continuous integration, agile planning, and release management for continuous delivery to the cloud and on-premises. Includes broad IDE support.
    CloudBees
    Enables organizations to build, test and deploy applications to production, utilizing continuous delivery practices. They are focused solely on Jenkins as a tool for continuous delivery both on-premises and in the cloud.
    See all alternatives
    Decisions about CircleCI and Concourse
    No stack decisions found
    Interest over time
    Reviews of CircleCI and Concourse
    Review ofCircleCICircleCI

    I use CircleCI as part of a cross platform mobile app to build and test the app as well as deploying .apk files to an s3 bucket.

    Alongside CircleCI this repo also has a TravisCI setup for iOS. The CircleCI build has always been quicker and since moving from CircleCI v1 to CircleCI v2 it blows the TravisCI build out of the water. I'm really impressed with the performance gains from moving to v2. I'm pretty sure I could achieve similar results in Travis as well, but it was really easy to setup the Android CI build in Circle making use of Docker.

    Avatar of regentgal
    VP of Engineering at Jetpack Workflow
    Review ofCircleCICircleCI

    After trying several CI systems, we stuck with CircleCI because of the inference engine in CircleCI 1.0 made setup a breeze. We were up and running quickly. Builds are reliable, nicely integrated into GitHub, and anytime we've had a question, the support team was there to help. The 2.0 system provides Docker support and far more customization and is still fairly easy to set up with helpful documentation.

    Review ofCircleCICircleCI

    CircleCI has become our CI of choice. The UI is really good and it has all the integrations we need. The 2.0 upgrade was not yet possible for one of our projects due to outdated gems, however, I have been able to get it working for a different one.

    Avatar of ryuzaki01
    Information Technology
    Review ofCircleCICircleCI

    It help us with the automated build and test and also provide us with the build artifacts which we can use for the deployment also give use archive for each of our build, this things save us alot of time and cost

    Review ofCircleCICircleCI

    We use CircleCI to deploy to server. It is much easier than other websites like Travis especially for the free tier. It is especially useful for open source projects that need private access behind the scenes.

    How developers use CircleCI and Concourse
    Avatar of AngeloR
    AngeloR uses CircleCICircleCI

    We originally used CircleCI as our self-contained build system for our internal node modules. It was very easy to set up and configure. Unfortunately we ended up stepping away from it to Jenkins and then CodePipeline due to better integration with our various applications.

    Avatar of Jeff Flynn
    Jeff Flynn uses CircleCICircleCI

    We prefer CircleCI because we care about testing our apps. We found it is better to invest the time writing rSPEC tests to ensure we don't insert any regression bugs with new branches. It's also nice to have a fully-automated deployment process from GitHub to Heroku.

    Avatar of Matt Welke
    Matt Welke uses CircleCICircleCI

    Used for CI/CD for all proofs of concept and personal projects, because of ease of use, GitHub integrations, and free tier.

    Also used for example repos hosted in GitHub, paired with Dependabot, so that example repo dependencies are kept up to date.

    Avatar of Marc3842h
    Marc3842h uses CircleCICircleCI

    CircleCI is used as continues integration system for shiro and all of its modules.

    It automatically deploys the latest GitHub commit to https://shiro.host/.

    Avatar of jasonmjohnson
    jasonmjohnson uses CircleCICircleCI

    CircleCI will be used for deployment and continuous integration using a scripted configuration that deploys to Amazon EC2.

    Avatar of Tom Staijen
    Tom Staijen uses ConcourseConcourse

    Pipeline for terraform (infrastructure) and ansible (application).

    How much does CircleCI cost?
    How much does Concourse cost?
    Pricing unavailable
    News about Concourse
    More news