> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/snyk-data-and-governance/how-does-snyk-count-assets.md).

# How Snyk counts assets

How Snyk counts billable assets managed through Snyk Essentials

## Billable assets <a href="#billable-assets" id="billable-assets"></a>

Managed Billable Assets are the resources, assets, and configuration files accessed through or managed by the customer in Snyk Essentials.

According to Snyk, the following are considered Managed Billable Assets against the customer's subscription allocation:

| Asset type                                                                                                                                                                                                                                                                             | Billable asset examples                  |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |
| <p><strong>Repository assets:</strong></p><p>Source Code Repository, where Snyk counts the total repositories.</p>                                                                                                                                                                     | github.com/snyk/hello-world              |
| <p><strong>Container image assets:</strong></p><p>Represent the built image that is found in a customer’s estate, where images are counted based on the globally unique identifiers, like image IDs and SHA, that may contain an application and all of its software dependencies.</p> | dockerhub.com/my-company/my-image:latest |

## Asset usage policy <a href="#asset-usage-policy" id="asset-usage-policy"></a>

Snyk may monitor customer billable asset volumes on a daily basis and actively review customer utilization on a rolling thirty (30) day period. If a customer’s billable asset usage exceeds the limit granted by the plan purchased by twenty percent (20%) on a rolling ninety (90) day period or by one-hundred percent (100%) for a period of thirty (30) days, Snyk may notify the customer to discuss the overage and, \[if action is required], provide an expansion invoice to increase the billable asset allocation. Except in unusual circumstances, Snyk will not invoice retroactively for Managed Billable Asset overages.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snyk.io/snyk-data-and-governance/how-does-snyk-count-assets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.