[devonkim]

I haven't gotten very deep into the guts of Spinnaker, but how are you expecting to handle the enormous number of organizations that prohibit developers from having production access and require someone in operations to perform a deployment? Even if you do all the necessary steps of API versioning, feature flags, blue / green deploys and such, most of these start to break down fast in velocity when there's a requirement for removing control away from developers to those that have less familiarity with the impact of changes. I absolutely agree something needs to address low-performing software organizations because oftentimes they're among the highest-impact organizations out there such as the Fortune 100 and public sector (as opposed to some SaaS company with a whole 1000 customers) but I haven't been able to crack the problem of many different reasons for dysfunctions leading to such low rates of deployments (it's invariably a Wicked Problem due to being almost entirely social in roots rather than technical I've observed so far).

[imosquera]

We believe that engineers should have access to deploy, manage and ultimately own their own deployments. This fundamental change is more commonly known as DevOps. In our interviews with over 100 enterprise companies, before we even incorporated the company, we observed a strong desire for teams to move in this direction. While we are aware there are many laggards, we’re making a bet, with Armory, that companies must move in this direction or die.

That said, it’s an immense challenge working with the F100, which for some, don’t want to move in this direction yet. We’ve chosen not to focus those laggard companies. Even within our current focus, we’ve found that we actually can’t hire fast enough to support new customers who want to truly enable their deployment teams. And yes, it’s very much a “Wicked Problem” to solve but we’re hoping that with Spinnaker and market pressure it helps loosen those roots.