# GitHub Actions vs Concourse CI: Pipelines Comparados

> GitHub Actions vs Concourse CI comparados em preço, hospedagem, configuração e manutenção. Concourse é um CI self-hosted baseado em recursos versus o Actions gerenciado.

Source: https://latchkey.dev/pt/learn/tool-comparisons/github-actions-vs-concourse  
Updated: 2026-06-26

Concourse modela tudo como pipelines, recursos e jobs com reprodutibilidade rigorosa; GitHub Actions é um CI integrado e gerenciado.

Concourse CI é um CI self-hosted baseado em containers, com um modelo distinto de recursos/jobs e foco em reprodutibilidade. GitHub Actions é o CI integrado ao GitHub. Aqui está a comparação.

## Comparison

|  | GitHub Actions | Concourse CI |
| --- | --- | --- |
| Config | .github/workflows/*.yml | pipeline.yml (resources + jobs) |
| Modelo de hospedagem | GitHub-hosted ou self-hosted | Self-hosted (web + workers) |
| Preço | Por minuto (hosted) | Software gratuito + sua infra |
| Ecossistema | Grande Actions Marketplace | Tipos de recursos |
| Alavancas de velocidade | Cache, runners maiores/gerenciados | Dimensionamento de workers, jobs paralelos |
| Manutenção | Baixa (gerenciado) | Você roda web + workers |

## Preço e manutenção

Concourse é open-source e gratuito para rodar, mas você opera o nó web e os workers e mantém a disciplina de reprodutibilidade. GitHub Actions remove isso e cobra por minuto.

## Configuração e ecossistema

Concourse impõe pipelines limpos e reprodutíveis através do seu modelo de recursos - poderoso, mas com uma curva de aprendizado mais íngreme. O Actions é mais acessível e tem um marketplace muito maior.

## Velocidade e runners

Para um CI gerenciado sem rodar workers do Concourse, o GitHub Actions com runners gerenciados (por exemplo, Latchkey) oferece computação barata (~70% abaixo do GitHub-hosted), warm pools e retentativas com autocorreção.

## Migrating between CI platforms: what actually costs time

- Pipeline syntax is the easy part and the part every comparison focuses on. Budget for it, then expect it to be the smallest line item.
- Secrets, OIDC trust relationships, and deploy credentials have to be recreated and re-approved, usually by a different team.
- Caching semantics differ enough that a naive port produces a pipeline that is correct and much slower.
- Required status checks and branch protection reference check names. Renaming them mid-migration blocks merges until the rules are updated.
- Run both in parallel on the same commits until the new one has been green for a full sprint. Cutting over on a green first run is how migrations get rolled back.

## O veredito

Escolha Concourse para pipelines self-hosted rigorosos e reprodutíveis com uma equipe de plataforma; escolha GitHub Actions para um CI gerenciado e acessível. Runners gerenciados mantêm o Actions barato e com baixa operação.

## FAQ

### GitHub Actions vs Concourse CI: Pipelines Compared?

Concourse CI is a self-hosted, container-based CI with a distinctive resources/jobs model and a focus on reproducibility. GitHub Actions is integrated CI for GitHub. Here is the comparison.

### Pricing and maintenance?

Concourse is open-source and free to run, but you operate the web node and workers and maintain reproducibility discipline. GitHub Actions removes that and bills per minute.

### Config and ecosystem?

Concourse enforces clean, reproducible pipelines via its resource model - powerful but a steeper learning curve. Actions is more approachable with a much larger marketplace.

### Speed and runners?

For managed CI without running Concourse workers, GitHub Actions with managed runners (e.g. Latchkey) gives cheap compute ($0.0025/min at 2 vCPU vs $0.006 GitHub-hosted), warm pools, and self-healing retries.

### Which should I choose?

Choose Concourse for strict, reproducible self-hosted pipelines with a platform team; choose GitHub Actions for approachable managed CI. Managed runners keep Actions cheap and low-ops.

---

Latchkey runs CI/CD that repairs its own failures. Agent entry points: https://latchkey.dev/agent.txt, https://latchkey.dev/openapi.json, https://latchkey.dev/llms.txt