> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/licensing/licensing.md). # Licensing Understand how Digibee’s licensing works, including the current models, how consumption is measured, and the Platform's hosting options. ### **What you'll find here** * Overview of license tiers and features * Consumption tracking * Billing and usage reporting * Platform hosting options ### **Recommended for** Team administrators and platform decision-makers. ### Learn more


Licensing Models	Understand the current licensing models available on Digibee, their key concepts, and the differences between them.	09 - Licensing Models.jpg	Licensing Models
Licensing Consumption	Learn how to monitor your usage and track resource consumption based on your licensing plan.	10 - Licensing Consumption.jpg	Licensing consumption
Hosting Types	Explore the available hosting options and how the Platform operates in each environment.	11 - Hosting Types.jpg	Hosting Types

--- # 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.digibee.com/documentation/licensing/licensing.md?ask=&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.