What does the Zentitle architecture look like?
Zentitle’s architecture centres on a cloud-based multi-tenant repository for all entitlements, with two primary client paths: an SDK-based library for on-prem applications and a REST API for SaaS applications.
Why this architecture matters
The two-path design means the same entitlement model works for desktop, server, embedded and SaaS software, so you only design your licensing model once. It also means you get anti-cloning, virtualization detection and encryption uniformly across every target.
How the components connect
Applications authenticate and exchange encrypted payloads with the Zentitle Cloud.
- Generated SDK libraries for Windows, Mac, Linux (Intel and ARM)
- REST API for SaaS applications to look up entitlements and activate seats
- Machine fingerprinting for reliable seat identification
- Virtualization detection and anti-cloning built in
- End-to-end encrypted connections guard against tampering
Who this video is for?
Architects and senior engineers who want a concise architectural overview before reading the integration docs.
Video transcript
Auto-generated from the video and lightly edited for readability.
So what does the Zentitle architecture overall look like? Well, of course, as you know, we have a cloud-based multi-tenant environment that acts as that central repository for all the licenses, all the entitlements, that your customers has purchased, as well as all your definitions of your various plans, what features should be included in which plan and so forth.
So once you have that established, then the way your applications can then reference those licenses and therefore enforce whatever license rates, you've sold.
Two main paths. One is for on-premise applications, and there, for Windows Mac, Linux, and so forth, we can generate a library for you that you would then embed into your application Your application at runtime to activate a license would make the appropriate calls into the library to pass on the credentials that the customer is using could be a license key, could be an identity.
Our library will then make the call back to the Zentitle Cloud, to take care of the actual activation, and then bring all the metadata for that license back into that cached environment sitting in that end customer device.
And so all of your interaction with licensing happens through our library that gives you a full suite of functions to be able to activate, deactivate, query, and so forth.
And it also calculates a fingerprint for that machine. So you can really reliably distinguish one, end user from another, as well as that also handles our virtualization detection and anti-cloning.
For SaaS environments, it's even easier, right? Within your SaaS application, again, could be single-tenant, could it be a multi-tenant.
You can make a straightforward rest based call into the Zentitle database and look up the appropriate entitlement for that customer, activate the seat and so forth and again, bring all that metadata back around that license as a straightforward JSON payload.
Now in both of these cases, you have full encryption across that connection. So you never have to worry about, you know, men in the middle attacks or other potential approaches to interrupting sort of the integrity of that entitlement enforcement.
Decouple your
monetization today
Join the enterprises scaling their revenue without rebuilding their stack every year.
Unleash the monetization potential of your software / SaaS / Hardware