> 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/iot-and-hardware-licensing.md). # IoT and hardware licensing Monetize hardware and IoT devices with feature-based and capacity-based licensing, applying subscription, perpetual, consumption, and other software business models to physical products. Passive-type licensing within Zentitle2 is now much easier, with the more flexible seatID and methodology. Using the offline methodology we now have, you can attach your own unique hardware-type IDs to a license. {% embed url="" %} ### Hardware and IoT Monetize your Hardware and IoT by turning features on and off through subscriptions and purchases. Secure new untapped revenue streams.\ \ Monetize by selling and controlling access to additional cloud-based services that your hardware talks to, adding more value for your customers.\ \ IoT, Industrial Hardware Manufacturers, Electronics Manufacturers, Consumer Electronics, Telco Equipment, and other types of Dedicated Servers can all be monetized using Zentitle.\ \ Feature-based licensing that enables you to create differentiated offerings by turning on or off specific features for a given customer or market segment entirely through secure licensing.\ \ Capacity-based licensing allows you to securely restrict a customer's use of your device to a specific capacity limit.\ \ Bring all kinds of business models normally associated with software to your Hardware and IoT products, including perpetual, subscription, date-based, concurrent, consumption, and trust-but-verify. {% 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/iot-and-hardware-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.