Concourse vs Gogs: 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, Gogs is detailed as "A self-hosted Git service written in Go". The goal of this project is to make the easiest, fastest and most painless way to set up a self-hosted Git service. With Go, this can be done in independent binary distribution across ALL platforms that Go supports, including Linux, Mac OS X, and Windows.
Concourse can be classified as a tool in the "Continuous Integration" category, while Gogs is grouped under "Code Collaboration & Version Control".
"Real pipelines" is the top reason why over 8 developers like Concourse, while over 32 developers mention "Self-hosted github like service" as the leading cause for choosing Gogs.
Concourse and Gogs are both open source tools. It seems that Gogs with 30.8K GitHub stars and 3.56K forks on GitHub has more adoption than Concourse with 3.99K GitHub stars and 482 GitHub forks.
DigitalOcean, Starbucks, and HelloFresh are some of the popular companies that use Concourse, whereas Gogs is used by Write.as, OSInet, and GameDuell. Concourse has a broader approval, being mentioned in 18 company stacks & 17 developers stacks; compared to Gogs, which is listed in 9 company stacks and 10 developer stacks.