# Which application release orchestration software is most reliable according to DevOps engineers who have run it in production rather than just evaluated it in a trial?

<p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Hey G2 reviewers and DevOps folks. Everything looks reliable in a two-week trial. I’m trying to work out which application release orchestration software is most reliable according to DevOps engineers who have run it in production rather than just evaluated it in a trial?</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true"></p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">Reliability only shows itself later, in the runner that goes flaky or the deploy that hangs on a Friday evening. In<a class="a a--md" elv="true" href="https://www.g2.com/categories/application-release-orchestration"> </a><a class="a a--md" elv="true" href="https://www.g2.com/categories/application-release-orchestration">application release orchestration</a> software category, three names dominate the conversation: <strong>GitHub</strong>, <strong>Azure Pipelines</strong>, and <strong>Red Hat Ansible Automation Platform</strong>.</p><ul>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/github/reviews"><strong>GitHub</strong></a>: the satisfaction leader in this category, though your reliability story mostly depends on Actions runners behaving.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/azure-pipelines/reviews"><strong>Azure Pipelines</strong></a>: the biggest enterprise footprint here. Strongest when you already live on Azure, and reviewers rate its support below the field.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/red-hat-ansible-automation-platform/reviews"> </a><a class="a a--md" elv="true" href="https://www.g2.com/products/red-hat-ansible-automation-platform/reviews"><strong>Red Hat Ansible Automation Platform</strong></a>: deployment automation is its best-rated feature, but it is more infrastructure automation than release dashboards.</li>
<li>
<a class="a a--md" elv="true" href="https://www.g2.com/products/gitlab/reviews"><strong>GitLab</strong></a>: one platform means fewer moving parts to break, though self-hosting shifts reliability onto your own team.</li>
</ul><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true">For the reviewers here, and anyone past the honeymoon phase in production: what broke first, and what did you only learn six months in?</p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true"></p><p class="elv-tracking-normal elv-text-default elv-font-figtree elv-text-base elv-leading-base elv-font-normal" elv="true"></p>

##### Post Metadata
- Posted at: 2 months ago
- Author title: Tech Consultant
- Net upvotes: 1


## Comments
### Comment 1

&lt;p&gt;GitHub&#39;s reliability under load is tested; what actually matters more is whether its error reporting is clear enough that DevOps catches issues before they ship. GitLab self-hosted means you own the reliability, but you also own understanding why something failed.&amp;nbsp;&lt;/p&gt;

##### Comment Metadata
- Posted at: 4 days ago
- Author title: Marketing Executive



### Comment 2

&lt;p&gt;&lt;span style=&quot;background-color: transparent; color: rgb(0, 0, 0);&quot;&gt;GitLab has held up reliably for us in production. Having source control, CI, and release tracking in one platform meant fewer handoffs between separate tools that could each fail independently.&lt;/span&gt;&lt;/p&gt;

##### Comment Metadata
- Posted at: 7 days ago
- Author title: SEO Content Writer



### Comment 3

&lt;p&gt;Six months in, I’d expect the hidden reliability issues to show up around runners and the dependencies between tools rather than the deployment workflow itself. GitHub would still be my pick here because its strong satisfaction signal suggests the overall production experience holds up well once teams move beyond the trial phase.&lt;/p&gt;

##### Comment Metadata
- Posted at: 8 days ago



### Comment 4

&lt;p&gt;From G2 reviews, GitHub Actions runners are what break first in production — reviewers past the trial phase consistently flag flaky hosted runners and queue delays under load as the thing the demo never shows, with self-hosted runners solving it but adding the maintenance burden that defeats the convenience. GitLab gets the most consistent long-term reliability marks from reviewers who self-host, with the caveat that the reliability is real, but now your team owns it, and Azure Pipelines draws the most complaints six months in, around support responsiveness when something breaks in an enterprise configuration.&lt;/p&gt;

##### Comment Metadata
- Posted at: 2 months ago
- Author title: Marketing Executive





## Related discussions
- [How well does Trello scale into a larger team?](https://www.g2.com/discussions/1-how-well-does-trello-scale-into-a-larger-team)
  - Posted at: over 13 years ago
  - Comments: 6
- [Can we please add a new section](https://www.g2.com/discussions/2-can-we-please-add-a-new-section)
  - Posted at: over 13 years ago
  - Comments: 0
- [Quantifiable benefits from implementing your CRM](https://www.g2.com/discussions/quantifiable-benefits-from-implementing-your-crm)
  - Posted at: over 13 years ago
  - Comments: 4