Capistrano maintainer here, I gave a more comprehensive answer in this thread [1], I hope that answers some of your questions.<p>Specifically to address your point about having &quot;nothing to do with the tool for the vast majority&quot; there may be some sense to that. We first built a pure, pure literal web front end for Capistrano, it turns out something that limited is not that useful, however when you boil the problem down in to:<p>- Management of secrets, variables, keys, etc<p>- Tasks that can be combined with sets environment specific config and re-used<p>It turns out to be fairly universal. <a href="https:&#x2F;&#x2F;xkcd.com&#x2F;927&#x2F;" rel="nofollow">https:&#x2F;&#x2F;xkcd.com&#x2F;927&#x2F;</a> springs to mind, if we&#x27;d built another custom web front end for another specific tool it would be nearly useless. As it is we&#x27;ve got customers who have cut their monthly spend on testing&#x2F;monitoring services from 800$ to $160 and have a better, more consistent experience.<p>It&#x27;s all relative, frankly my company invested a lot to build this and I personally truly believe it in, and after 18 months  intentional slow-burn to make sure it worked well for the people who did use it, it&#x27;s time to test the water and see if we can bring the product to profitability.<p>If we can&#x27;t I&#x27;m almost certainly going to have to cease working on FOSS due to business and family commitments, given my love for FOSS that&#x27;s something I&#x27;d rather not do!<p>[1]: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=11596602" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=11596602</a>