> For the complete documentation index, see [llms.txt](https://docs.multitudes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.multitudes.com/metrics-and-definitions/process-metrics/flow-of-work/deploy-time.md).

# Deploy Time

{% hint style="warning" %}
Note: this metric is **only shown at a team level**, not an individual level.
{% endhint %}

<img src="https://cdn.prod.website-files.com/610c8a14b4df1ae46b1a13a3/64927f855674f58481962303_Deployment%20Time%20(2).png" alt="Deploy Time line graph" width="836">

***‍*****What it is:** This metric shows how long code takes to get deployed once a PR has been merged.

**Why it matters:** `Deploy Time` measures how fast new features, bug fixes, and hot-fixes can reach end-users. A lengthy build or deployment process can delay crucial updates, hinder customer satisfaction, and even impact the overall competitiveness of a product or service. By minimizing `Deploy Time`, organizations can ensure a faster time-to-market.

A long `Deploy Time` also has a direct impact on developer productivity and well-being. As this can introduce frustration and inefficiency, leading to a decline in developer morale and motivation. When developers have to wait for long periods to see their code build, it can disrupt their workflow and hinder their ability to iterate and make further improvements.

**How we calculate it:**  The number of hours from when a PR is merged to when an [attempt to deploy it to production](/metrics-and-definitions/deployment-metrics.md) succeeds.

**A few notes:**

* If you have GitHub Actions set up, see [here](/integrations/github-actions.md) for info on how the way you use and configure this integration will appear in your data
* If you’re using our [Deployments API](/integrations/deployments-api.md), the commitSha is what we’ll use to match deployments to PRs