# Costs and Usage

> One page per connected provider, with spend so far this month, spend over time, and a breakdown you can group by service, account, tag or virtual tag.

Source: https://docs.levelfour.ai/cost-and-usage


**Costs and Usage** in the dashboard sidebar lists every provider you have connected. Each one opens its own page, from the top down: a row of totals, a chart of spend over time, a cost breakdown table, and, where LevelFour keeps an inventory, the resources behind the cost.

A provider shows here once it is connected. [Connect Providers](/connectors) covers each one.

## The totals

The strip at the top shows the provider's figures at a glance:

| Figure                     | What it is                                   |
| -------------------------- | -------------------------------------------- |
| **Total Spend**            | Month to date for this provider              |
| **Forecast · EoM**         | Where the month is heading                   |
| **Savings Recommendation** | The open savings on this provider            |
| **Savings Audit**          | The savings captured on this provider so far |

Google Cloud shows **Gross cost**, **Credits** and **Net cost** instead, all month to date, so you can see how much your credits cover.

## Spend over time

**Spend over time** charts daily cost. Switch between **Daily** and **Monthly** bars, pick a period with the date control, and pick what the bars are split by. On AWS and Google Cloud you can also filter the chart to one tag value.

## Cost breakdown

**Cost Breakdown** is a table of the same spend, with the period total in its heading. Group it by:

| Group             | Groups by                               |
| ----------------- | --------------------------------------- |
| **Service**       | The provider's service                  |
| **Account**       | The account the cost landed in          |
| **Region**        | Where the resource runs                 |
| **Tag**           | A provider tag you pick                 |
| **Virtual Tag**   | A [virtual tag](/virtual-tags) you pick |
| **Resource**      | The individual resource                 |
| **Usage Type**    | The provider's usage type               |
| **Cost Category** | Your AWS cost categories                |
| **Purchase Type** | How the capacity was bought             |
| **Instance Type** | The instance size                       |

Grouped by a virtual tag, cost that no rule claims appears as its own **Unallocated** row, so the rows still add up to the bill.

### Google Cloud

Google Cloud names these the way its console does: **Project**, **Label**, **SKU**, **Pricing Model** and **Machine Type**. Cost categories do not exist on Google Cloud. The chart can also split by **Folder**, **Credit Type** and **Charge Type**.

The Google Cloud page adds **Google Cloud insights**: credits, commitments, labels, usage and inventory. A toggle in its header switches its figures between **After credits**, the default, and **Before credits**. [Boards](/boards#google-cloud-credits) explains the two figures.

## Resources

For providers where LevelFour keeps an inventory, such as DigitalOcean, a **Resources** table lists what runs in the account: name, type, region, size, project, tags and status. Search by name or ID, filter by type, region, project or tag, and switch between **Active** and **Removed** resources.

| Column                  | What it is                                                                 |
| ----------------------- | -------------------------------------------------------------------------- |
| **List price / mo**     | An estimate from the list price of that size, before discounts and credits |
| **Invoiced MTD**        | Invoice line items for the resource this month, before tax and credits     |
| **Invoiced last month** | The same for last month                                                    |

Charges that belong to no single resource, such as bandwidth, are totalled under the table.

## Next

* [Boards](/boards) put the same numbers side by side across providers
* [Virtual tags](/virtual-tags) create the keys the **Virtual Tag** grouping reads
* [Costs](/resources/costs) is the same data through the API