Skip to main content
Version: v0.25.0 (Latest)

Products and SKUs

A product is a sellable bundle of features. It groups a set of features under a stable product id and a display name. It organises them into editions, which are the SKUs a customer buys. A product is pure data. It carries no behaviour, only the mapping from each edition to the feature keys that edition grants.

Editions​

An edition is a named tier within a product, mapped to the set of feature keys it includes. A product can offer several editions. The same feature can appear in more than one of them, so editions layer from a smaller bundle to a larger one.

For example, the Enterprise Development Kit product offers an enterprise edition that includes the enterprise semantic-modeling feature. A richer edition maps to a larger feature set. A leaner one maps to a smaller set. Because the mapping is many-to-many, a feature is never tied to a single edition. Editions compose feature keys freely.

From purchase to signed grant​

Products and editions describe what can be sold. They do not, by themselves, entitle anything at runtime. When a customer purchases a (product, edition), that selection is expanded into the concrete set of feature keys the edition grants. That resolved feature set is what gets signed into the license.

The catalog drives this expansion at issue time, when the license is minted. From then on the signed feature set is authoritative. A deployment's runtime can reason about exactly the features the customer paid for, even if its local catalog later changes.

Reading the catalog​

An operator can list the products a deployment knows about through the Platform Admin API, each with its id, display name, and editions, alongside the feature catalog. The per-product summary in the license status projection reports, for each licensed product, its edition together with the licensed module and quota key names. An operator can see which products a deployment is licensed for. See the Platform Admin API reference for the wire shapes.

Where products fit​

  • Features are the keys a product's editions bundle.
  • The catalog is the read-only view over the products and features a deployment supports.
  • Entitlement Resolution evaluates the signed grant against each command, not the product itself.