Skip to main content
Use a plan to name the commercial offer that you sell. Use a plan version to define the published pricing, entitlement, billing, and feature rules for that offer.

​
Create the plan identity

Give each plan a clear title, stable slug, and description. Your application should use feature slugs for runtime checks. Do not branch request-path code on plan names such as Pro or Enterprise.

​
Build a draft version

In the version, configure the billing period, currency, included credits when used, and the features that the customer can access or consume. A usage feature also needs a meter that defines the event and property to aggregate.

​
Publish, then assign

  1. Create and review the draft plan version.
  2. Publish the version.
  3. Sign up a customer with planSlug or assign the published version directly.
  4. Create a new version when pricing or entitlement rules change.
Published versions preserve the commercial rules that existing customers bought. Move a customer to a new version only when you intend to change their commercial terms. Read Plans and versions for the model and First plan for the first setup.