Overview

Feature entitlements let you control which capabilities of your product each license enables. With them you can sell consistent product tiers such as Standard, Pro, and Enterprise, roll out features to selected customers, and set per-license values and limits for your application to enforce, all from the same build of your app. This is often called feature-based licensing.

How entitlements are assigned

Feature entitlements can be assigned in two ways, which you can also combine:

• Through Entitlement Sets, which group multiple feature entitlements into reusable collections for standardized license tiers. See Features and Entitlement Sets.
• Directly on individual licenses for more granular, per-customer control, including overriding values from a linked Entitlement Set. See Assigning Feature Entitlements.

Values and expiry

Each feature entitlement may optionally include a value, always a string, which your application interprets, for example as a number or a flag, to enforce limits or enable conditional functionality. Feature entitlements enable, disable, and configure features; they do not track consumption. To meter usage per license, such as API calls or exports, use meter attributes, which implement usage-based (metered) licensing.

When a feature entitlement is added directly to a license or a value is overridden at the license level, it can also include an expiration date. This expiry date is license specific and applies only to that custom or overridden entitlement, enabling time-bound access to individual features, such as feature-level trials or temporary feature unlocks.

Using entitlements in your app

Your application retrieves entitlements at runtime through LexActivator or LexFloatClient and adapts its behavior accordingly. See Accessing Feature Entitlements, and browse the Use Cases for practical patterns like tiering, value-based limits, beta rollouts, and feature trials.