Products & versions

A product is something you license — your app, a module, an edition. It’s identified by a product code plus a product version (SemVer, e.g. 2.1.0); the two together are unique. A product carries its own features and metrics, and moves through a lifecycle:

Draft → Preview → Published → Disabled → Archived

Only a Published product can be granted to customers.

Versions are first-class

A new version isn’t a flag on an existing product — it’s a separate product that shares the same product code, carries its own version number, and points back to its predecessor (a lineage). Each version owns its own features, metrics and plans, so you can evolve 2.0 without touching the licenses already issued against 1.4.

That independence is the point: changing a newer version never silently alters what an existing customer is licensed for.

Where it runs

A product can declare application scopes (e.g. Desktop, Mobile, Cloud.Production) that restrict where it may be activated — handy when the same code ships to very different targets.

How it relates

• Defines → features and metrics that belong to this version.
• Priced by → plan sets, which are scoped to a single product.
• Granted via → entitlements, which snapshot the product’s features at grant time.