Zentitle business models
PreviousZentitle supports every platformNextCritical differences for secure site/offline/dark site management
Last updated
Was this helpful?
Last updated
Was this helpful?
Zentitle enables you to adopt proven software licensing models that increase revenue while simplifying license management.
With Zentitle Cloud-Based Licensing, implementing revenue-boosting software licensing models is quick and straightforward. It's the most effective way for software vendors to grow sales and revenue.
These licensing models can work together, simplifying complex use cases that are easy to describe but typically difficult to implement.
Zentitle is incredibly flexible, accommodating both simple and complex business models.
Set up trials with customizable limits on time, usage, features, or any combination.
Offer subscriptions for any product type—on-premise, server, SaaS, hardware, or IoT.
Traditional licenses are easy to use and migrate from your existing licensing platform.
Enable business customers to limit the number of simultaneous users or devices.
Control and throttle access to connected resources in your software or SaaS products.
Support customers operating in dark sites without internet access through Zentitle's Network Licensing.
Track software usage for billing flexibility, with simple allocation of consumption rights.
Let customers access your software modernly, with email and password login.
Manage both installed software and cloud-based elements under a single license.
One of the real benefits of adopting the Zentitle platform as you bring your products to market is the ability to separate the business model from the application implementation itself. You instrument your application once, then can take it to market with various business models, such as feature-based licensing that lets you enable or disable specific capabilities, modules, and components per license.
The platform supports all types of time-based licenses: one-month subscriptions, one-year subscriptions, or licenses that expire on a specific date, like December 31st, 2025. You can implement any date-based metric you need.
You can also offer perpetual or non-expiring licenses with optional maintenance contracts. The entitlement tracks when maintenance contracts end, allowing you to build logic into your application and only allow software updates for licenses within their maintenance window.
For version-based licensing, you have two options. First, you could require separate licenses for each product version (version 2, version 3, etc.). However, we recommend defining a valid range of versions within the entitlement. Start with a 2.x line, then as customers upgrade to 3.x or 4.x versions, they keep the same license but update their attributes to include the new version ranges.
We fully support usage-based, consumption-based, and software-as-a-service models through our consumption tokens and other capabilities. This makes it easy to track resource usage over time within the license.
From a capacity standpoint, you can use entitlement attributes to set specific limits. For example, a lower-cost edition might manage up to 10 widgets, a mid-tier up to 50 widgets, and an enterprise edition could offer unlimited widget management. You can include as many of these attributes as needed.
We also support named user models. You can set up a license for 10 specific users based on identity and allow your end customer to manage their list of authorized users.
Similarly, we allow integration with identity-based systems to provide experiences like Adobe Creative Cloud or Office 365, where end customers activate seats using email addresses and passwords. We integrate with any OpenID-based identity platform—whether that's Auth0, Okta, Cognito, or Azure AD.
This provides additional benefits for end customers with their own identity provider (IdP). They can federate into these identity platforms, allowing single sign-on access to license rights.
We provide these capabilities for customers with ongoing internet connections, intermittent connectivity, or completely disconnected ("dark site") environments. This works for node-locked individual seat licenses and concurrent or network-based licensing models running in dark environments.
Across all these capabilities, you can monetize your application however you want, mixing and matching models without building dependencies into your core application. This means you can easily deploy new packages, offerings, and pricing without engineering changes.