Add support for Identity-Based Pricing #1995
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description 📣
This PR adds support for identity-based pricing.
Logic: In order to implement identity-based pricing, we create a new
price
in Stripe withseat_type
metadata (can be eitheruser
oridentity
). When Infisical fetches back the feature set from the license server, the license server computesidentitiesUsed
and hasidentityLimit
based on the Stripe product +metadata
on theprice
. The Infisical platform then imposes the necessary constraints at the frontend UI-level and backend.Included in this PR:
identityLimit
is specified in the customer's feature set, then checks are imposed for example when inviting a new user to an organization or when a new user logs into an organization via SAML / LDAP.Note: Existing users of Infisical are not affected by the price change; only new users that will be bound to the identity-based prices on Stripe.
Type ✨