TreeSize Tightens Support: Perpetual-License Holders Face Subscription Requirement for Future Updates
TreeSize's vendor decision to withhold future support unless customers move to a subscription model marks another vendor push away from perpetual-license economics. IT and procurement leaders must reassess software lifecycles, total cost of ownership, and contract language to manage vendor lock-in and service continuity.
What changed
TreeSize - a popular disk-space analysis tool - has signaled it will not renew perpetual-license support unless customers convert to a subscription. While vendors often sunset legacy licensing, this move forces organizations that relied on perpetual licenses for predictable CAPEX to confront an unanticipated shift in renewal and support costs.
Why this is significant
This is part of a broader industry trend: vendors recasting revenue models to subscription to stabilize recurring income. For buyers, the shift alters cost profiles (from one-time to recurring), complicates budgeting, and can increase operational risk if support and security updates are tied to a subscription. It also raises contractual and governance issues: were perpetual licenses sold with implied ongoing support, and how does that affect renewal negotiations?
Business implications
IT teams must quickly inventory affected assets, assess the operational impact of forgoing future updates, and model TCO under subscription scenarios. Organizations with large deployments may face meaningful increases in annual spend, while small teams might accept reduced features. Alternative strategies include negotiating extended support, seeking perpetual-compatible forks or open-source replacements, or consolidating tools during contract renegotiations.
Actionable guidance for leaders
Audit your license types and support expiry dates, and quantify the cost of subscription migration versus risk of unsupported software. Update procurement templates to require clear end-of-life, transition, and pricing protections. Where feasible, push for phased migration clauses or consider strategic replacements that align with longer-term cost predictability and operational resilience.
Original Source
Ars Technica
