Zentitle Virtualized Environments

VMs, docker containers, OSes with virtualized environments underneath, all catered for

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

Wasn't that many years ago where virtualized environment we're still relatively uncommon.

Spring forward to today, and really virtualized environments are everywhere, whether it's full VMs, docker containers, or even individual desktops now. A lot of desktops running Windows eleven, for example, present themselves as being virtual And under the covers, they are, in fact, a virtualized environment. So we wanted to build in really great support for a virtualized image detection and decloning, and to ensure that you get properly paid for every single seat of the license that you sell to your customers. The way we do that is with a technique we call the nonce. So think of the knot as being kind of a transient secret. So every time there's a communication between the application back to the Zentitle Cloud, as part of the license refresh.

We will generate a brand new notch that comes back from the server that is then registered to that individual in So if that instance stores that nonce and then makes a subsequent request, they have to provide that nonce again that nonce comes in as part of that request. We'll see that they actually did provide the right nonce. So we'll make that a validated authenticated use of that seat of the license.

And we will then generate a brand new right, which will then go back to the client. And so that will continue through that conversation.

Now, if The process gets activated so they get their nonce, then they clone themselves. So both process one and process two will then have the same secret.

The first of these that then do that refresh request will have that be validated by the Zentitle Cloud, and then that will generate a brand new nonce back to whichever process made that request.

But now one of those two processes will no longer know the current nonce that was just refreshed. And so when they do a refresh, They won't have the correct nonce, and the request will be denied. Now when the request is denied at that process, they realize, Hey, we don't have a seat because we lost it a clone, etc.

Then the application can decide, Hey, I wanna try checking out another seat against the license So that's up to you as the vendor to define what kind of policy you want to enforce when we've detected that a clone has already grabbed that seat. Away from that process.