Hey folks, I'm Ben from Armory.io (YC W17). We just launched Continuous Deployment-as-a-Service (CDaaS) to make it easy for developers to deploy their apps safely to the cloud. We’d greatly appreciate (raw, candid) feedback from the HN community if this solution improves the speed at which you deploy to production. We have a free-forever tier that gives you up to 25 Application Targets[1] (our unit of scale for pricing).<p>Try it here: <a href="https://www.armory.io/products/continuous-deployment-as-a-service/" rel="nofollow">https://www.armory.io/products/continuous-deployment-as-a-se...</a><p><i>Our Story</i><p>We’ve been helping large companies with CD since 2016 by selling them our distribution of Spinnaker (spinnaker.io, originally Netflix OSS). We’ve learned three big lessons:<p>One reason developers are drawn to Spinnaker is because it provides an imperative approach to orchestrating deployment workflows
Operating Spinnaker “on-prem” (usually in the customer’s AWS account) requires significant effort
Doing true continuous deployment to production requires the use of advanced strategies to mitigate risk<p>These learnings inspired us to build CDaaS and make it easy for developers to employ well-understood deployment strategies like blue/green and canary deployments without having to write custom code. With CDaaS, our aim is to deliver many of the features developers rely on from Spinnaker, but in a declarative manner that supports the GitOps approach they know and use extensively.<p>CDaaS currently supports deployments to Kubernetes but we’re adding additional cloud providers quickly (AWS, GCP, Azure, etc)<p><i>How It Works</i><p>Connect any number of Kubernetes clusters to our central control plane by installing a lightweight network agent. Once connected, you can configure your application deployment logic in a declarative YAML file that can be checked in alongside your app’s source code. Deployments can be invoked from our CLI which allow you to use your existing CI platform (Jenkins, Github Actions, CircleCI, etc) to trigger a deployment. Monitor deployments (and take additional action like rolling back, if needed) from our UI.<p><i>More Information</i><p>CD-as-a-Service product docs: <a href="https://docs.armory.io/cd-as-a-service/" rel="nofollow">https://docs.armory.io/cd-as-a-service/</a><p>Short Demo (8 min): <a href="https://www.youtube.com/watch?v=r29UCKMXEi4" rel="nofollow">https://www.youtube.com/watch?v=r29UCKMXEi4</a>
Great to see Armory team manifest their deep expertise in software deployments through a simple SaaS offering that reduces a lot of complexity and adds value to the existing SDLC workflows instead of trying to replace them. Excited to see future multi-cloud and functions support, which will be game changing as most companies nowadays are multi-cloud and deploy more than just containers.
This could be cool. I've worked at places in the past that have essentially tried to roll their own tool like this, which I think was pretty resource-intensive. I never worked on those directly, so I don't know if this would fully meet the requirements those tools did.
Looks pretty sweet! Love the declarative model. Imperative pipelines are super flexible but also a pain to maintain and easy to get wrong. The key features like canary and blue/green all that most deployments actually need.