StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Continuous Integration
  4. Continuous Integration
  5. Concourse vs Spinnaker

Concourse vs Spinnaker

OverviewDecisionsComparisonAlternatives

Overview

Concourse
Concourse
Stacks254
Followers393
Votes54
GitHub Stars7.6K
Forks870
Spinnaker
Spinnaker
Stacks233
Followers358
Votes14
GitHub Stars9.6K
Forks1.2K

Concourse vs Spinnaker: What are the differences?

# Introduction

Concourse and Spinnaker are both popular continuous delivery tools used by software development teams to automate their build, test and deployment processes. While they serve a similar purpose, they have key differences that differentiate them in terms of functionality and use cases.

1. **Architecture**: Concourse follows a pipeline-based architecture, where tasks and resources are defined in a YAML file to create a linear workflow. On the other hand, Spinnaker uses a Kubernetes-style declarative API with stages and pipelines defined in a JSON format, offering more flexibility and scalability for complex deployment scenarios.

2. **Integration**: Concourse is heavily integrated with containerization platforms like Docker and Kubernetes, making it a preferred choice for teams working with containerized applications. In contrast, Spinnaker provides integrations with a wide range of cloud providers, offering support for multi-cloud deployments and hybrid environments with ease.

3. **Approval Process**: Concourse lacks built-in support for an approval process, which means that all stages in a pipeline run sequentially without human intervention. In contrast, Spinnaker offers an approval process where designated users can manually approve or reject each stage, providing greater control over deployment workflows.

4. **Rollback Mechanism**: Concourse does not have a native rollback mechanism, making it challenging to revert to previous versions in case of issues during deployment. On the other hand, Spinnaker provides a robust rollback mechanism that allows users to easily roll back to a previous, stable version in case of failures or bugs in the current deployment.

5. **Community Support**: While both Concourse and Spinnaker have active communities contributing to their development, Spinnaker has a larger user base and a more extensive support network, making it easier for users to find resources, documentation, and solutions to their deployment challenges.

In Summary, Concourse and Spinnaker have distinct architectural differences, with Concourse being more focused on pipelines and containerization, while Spinnaker offers a broader range of integrations and features for managing complex deployment workflows.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Advice on Concourse, Spinnaker

veera
veera

Jan 27, 2020

Needs advice

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 !

521k views521k
Comments

Detailed Comparison

Concourse
Concourse
Spinnaker
Spinnaker

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.

Created at Netflix, it has been battle-tested in production by hundreds of teams over millions of deployments. It combines a powerful and flexible pipeline management system with integrations to the major cloud providers.

Statistics
GitHub Stars
7.6K
GitHub Stars
9.6K
GitHub Forks
870
GitHub Forks
1.2K
Stacks
254
Stacks
233
Followers
393
Followers
358
Votes
54
Votes
14
Pros & Cons
Pros
  • 16
    Real pipelines
  • 10
    Containerised builds
  • 9
    Flexible engine
  • 6
    Fast
  • 4
    Open source
Cons
  • 2
    Fail forward instead of rollback pattern
Pros
  • 14
    Mature
Cons
  • 3
    No GitOps
  • 1
    Management overhead
  • 1
    Ease of use
  • 1
    Configuration time
Integrations
No integrations available
Stackdriver
Stackdriver
Packer
Packer
Prometheus
Prometheus
Chef
Chef
Jenkins
Jenkins
Docker
Docker
Puppet Labs
Puppet Labs
Amazon EC2
Amazon EC2
GitHub
GitHub
Google Kubernetes Engine
Google Kubernetes Engine

What are some alternatives to Concourse, Spinnaker?

Jenkins

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

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

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.

CircleCI

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.

Buddy

Buddy

Git platform for web and software developers with Docker-based tools for Continuous Integration and Deployment.

TeamCity

TeamCity

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.

Drone.io

Drone.io

Drone is a hosted continuous integration service. It enables you to conveniently set up projects to automatically build, test, and deploy as you make changes to your code. Drone integrates seamlessly with Github, Bitbucket and Google Code as well as third party services such as Heroku, Dotcloud, Google AppEngine and more.

wercker

wercker

Wercker is a CI/CD developer automation platform designed for Microservices & Container Architecture.

GoCD

GoCD

GoCD is an open source continuous delivery server created by ThoughtWorks. GoCD offers business a first-class build and deployment engine for complete control and visibility.

Shippable

Shippable

Shippable is a SaaS platform that lets you easily add Continuous Integration/Deployment to your Github and BitBucket repositories. It is lightweight, super simple to setup, and runs your builds and tests faster than any other service.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana