Skip to content
Article

Software Licensing Models Explained: Subscription, Perpetual and Usage-based

Subscription, perpetual, or usage-based: choosing the right license model can save tens of thousands of euros. This is a clear overview of all models, their pros and cons, and how to make the right choice.

  • May 20, 2025
  • 5 min

Subscription, perpetual, usage-based, per user, per core or per server: the landscape of Software licensing models has become more complex in recent years. That complexity costs organizations money, because the wrong model means consistently overpaying.

The three main models

Subscription

The most common model. You pay periodically, monthly or annually, for access to the Software. Benefits: always the latest version, low entry costs, and flexible scaling. Drawbacks: no ownership, higher long-term costs, and price increases upon renewal.

Perpetual

You buy a license once and pay annually for support and maintenance, often a fixed percentage of the purchase price. Benefits: ownership and predictable costs. Drawbacks: a higher initial investment and no entitlement to new versions without an upgrade. Increasingly, Software vendors are discontinuing this model.

Usage-based

You pay based on actual usage, such as the number of transactions, the amount of stored data, or the number of active users. Benefits: costs follow usage. Drawbacks: unpredictable invoices during peaks and difficult to budget.

Hybrid models

Many Software vendors combine models. Since Broadcom’s acquisition, VMware is sold only as a subscription per core; other vendors combine hardware with Software subscriptions or work with pricing tiers per number of users. Such models make comparisons with alternatives difficult. That works out well for the Software vendor.

How do you choose the right model?

The choice depends on expected usage duration, usage stability, and the importance of ownership. Always have the total cost calculated over at least three years; only then will it become clear which model is truly more cost-effective.

How SoftVaro helps

SoftVaro calculates the models for your situation and negotiates on your behalf for the model and terms that best fit.

Frequently Asked Questions

The most asked questions about this topic.

What is more cost-effective: subscription or perpetual?

A subscription always gives you the latest version and lower entry costs, but higher ongoing expenses. With a perpetual license, entry costs are higher, but you own the license. Which is more cost-effective depends on the duration and support costs. Note: more and more Software vendors are offering only subscriptions.

When do you choose usage-based?

Usage-based is suitable if usage fluctuates significantly. You pay only for what you use, but costs are harder to predict. With stable usage, a fixed license is usually more advantageous.

How do you choose the right licensing model?

Have the total costs calculated over at least three years, including support, upgrades and any exit costs. SoftVaro assists with this analysis and negotiates the model that suits your situation.

Ready to save on software?

SoftVaro negotiates the best deal on your behalf with over 4,000 suppliers. Independent, transparent, within 24 hours.

More from the knowledge base

Change language

More pages

Choose per category what we may place. Strictly necessary cookies cannot be turned off.

  • Third-party analytics (Google)

    Google Analytics 4 for product improvement: page views, time on page, button clicks. In addition to our own privacy-friendly Umami (always active, no consent required). Data is transferred to Google in the US — under Standard Contractual Clauses.

  • Marketing

    Leadinfo identifies companies visiting the site by IP address, for B2B lead follow-up (no personal data of individual visitors). Google Ads sets advertising cookies for remarketing and conversion measurement; this transfers data to Google in the US under the Standard Contractual Clauses.

  • Strictly necessary

    For basic site functionality: remembering your language preference, rate-limiting, session handling. No third parties.

    Always on

No Umami measurement

Umami qualifies for the analytics exception and does not require consent, but you can opt out of being measured.