We've extended the configuration of metered entitlements with an ability to control whether access will be denied when customers reach their limit or not using no-code.

By default, Stigg enforces access to metered entitlements according to customer's usage - when customers reach their limit, additional access to the feature is denied. This concept is known as "hard limits".

With this new functionality, you can now decide whether to continue granting access when customers reach their limit - this concept is known as "soft limits".

There are common use-case where soft limits are helpful:

1. In enterprise plans, to prevent disruptions to customers' business - excessive usage is commonly leveraged for discussions with sales, CS and account executives about expansion opportunities and increased commitment.

2. When implementing an automatic smart upgrade flow to a higher tier based on customer usage instead of charging for overage - upgrades help increase recurring revenue, as opposed to overage charges are less predictable.

3. During the initial integration with Stigg - companies that already have soft limits in-place today and want to gradually rollout the integration with Stigg, can do so while activating enforcement at a later stage without any additional code changes.

Soft limits can be applied to plan entitlements, add-on entitlements and promotional entitlements. They can also be applied at the subscription level for entitlements with variable values.

Soft limits are supported in the Stigg Node.js SDK v3.5.0, Stigg Python SDK v1.48.7, Stigg Ruby SDK v1.48.7, Stigg Go SDK v1.48.7, Stigg Java SDK v1.48.7 and Stigg JavaScript SDK v3.4.0 or later. 

Customers that leverage Stigg's persistent caching service should also upgrade to v2.11.0 or later.

More details about Stigg's limit enforcement capabilities can be found here.