# Compare costs with other clouds

Price the instance hours, database node hours and storage of a window at other clouds' public list prices, next to what you paid.

## Prerequisites

- Permission for `billing:GetCostAndUsage`.
- `iam:UpdateOrganization` only to filter or group by where resources run (`provider`). Without
  it, such a query is refused with `403` "Grouping or filtering by where resources run needs
  iam:UpdateOrganization (the org’s Infrastructure settings)".

## Compare a window

**Console**
1. Open **Cost explorer** and choose the window and filters (see [Explore costs](explore-costs.md)).

The section **Compared with other clouds** prices the same usage at each reference provider: the
cost of the **Same usage**, how it **Compared with us**, what was **Matched**, and where the
**Prices from** come from.

**CLI**
```sh
dcloud billing costs compare --start 2026-10-01 --end 2026-10-31
```

**API**
```http
POST /billing/api/cost-explorer/compare
{ "start": "2026-10-01", "end": "2026-10-31" }
```

## What is compared

- Instance hours, each matched to the provider's cheapest machine of the same CPU class and
  architecture with at least the vCPUs and memory (named in `matches`).
- Managed PostgreSQL node hours, matched to the provider's cheapest managed PostgreSQL server with at
  least the vCPUs and memory; where a provider has none, the node counts at our price and is named
  in `partial`.
- Block and object storage, by GB-month.

Everything else is `notComparedEur`, and usage that is metered but not charged yet is left out
(`notChargedEur`). No free tiers, commitments or discounts are applied. A provider without a
verified price list says so in `missing`, and its `totalEur` is null.

Filters here match ids only: a value written as the name the console shows (`project:Shop`) is not
looked up. `granularity`, `groupBy` and `maxGroups` are accepted and do not change the answer.

## Related

- [Explore costs](explore-costs.md)
- `billing.costs.compare` · `dcloud billing costs compare`
