Versions and maintenance

A perpetual purchase allows continued use, but not necessarily free upgrades forever. The maintenance period determines eligibility based on each version's release date.

Own the current version, updates included for a year

Set the policy to Perpetual with 365 maintenance days. Maintenance begins at first activation. Publish versions such as 1.0.0 and 1.1.0 in Software versions with their actual release dates.

Versions released within the maintenance period remain usable. Versions outside that period require extended maintenance entitlement.

How does the app report its version?

Set AppVersion / app_version in your SDK configuration object, for example 1.1.0. Maintenance control requires a published application version. Use three numeric components, such as 1.2.3. Release publication dates are immutable to preserve purchased entitlements.

Set a version range, such as 1.0.0 through 1.999.999. The running version must match the signed grant.

Provide downloads

Version records can include an HTTPS download URL and SHA-256 checksum. The portal shows only eligible versions. These records provide links; they do not upload installers or automatically install updates for customers.