---
title: "Why continuous deployment just keeps on giving - The Intercom Blog"
description: "Intercom has practiced continuous deployment since its early days, deploying code automatically after each merge to master. The pipeline uses GitHub, Codeship for the test suite, and an internal tool called Muster to push code to production EC2 instances, typically in under ten minutes. The company now deploys over 80 times a day, aiming for 100 by end of 2015, and a dashboard tracks this history over three years. This rapid feedback loop allows engineers to iterate features through internal, beta, and public stages, learning how people use the feature and how code performs in production. The automated system helps new engineers ship code on their first day and a feature in their first week by removing deployment barriers, and they demo their work at Friday sessions. Additionally, a fast and reliable deployment process discourages engineers from bypassing it during critical bug fixes, reducing risky behavior."
---

# Why continuous deployment just keeps on giving - The Intercom Blog

[Intercom](https://yomu.fyi/company/intercom) · Oct 13, 2026

**Type:** Explainer

## Summary

Intercom has practiced continuous deployment since its early days, deploying code automatically after each merge to master. The pipeline uses GitHub, Codeship for the test suite, and an internal tool called Muster to push code to production EC2 instances, typically in under ten minutes. The company now deploys over 80 times a day, aiming for 100 by end of 2015, and a dashboard tracks this history over three years. This rapid feedback loop allows engineers to iterate features through internal, beta, and public stages, learning how people use the feature and how code performs in production. The automated system helps new engineers ship code on their first day and a feature in their first week by removing deployment barriers, and they demo their work at Friday sessions. Additionally, a fast and reliable deployment process discourages engineers from bypassing it during critical bug fixes, reducing risky behavior.

## Context

Intercom’s engineering team describes their continuous deployment system and its benefits for product development, team onboarding, and operational discipline.

## Approach / What changed

The deployment pipeline: after code review on GitHub, engineers merge to master. GitHub sends a webhook to Codeship to run the test suite, and another webhook to Muster, an internal tool that prepares the code for release. Once tests pass, Codeship notifies Muster, and the code is pushed to production EC2 instances. The entire process takes less than 10 minutes.

## Takeaways

- Continuous deployment enables rapid iteration through feature flags and staged rollouts (internal, beta, public), allowing dozens of deployments per feature before full launch.
- New engineers can ship code on their first day and a feature in their first week because the automated deployment system removes the need to learn deployment processes.
- A fast and reliable deployment system (under 10 minutes) discourages engineers from bypassing it during critical bug fixes, reducing risky production hacks.

## FAQ

### How does Intercom's deployment pipeline work?

After code review on GitHub, engineers merge to master. GitHub sends webhooks to Codeship for testing and to Muster for release preparation. Once tests pass, Muster pushes the code to production EC2 instances, typically in under 10 minutes.

### What benefits does continuous deployment provide for new engineers?

New engineers can deploy changes immediately without learning deployment rules, enabling them to ship code on their first day and a feature in their first week, which helps them feel productive quickly.

### How does continuous deployment prevent bad behavior during incidents?

A fast and reliable deployment system makes it easier to use than hacking in production, so engineers are not tempted to bypass the process when fixing critical bugs.

**Tags:** [Automation](https://yomu.fyi/topic/automation), [Continuous Deployment](https://yomu.fyi/topic/continuous-deployment), [Developer Experience](https://yomu.fyi/topic/developer-experience), [Productivity](https://yomu.fyi/topic/productivity)

- Source: [Intercom](https://www.intercom.com/blog/why-continuous-deployment-just-keeps-on-giving)
- Source URL: https://www.intercom.com/blog/why-continuous-deployment-just-keeps-on-giving
- Ingested by Yomu: 2026-10-13T18:00:21.132Z

[Read original post](https://www.intercom.com/blog/why-continuous-deployment-just-keeps-on-giving)