> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/use-cases/use-case-directory/usage-based-licensing.md). # Usage-Based Licensing Learn how Zentitle lets you license software by consumption using usage-based tiers, usage credits, metering, and shared feature limits, with both hard and soft limits. {% embed url="" %} Drive revenues by offering consumption or usage-based pricing and packaging By measuring usage along with complete control, a flexible world of usage-based monetization opportunities is opened up.\ \ Usage-based tiers, usage credits for add-ons and features, and post-pay usage-based billing—whichever way you want to license your software based on consumption is possible. ### Limits Limits that can be controlled using Zentitle include setting how many times something specific can be done on a plan or limiting an amount, such as an included ‘x’TB of Storage.\ \ Zentitle has a robust overdraft license feature that lets you set flexible limits for software usage.\ \ You can establish hard limits that are strictly enforced and soft limits that trigger warnings when exceeded. ### Usage Credits Zentitle can easily control and monitor the consumption of usage credits purchased for add-on functionality. You may wish to include a default amount of credits with each plan or give away Trial credits.\ \ Zentitle allows you to easily implement usage-based business models for pre-pay use cases. With its versatile features, Zentitle allows businesses to monitor and charge customers based on their software usage. ### Metering Similar to utility bills, you can use Zentitle to accurately meter and measure software usage over time, allowing for post-pay billing.\ \ Potential monetization strategies can be modeled financially before pricing plans are implemented, and software usage analytics, which can track any feature, can inform them. ### Shared Limits Sometimes, on a multi-user account, you may only want to allow limited use of a particular feature at any moment. Using features and resource control can be concurrent with Zentitle’s Element Pools and Zentitle floating feature capabilities. {% hint style="success" %} Let's jump on a call and discuss how we can help, get in touch with your account manager today → [Setup a 1:1 discussion](https://www.nalpeiron.com/get-a-11-demo.html) {% endhint %} --- # 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.nalpeiron.com/zentitle2-docs/use-cases/use-case-directory/usage-based-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.