Zentitle Consumption Tokens

One of the big trends that we're seeing in the industry is software vendors wanting to experiment more with usage or consumption based pricing models. And of course, the key component of being able to enforce a consumption or usage based approach is to be able to track that ongoing usage against the application by the pool of users.

So one of the things we've done is built in as a primitive within the entitlement definition. The ability to have a consumption token feature, you can have as many of those independent features as you like within a given entitlement.

And what they allow you to do is to track the count, the usage of whatever metrics you as the vendor want to value on that usage basis. So for example, you may want to sell a one year subscription to a given product with the ability to run a thousand reports during that one year period. And so every time a report is run, the software through our SDK would check out a token from that consumption token pool. So you would be able to track how many reports have been run. And then perhaps when that pool is exhausted, even perhaps, before the subscription of the license itself expires.

The customer can then come back to the vendor and purchase additional tokens to be able to run additional reports. And so this gives you a powerful way to mix and match between various business models, subscription, perpetual, etc, combined with a usage based component.