> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/internal-developer-portal/use-idp/environment-management/cost-estimation.md).

# Cost Estimation for Environments

Harness IDP displays infrastructure cost estimation data from IACM workspaces directly in your environments. When an IACM workspace has cost estimation enabled, Infracost runs during the Terraform plan stage and computes estimated monthly costs for priceable cloud resources. This data is exposed at the individual resource level and aggregated at the environment level.

***

### Before you begin <a href="#before-you-begin" id="before-you-begin"></a>

If you wish for cost estimation data to appear in your environments, ensure the following:

* The IACM workspace template used by the environment has `cost_estimation.enabled: true`. Go to [Workspace Templates](/infrastructure-as-code-management/platform/workspaces/workspace-templates.md) to know the process of template configuration.
* The Terraform module contains priceable cloud resources (compute instances, databases, storage, and so on).

{% hint style="info" %}
Kubernetes and Helm resources are not supported by Infracost and do not produce cost data.
{% endhint %}

***

### How it works <a href="#how-it-works" id="how-it-works"></a>

Cost estimation runs during the **Terraform plan** stage, not the apply stage. Infracost evaluates the plan output and computes estimated monthly costs for supported cloud resources. No additional configuration is needed on the environment or blueprint beyond enabling cost estimation on the IACM workspace template.

Cost data is supported for the following cloud providers:

* Amazon Web Services (AWS)
* Google Cloud Platform (GCP)
* Microsoft Azure

***

### View cost data <a href="#view-cost-data" id="view-cost-data"></a>

#### Environment list <a href="#environment-list" id="environment-list"></a>

The environments list includes an **EST.COST/MO** column. Environments with cost estimation enabled display an aggregated value such as `$~7/mo (USD)`. Environments without cost estimation enabled display **Cost not enabled**.

<figure><img src="/files/vatKqekH1UJkDhVudqFQ" alt=""><figcaption></figcaption></figure>

The same **EST.COST/MO** column appears in the **Environments** tab on the blueprint overview page, showing cost data across all environments created from that blueprint.

<figure><img src="/files/XiDG4ZHq6R41yGXRWIp7" alt=""><figcaption></figcaption></figure>

#### Environment detail: Cost tab <a href="#environment-detail-cost-tab" id="environment-detail-cost-tab"></a>

On the environment detail page, open the **Cost** tab to view a per-resource breakdown.

<figure><img src="/files/tWNx6IpyPphydnzW4efi" alt=""><figcaption></figcaption></figure>

The table shows the following columns:

| Column            | Description                                                                    |
| ----------------- | ------------------------------------------------------------------------------ |
| **Resource**      | The Terraform resource identifier (for example, `google_compute_instance.vm`). |
| **Resource Type** | The resource type (for example, `google_compute_instance`).                    |
| **Est. Cost/Mo**  | Estimated monthly cost in USD.                                                 |

{% hint style="info" %}
The Cost tab also supports pagination for environments with a large number of resources.
{% endhint %}

When a cost change is detected between plan runs, a diff appears next to the estimated cost, showing the absolute change and percentage (for example, `+$114 (+100%)` for increases or `-$1 (-14%)` for decreases).

<figure><img src="/files/TIf6yCjMFbVKjnPC8bHH" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**WHEN COST DATA IS NOT SHOWN**

Cost data is absent in the following cases:

* The IACM workspace template has `cost_estimation.enabled: false`.
* The workspace uses only Kubernetes or Helm resources, which Infracost does not support.
* No Terraform plan has been executed yet for the environment.
* The environment instance uses a [CD backend rather than IACM](/internal-developer-portal/use-idp/environment-management/blueprints/env-blueprint-yaml.md#backend-types).
  {% endhint %}