Zentitle Concurrent Licensing Deployment Models
Floating features, element pools, floating features, how can you do this for your customers?
How are concurrent licenses deployed with Zentitle?
Zentitle supports two deployment paths for concurrent and floating licensing: the Zentitle Cloud for most customers, and a local license server for dark-site or isolated environments where outbound internet isn’t available.
Why two deployment paths matter
Most customers want the low-latency, zero-admin experience of the Cloud. A smaller group — defence, regulated industries, sovereign-cloud — can’t use the public internet. Supporting both from the same platform avoids a separate licensing stack for the harder customers.
How the two paths compare
The client protocol is identical, so applications need no code changes across the two modes.
- Zentitle Cloud for connected customers, globally low-latency
- Local license server as a Docker container inside the customer’s network
- Licenses delegated from the cloud into the local server
- Full support for floating, named-user, feature-based, element-pool and consumption models
- Usage data (high-water, low-water, overdraft) flows back to the cloud where possible
Who this video is for?
Sales engineers and architects planning concurrent licensing for a mix of connected and disconnected customers.
Video transcript
Auto-generated from the video and lightly edited for readability.
A lot of software vendors want to make use of some sort of network-based licensing model. Some sort of concurrent or floating model using our element pools, floating features, consumption tokens, and so forth. And so we support two very flexible ways of addressing that. The easiest one is for the application to work against our Zentitle Cloud, fully multi-tenant, high availability, low latency from anywhere in the world. So if you've got customers in China, Japan, South America, North America, and so forth, and you want to provide a really easy to adopt reliable cloud-based licensing service, the Zentitle Cloud is perfect for that.
Sometimes though, you may have customers often big customers that are wanting to work in a completely isolated environment. For a couple of reasons, one could be security. Right? They don't want any kind of outside access, but another one could be reliability or sovereignty.
Where they wanna make sure that there's no dependency in terms of their day to day operations on some external cloud service being available.
So for those situations, we provide our local license server that's deployed as a Docker container, so it can be employed very easily in any kind of environment.
And what you can do then is delegate a license from the Zentitle Cloud into that local license server. It's actually locked into that dark LAN environment.
And then your applications can simply hit against that local license server. The beauty of this approach is the protocol from your application to the local license server is identical to the protocol between that the Zentitle cloud. So no additional changes need to be made to your application to support that.
This allows you to deploy in any of these full concurrent license models, including things like named user, floating features, element pools, consumption-based models, and so forth, and we will track the usage of those licenses, both high water, low water marks of overdraft licenses and so forth. As well as arbitrary analytic data and be able to flow that back to the Zentitle cloud, where you can use that either for reporting, for billing, and so forth.
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