Zentitle Platform Technical Architecture

What I'd like to do now is to give you a very high level overview of the entire Zentitle architecture in the ecosystem.

So of course, it starts with the Zentitle Cloud. Fully multi tenant, very easy to spin up an account. We can work with you to do a proof of concept and so forth. And that allows you to have a consistent, highly scalable system of record for keeping track of everything that you've sold each and every individual customer, when those rights expire, what features should be included and so forth. So that acts as that system of record.

Now, that can be populated fed by whatever order entry process you have. So whether you're doing inside sales, fulfilling through say sales force or dynamics, Zoho, SAP, Oracle NetSuite, and so forth.

You can map all of that order fulfillment into creating the appropriate set of rights within the Zenpuddle cloud. And of course, if you're using e commerce environment, you know, Stripe, ZORF, Chargeify, and so forth, we can accommodate all of that as well. So here, there's a very powerful set of web services to populate that.

Now within that, as you are defining your various offerings, we have full capabilities to allow you to easily define what set of rights each individual package or SKU or offerings should have. And so you can create as many individual offerings as you like each of them with their own unique set of rights. You can do upgrades for a customer from one addition to another and so forth.

Within that set of offerings, we support a wide variety of different business models, and these are all out of the box. So if you want to do perpetual based licenses, perpetual plus maintenance, feature based licensing, turning individual capabilities, components, modules, on or off for given customers, subscriptions, one year, two year, one month, three days, and so forth, concurrent and floating based license saying. So a hundred concurrent seats. Nameded users for a specific set of named individuals.

Arbitrary seat counts, so we support both single seat licensing as well multi seat licensing.

Capacity based licensing, so you may have some metric that you wanna be able to limit within your given application.

Of course, we also support usage based models. So capturing usage information from your application, flowing that back to the cloud for use in a billing model. And then we have great support for trials. So if you're looking to have a trial component as being part of your go to market, You want to set people up on a trial, self serve, easily have them register, get an initial license very easily. And then work to convert them into a fully paid license.

And so you can then take any of those business models tie that into your packaging and then have applications reference those rights and enforce those rights across a wide number of deployment models. So whether you're dealing with on prem software, whether it's desktop, server based could be Windows, Mac, Linux, Intel based, ARM based, Apple silicon, and so forth. We have you covered there. IOT with a embedded Linux, again, both Intel and ARM based. And of course, more and more we're doing SaaSbee. Models where companies are coming to us to say, Hey, we need you to manage the definitive set of rights against all of our SaaS customers.

And then we support mobile as well.

Now within all of that, we can support both licensed key base models where you assign a given serial key in arbitrary string format of that is totally up to you.

And that is the way that individual end customers will access the specific set of rights that you've sold them, or we can also support identity based models where you can use are built in identity system, or you can leverage an existing identity platform that you may already be using with your customers for, you know, support logins or knowledge base and so forth. So we can tie into any open ID connect based identity platform. All zero, Octa, forgerock, you know, what have you?

In terms of the applications using our SDKs in order to access all of this. We have language bindings in C, c plus plus, Java, Python, and so forth. So any language that you're making use of you can easily access all of these capabilities from within those applications.

From an end customer standpoint in terms of being able to access those license rights. We, of course, support online connected customers, whether they have a permanent connection or at least an intermittent level connection, Our lease period mechanism gives you a lot of fine grained control about even for application licenses deployed in the field. You still have control over how frequently those should be refreshed.

We also support offline node lock licenses. So if an individual end customer needs to activate an individual desktop or an individual server, we support easy offline activation approaches there. And then if you sell customers a large seat count license, for example, into an enterprise, and that enterprise is wanting to run-in a completely secure or dark environment we can provide you with a local license server that gives you the ability to delegate licenses into that local license server have that deployed at that end customer environment in a secure manner in a docker container that then allows your licensed policies to be securely, and predictably enforced within that network but not requiring any ongoing connectivity back to the internet, to the Zentitle cloud, and so forth.

So those are all the capabilities from an end customer standpoint and go to market Now all of that, of course, being represented in the Zen Ploto cloud, including the usage data that comes back from those applications, So you can use that for robust reporting. Like show me all the licenses that are about to expire in the next thirty days. Or show me all the licenses for, you know, this top customer or whatever you choose. So really easy access to that information both directly through our UI as well as through APIs.

We also support billing So you can flow that usage data back through the Zentitle Cloud and then use that as an underpinning for some variable usage based or metered billing model.

We can also provide an end customer facing portal that can be branded according to your specific logo, custom stylesheet, And in fact, you can even reference it through a domain of your choice.

That is available out of the box. So you've got a robust set of capabilities without having to write anything yourself. And again, that can also be integrated with your identity platform, so you can have single sign on across a broad set of end customer facing services, with a single set of credentials.

And of course, one of the other key areas that leverage this information our support and renewals. So support from the standpoint of being able to see definitively what specific licenses a given customer has We also get, telemetrics back from the field with regards to things like what version of windows are they running? What features are they using? What version of the application are they using and so forth.

So this gives support all the important intelligence about that customer to really provide the highest quality support. From a renewal standpoint, we can also show usage of the application, and how many seats of a given license, for example, are being used over time, what features are being used so that from a renewal standpoint, They cannot understand, you know, is the account growing? Is it shrinking? Who's using it?

Who are the individuals who are making most use of it? So they can really hone in on What is the value that the customer is currently getting out of the application? And how should we take that into account as we start to propose, a renewal?

And so this entire infrastructure really kind of forms the central nervous system of a software company and allows your end customers and all the other stakeholders of the organization to have that common frame of reference of exactly what you've sold and exactly how it's being used.

‍