Alternative to 10Duke

No. To be fair to 10duke they are specialists in identity, but their solution is not better than the best of breed options available and Nalpeiron also offers it own free internal account based licensing option that's similar to 10duke.
‍
- Seamlessly integrate with whichever IDP you use such as: 1. Microsoft Azure Active Directory (Microsoft Entra ID),
  Okta, Auth0, Amazon Cognito (AWS Cognito), Ping Identity (PingFederate) and more.
- Based on open standards such as OpenID Connect, OAuth2, and SAML2.
- Gives your customers an easy way to access your applications using a single identity, from SaaS to On-Prem to IoT.
- Supports Federated Identity environments.

Learn more at: https://docs.nalpeiron.com/zentitle2-docs/use-cases/identity-idp

- Auth0
- Authelia
- Authentik
- Authlete
- AWS Cognito
- Cloudentity
- Connect2id
- Curity Identity Server
- Duende IdentityServer
- Duo (Cisco)
- FrontEgg
- ForgeRock Identity Platform
- Keycloak
- Gluu
- Gravitee.io
- LoginRadius
- Logto
- Okta
- Microsoft Entra ID (formerly Azure AD)
- MITREid Connect
- OpenIddict
- OneLogin
- Ory Hydra
- panva/node-oidc-provider
- PingFederate (Ping Identity)
- SiteMinder (Broadcom)
- SSOJet
- Transmit Security
- WSO2 Identity Server
- Zitadel
- Google
- Yahoo
- PayPal
- Amazon
- Salesforce
- PhantAuth
- Facebook
- IBM Cloud Identity
- IBMid
- Deutsche Telekom
- MonoCloud
- Onegini Connect
- Imprivata
- OpenAM (ForgeRock/Open Source)
- OpenAthens Keystone
- Oracle Access Management
- Peercraft
- PhenixID Authentication Services
- Samsung
- Signicat

And more

Not in the same way or to the same level as Zentitle2. There's a huge difference in the platforms when it comes to dark sites and offline usage - as we started as a licensing innovator over 20 years ago it's in our roots and that of our products to offer deep levels of support for on premises environments.

Identity-based licensing 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.

That requires huge investments in offline technologies not supported by simple SaaS solutions.

Learn more here: https://docs.nalpeiron.com/zentitle2-docs/use-cases/dark-site-local-license-server-network-based-licensing

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.

Learn more: https://docs.nalpeiron.com/education-and-training/licensing-education/identity-based-vendors-vs-true-entitlement-management-solutions

Using an identity licensing approach leans towards everything in the cloud and a SaaS type deployment - this is OK if your application is pure saas but what if it's hybrid or has an on premises component?

This is where a broader and more capable solution like Zentitle2 wins the day.

On-premise deployments tend to be far more varied and complex, often requiring deployment into dark (offline) sites, with pools of concurrent network seats and millions of user desktops in the B2C model. In each case, there's more security, often the need for SDKs and specific OS targeting, and issues relating to virtual machine cloning and piracy. In addition, entitlement management tends to have more moving parts, often including license codes (activation codes) distributed via channels, a store.

In summary, Zentitle2 allows you to authenticate users in any way you wish, to deploy via s SaaS or on-premise use case, and to offer a B2C desktop, seat, or a large network of users on an intranet. You can sell via seats, usage, subscriptions, perpetual, or a blend of any pricing model you wish. You can connect Zentitle to other systems like CRM, ERP, billing, and e-commerce to automate the whole lifecycle.

Learn more: https://docs.nalpeiron.com/education-and-training/licensing-education/saas-vs.-on-premise-deployments