What each platform release added, and why it matters in the room when the auditor is sitting across from you.
Flexera One is a SaaS platform. Unlike Agent and Beacon, you don't pick a version: Flexera does, and pushes the upgrade to your tenant on a monthly cadence. The ITAM surface is in a state of perpetual evolution.
This edition tracks what each platform release adds. For each new feature or capability, I write the 'What this means' answer: the one the consultant at the customer meeting needs, the one the auditor doesn't get to argue with. Product managers get features. SAM leads get the implications.
The Flexera One and Agent/Beacon release cycles overlap but aren't identical. A platform feature this month might depend on an Agent or Beacon component shipped two months earlier. Cross-reference is intentional.
The first dispatch starts from the non-empty monthly releases and grows from there. Every Flexera One monthly release gets appended as it ships. If a feature is older than what's shown here and you need context, the Flexera docs cover the full archive. Go read them.
These are the published problems in Flexera One ITAM itself, not in the agent or the beacon. Each one has a reference, a severity and a stated fix. The full catalogue is on the security page.