Need advice about which tool to choose?Ask the StackShare community!
Concourse vs TeamCity: What are the differences?
Developers describe Concourse as "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. On the other hand, TeamCity is detailed as "TeamCity is an ultimate Continuous Integration tool for professionals". TeamCity is a user-friendly continuous integration (CI) server for professional developers, build engineers, and DevOps. It is trivial to setup and absolutely free for small teams and open source projects.
Concourse and TeamCity can be primarily classified as "Continuous Integration" tools.
"Real pipelines" is the top reason why over 8 developers like Concourse, while over 52 developers mention "Easy to configure" as the leading cause for choosing TeamCity.
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.
According to the StackShare community, TeamCity has a broader approval, being mentioned in 168 company stacks & 51 developers stacks; compared to Concourse, which is listed in 18 company stacks and 17 developer stacks.
I'm planning to setup complete CD-CD setup for spark and python application which we are going to deploy in aws lambda and EMR Cluster. Which tool would be best one to choose. Since my company is trying to adopt to concourse i would like to understand what are the lack of capabilities concourse have . Thanks in advance !

I would definetly recommend Concourse to you, as it is one of the most advanced modern methods of making CI/CD while Jenkins is an old monolithic dinosaur. Concourse itself is cloudnative and containerbased which helps you to build simple, high-performance and scalable CI/CD pipelines. In my opinion, the only lack of skills you have with Concourse is your own knowledge of how to build pipelines and automate things. Technincally there is no lack, i would even say you can extend it way more easily. But as a Con it is more easy to interact with Jenkins if you are only used to UIs. Concourse needs someone which is capable of using CLIs.
Pros of Concourse
- Real pipelines15
- Containerised builds10
- Flexible engine9
- Fast6
- Open source4
- No Snowflakes3
- Simple configuration management3
- You have to do everything2
- Fancy Visualization1
Pros of TeamCity
- Easy to configure60
- Reliable and high-quality37
- On premise31
- User friendly31
- Github integration31
- Great UI18
- Smart16
- Can run jobs in parallel12
- Free for open source12
- Crossplatform8
- Chain dependencies4
- REST API4
- Great support by jetbrains4
- Fully-functional out of the box4
- Projects hierarchy4
- 100+ plugins3
- Free for small teams3
- Per-project permissions3
- Personal notifications3
- Build templates3
- Ide plugins2
- GitLab integration2
- Upload build artifacts2
- Artifact dependencies2
- Smart build failure analysis and tracking2
- Build progress messages promoting from running process2
- Built-in artifacts repository1
- Powerful build chains / pipelines1
- TeamCity Professional is FREE1
- Repository-stored, full settings dsl with ide support1
- Official reliable support0
- Hosted internally0
- High-Availability0
Sign up to add or upvote prosMake informed product decisions
Cons of Concourse
- Fail forward instead of rollback pattern2
Cons of TeamCity
- User friendly2
- Proprietary1
- High costs for more than three build agents1
- User-friendly1