> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/education-and-training/licensing-education/identity-based-vendors-vs-true-entitlement-management-solutions.md).

# Identity-based vendors vs true Entitlement Management solutions

Some vendors believe an identity-based approach is best, but we disagree. It's highly restrictive and rooted in the vendor's background, having built identity systems first and then layered on some licensing capabilities.

It's far better to have a flexible entitlement and licensing-based system designed to support any form of deployment rather than to fix on a user-name-based approach—why compromise?

### Why You Should Not Get Locked into an Identity-Only Based Licensing Solution

Sometimes, companies ask us about the difference between identity and entitlement management. While they have similarities in terms of providing access, they're fundamentally different systems. With an identity system, you're restricted to an identity-based approach (email address, username, password, etc.), which creates a one-size-fits-all model. This might work fine if you only need to manage identities with a lightweight set of attributes.

However, if you want to truly understand what rights you've sold at the company level and allow individuals, desktops, servers, devices, and other entities to access those entitlements, then entitlement management is what you need. Unlike identity-based systems that narrowly focus on authentication (who users are), entitlement management focuses on what rights users inherit from their association with an entity that has purchased various licenses.

Identity-based systems are particularly restrictive for desktop, server, or cloud-based deployments running in virtualized environments. Since you're only tying use to an identity, you can't distinguish between VMs or handle cloning effectively. Our entitlement platform, however, gives you direct management power over these scenarios.

Additionally, identity-based systems struggle with offline environments. If you have customers working in disconnected or air-gapped environments (what we call "dark sites"), leveraging a pure identity-based system becomes challenging. We integrate with IDPs, Okta, Auth0, etc., allowing you to support these flows within our standard entitlement management system, including offline use cases.

The channel presents another challenge. When working with channel partners who maintain an inventory of entitlements and licenses to sell, they can't effectively use a pure identity-based system because they don't yet know who'll buy the products. Entitlement management allows them to manage licenses without knowing the end users' identities.

Entitlement management provides flexibility even within a pure SaaS environment. It enables identity and license key/device-based activation, handles virtualization and offline scenarios, and offers superior channel partner support.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nalpeiron.com/education-and-training/licensing-education/identity-based-vendors-vs-true-entitlement-management-solutions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.