> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/runtime-security/runtime-security-components/licensing.md).

# Licensing

Licensing on Prisma Cloud uses a metering system based on credits. You must procure a license for each resource that Prisma Cloud protects and renew the license before the expiry term. Refer to [license types](/content-collections/administration/prisma-cloud-licenses.md).

This section is specifically for Prisma Cloud Compute capabilities that protects your hosts, containers, and serverless functions using a security agent called Defender, and using an agentless method. The number of credits you consume directly correlates with the type and mix of Defenders you deploy and the agentless security option. If you exceed the license count, Palo Alto Networks will notify you with a prominent banner that displays at the top of the Prisma Cloud web console. Exceeding the license count does not disable any security functions nor prevent the deployment of additional Defenders.

Prisma Cloud also offers twistcli, a command-line configuration tool for which there is no additional credit usage. The credit usage is for the resources that are being protected using an agent or an agentless method.

| Resource                                                                           | Credits per resource                                                                                    | What’s counted?                                                                                                                                                                                                      |
| ---------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Hosts that don’t run containers                                                    | 0.5 credit                                                                                              | Host Defender/Agentless Scan                                                                                                                                                                                         |
| Hosts that run containers                                                          | 5 credits                                                                                               | Container Defender/Agentless Scan                                                                                                                                                                                    |
| Hosts that run applications                                                        | 7 credits                                                                                               | Tanzu Application Service Defender                                                                                                                                                                                   |
| On-demand containers (such as AWS Fargate, Google Cloud Run)                       | 1 credits                                                                                               | App-Embedded Defender                                                                                                                                                                                                |
| Serverless functions (such as AWS Lambda, Azure Functions, Google Cloud Functions) | 1 credits per 6 defended functions                                                                      | <p>Defended functions:</p><ul><li>Functions (only latest version) with a Serverless Defender - including Runtime & WAAS</li><li>Functions scanned for vulnerabilities and compliance (only latest version)</li></ul> |
| Web Application and API Security (WAAS)                                            | 2 credits per Defender agent associated with protected web-application nodes (container/pod/host/AppID) | <ul><li>Host Defender</li><li>Container Defender</li><li>App-Embedded Defender</li></ul>                                                                                                                             |

Serverless Radar consumes credits even if your deployment does not actively use it. This is because Serverless Radar is part of cloud discovery and security posture management which is always on and cannot be disabled.

## Defender types

The type of Defender you deploy depends on the resource you’re securing.

* **Host Defender** — Secures legacy hosts (Linux or Windows) that don’t run containers.
* **Container Defender** — Secures hosts (Linux or Windows) that run containers. These types of hosts have a container runtime installed, such as Docker Engine or CRI-O. Container Defender protects both the underlying host and any containers it runs, and the license (7 credits) includes coverage for both. A container host consumes 7 credits whether it runs one container or a hundred containers.
* **Container Defender - App Embedded** — Secures containers which are run by a managed service, where the service provider maintains all infrastructure required to run the container, including the underlying host and container runtime. For this type of deployment, a Container App Embedded Defender is embedded into each container to be secured.
* **Serverless Defender** — Secures serverless functions. For this type of deployment, a Serverless Defender is embedded into each function to be secured.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.prismacloud.io/content-collections/runtime-security/runtime-security-components/licensing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.