Armory
Winter 2017AcquiredContinuous Deployment at any scale, for all developers.
Pressure-test this opportunity
Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.
Continuous Deployment at any scale, for all developers.
Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.
If you only have a few minutes to spare, here’s what investors, operators, and founders should know about Armory (W17).
Armory commercialized Spinnaker, the open-source continuous-delivery system created at Netflix and Google. It gave large companies a supported way to coordinate releases across clouds, apply security and approval policies, expose new versions gradually, measure their health, and reverse a bad deployment. The company raised more than $82 million and served customers including JPMorgan Chase, Autodesk, Informatica, Patreon, LaunchDarkly, and HelloSign.[1]
The venture outcome was poor. Harness acquired Armory's assets for about $7 million in cash in January 2024. Harness hired many employees and kept supporting existing installations, but its chief executive described the transaction as an asset deal. Armory had raised almost twelve times the reported purchase price.[2]
Armory's core insight was sound: software deployment is a separate operational problem from compiling and testing code. Its challenge was turning one stage of the development lifecycle into a large independent company. Spinnaker was powerful but expensive to operate. Simpler open-source tools improved. Integrated DevOps platforms expanded into deployment. Armory introduced a new hosted product, but only reached public early access in 2022 after discussing a SaaS version in 2020. When venture funding tightened, a point solution with heavy enterprise demands had limited room to maneuver.
Daniel R. Odio, Isaac Mosquera, and Ben Mappen had worked together before founding Armory in a Belmont, California, garage in late 2016.[3] At their previous company, they had increased deployment frequency by more than 300 times. They assumed other companies would buy faster delivery.
Mappen pushed the founders to test that belief before building. The team conducted more than 100 customer interviews, often lasting 30 to 60 minutes, and assembled hundreds of pages of notes. Odio wrote, “We didn't write a single line of code until we'd completed 100 customer conversations.”[4]
Those interviews changed the product's emphasis. Leaders at large companies did not first ask to deploy more often. They wanted releases to stop being frightening. Some still scheduled downtime on Friday nights, gathered a team around the release, and spent the weekend repairing failures. “What they are really looking for isn't velocity, it's safety,” Odio concluded.[4]
Spinnaker supplied the technical base for that safety. Netflix had open-sourced it in 2015 after building it to manage thousands of microservices and thousands of daily deployments. Armory packaged it for enterprises and contributed upstream. Mosquera explained why deployment mattered as architectures split into smaller services: “If the overhead of deployments is high, breaking up a monolith into smaller components only increases overall complexity.”[5]
The founders entered Y Combinator's Winter 2017 batch and positioned Armory as the company that would make Spinnaker usable, governable, and supportable inside large organizations.[6]
Armory's first main product was an enterprise distribution of Spinnaker installed in a customer's Kubernetes cluster. Spinnaker represented deployment as pipelines and could target AWS, Google Cloud, Kubernetes, and other environments. It supported blue-green releases, staged traffic shifts, and canary analysis, in which a small new deployment was compared with a baseline before wider release.[11]
Read the complete post-mortem, the rebuild playbook, and the exact reasons Armory is still worth studying now.