> 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/trial-management.md). # Trial Management Set up and manage trial licenses in Zentitle, such as short-term or 30-day trials, for SaaS or on-premises deployments, including offline activation and converting a trial to a paid license. {% embed url="" %} Zentitle makes trial management fast and easy. Set up a trial of any type on your portfolio in minutes, set a range of parameters that suit your business, and easily restart ended trials. Driven by a simple UI in our developer portal by any designated team, or automate all of this via our APIs. One important capability for any software vendor to manage well is letting customers try out an application through a trial-based model. With Zentitle, we make trial management super easy. You can set up multiple trial offerings—for example, a 14-day short-term license or a 30-day trial license. These can be given to different people based on criteria like how much information they provide. When you issue a trial license entitlement, you can leverage it in a pure SaaS environment or on-premises. In a SaaS setup, you might send customers an email login to your application, which then looks up their entitlement and shows how many days remain in their trial. Customers can request a trial through your site's process for traditional desktop or server-based software. You'd issue a short-term trial license—either identity-based or license key-based—which they can activate in their on-premises environment. They can even perform offline activation, use your application for the prescribed time, and hopefully convert to a full paid license. {% 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/trial-management.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.