The archive · Work & Ways of Doing · Technical decision · 2009–2011
Etsy's Deployinator shrinks a web push from an hour-long ceremony to one button
Etsy builds Deployinator, a one-button deploy tool: a web push that took a crew and over an hour now takes one person and two minutes.
Etsy
What it had to solve
Around 2009–2010 Etsy shipped code often, but every web push was an event: three developers, one operations engineer, everyone else on standby, and over an hour when things went smoothly. The engineering team moved to a continuous deployment system built around a tool they made themselves.
How it works
At Etsy in 2010, shipping a web push was a coordinated production: three developers, an operations engineer, everyone else on standby, and over an hour when things went smoothly. Engineer Erik Kastner described the team's move to a continuous deployment system based on a tool they had built themselves.
That tool, Deployinator, grouped deployments into stacks and gave each environment — staging, QA, production — its own button. Instead of choreographing a release across many people, an engineer pushed from the web UI and the deploy ran and was logged, shrinking the whole ceremony to one person and under two minutes.
Kastner's post framed the goal as the smallest possible number of steps, people and ceremony required to get new code running — what he called the quantum of deployment. Etsy open-sourced Deployinator as a Ruby framework, and the repository's README noted the company had been using it since late 2009 or early 2010.
Why it lands
- It attacked the bottleneck of deployment — coordination — instead of just speeding up individual steps.
- A button per environment made the release process visible, repeatable and operable by one person.
- Logging and announcing each push gave engineers feedback and accountability without a gatekeeper.
- Open-sourcing the tool let the pattern outlive Etsy's own codebase and enter general DevOps practice.
What it did
Etsy reported that a typical web push went from three developers, one operations engineer, everyone else on standby and over an hour down to one person and under two minutes. The tool stayed in Etsy's workflow for years, and open-sourcing it made the pattern available to other engineering teams.
What you can take
Cut the ceremony, not the care: when a release needs a crowd and an hour, turn the bottleneck into a tool one engineer can drive, and deployment becomes a routine instead of an event.
Since then
Deployinator remained part of Etsy's workflow for years, and Etsy's engineering blog kept writing about deploy tooling and a culture where engineers ship their own code. Etsy released Deployinator as open source on GitHub, where the repository stayed in read-only archive mode after the owner archived it in December 2019. The 'deployinator' idea — a simple button that removes ceremony from shipping — kept appearing in continuous-delivery discussions.
Sources
spotted an error? The archive wants to know.
Your turn
You just read one. Describe the brief you are staring at, and see who has been given the same problem.
Free account · 3 free questions · no card