> 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/ui-product-catalog/licensing-and-business-models.md). # Licensing and business models ### Benefits of the Zentitle Platform {% embed url="" %} One of the key benefits of adopting the Zentitle platform as you bring your products to market is the ability to separate the business model from the application implementation itself. You instrument your application once, and then you can take it to market against a wide range of business models. #### Flexible Licensing Options Feature-based licensing enables you to enable or disable specific capabilities, modules, or components for a given customer according to their license. Time-based licensing options include one-month subscriptions, one-year subscriptions, or licenses with specific expiration dates. Any date-based metric can be implemented. Perpetual or non-expiring licenses can be offered with or without maintenance contracts. You can track when maintenance contracts end and incorporate that information into your application logic, such as only allowing software updates for licenses within their active maintenance window. #### Version Management Version-based licensing can be implemented in two ways: 1. Requiring separate licenses for each product version 2. Defining valid version ranges within entitlements enables customers to use the same license across multiple versions by simply updating the attributes. #### Usage-Based Models {% embed url="" %} We fully support usage-based or consumption models similar to Software-as-a-Service on-demand approaches using consumption tokens. This allows you to track resource usage over time within the license. #### Capacity and User Management Entitlement attributes let you set specific limits on various parameters. For example, a lower-cost edition might manage up to 10 widgets, mid-tier up to 50 widgets, and enterprise editions unlimited widgets. Named user models allow you to set up licenses for specific numbers of users, limiting access to named individuals based on identity. End customers can manage their list of authorized users. #### Identity Integration {% embed url="" %} We support integration with identity-based systems, such as Adobe Creative Cloud or Office 365, where customers activate seats using identity credentials. We integrate with any OpenID-based identity platform, including Auth0, Okta, Cognito, and Azure AD. If customers have their own identity provider within their corporation, they can federate into these identity platforms, enabling single sign-on for license access. #### Connectivity Options These capabilities work for customers with ongoing internet connections, intermittent connections, or completely disconnected/dark site environments. We support node-locked individual seat licenses and concurrent or network-based licensing models for offline use. #### Flexibility Without Engineering Changes Across all these capabilities, you can monetize your application in any way you want, in a mix-and-match manner, without building dependencies into your core application. You can easily deploy new packages, offerings, and pricing without engineering changes. --- # 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.nalpeiron.com/zentitle2-docs/ui-product-catalog/licensing-and-business-models.md?ask=&goal= ``` `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.