Zentitle Architecture

Zentitle split down into its moving parts all explained

Watch more videos about how to license your software and increase revenues

1000s of software companies have used Zentitle to launch new software products faster and control their entitlements easily, many going from startup to IPO on our cloud software license management solutions

Software Licensing Customer LogosSoftware Licensing Customers

Zentitle - the Enterprise-Class Software Monetization Platform

18 Years+

Track Record

$1B+

Revenues Protected

300M+

Transactions / Month

99.9%+

Uptime SLA for 10 Years+

Zentitle supports 100M's users 24x7x365 for the world's leading SaaS, Software and IoT companies

Your long-term partner for software business growth

Zentitle meets the standards for scale, security and operational excellence demanded by enterprise-class software companies

From startup to $1Bn in ARR partnering with Nalpeiron

Partner for 8 years

From startup to VC funding to IPO for millions of users, all on Zentitle

Partner for 14 years

zentitle customer logoszentitle customer logos

What's in this video

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.