Perpetual License: What It Is and How to Sell One in 2026
A perpetual license is a software license you buy once and keep forever. There is no renewal date and no monthly bill for using it, though paid updates, support or hosted services can still run on their own terms.
You pay, you own the right to use that version of the software indefinitely.
For you as a buyer or seller, the practical questions are which version, updates and support the price covers, and whether recurring maintenance fits the product.
Here is what a perpetual license gives you, how it compares with subscriptions, and how you can sell one globally without managing tax registrations yourself.
TL;DR
- A perpetual license is a one-time purchase of the right to use a specific software version indefinitely.
- New major versions often require a paid upgrade. Included patches and support depend on the license terms.
- Perpetual licensing brings cash upfront. Subscriptions fund development through recurring payments.
- You can sell both: a perpetual base license and an optional recurring update plan.
- Creem supports both models as Merchant of Record, the legal seller responsible for collecting, filing and remitting VAT, GST and sales tax.
What is a perpetual license, and what does it include?
When someone buys a perpetual license, they are buying the right to use a specific version of your software for as long as they want. The key word is version. A perpetual license to version 4.2 does not automatically entitle the buyer to version 5.0.
This is where most of the confusion lives. Buyers assume "forever" means "forever, including everything you ship next year."
Smart sellers spell it out in the end-user license agreement (EULA), the contract that sets what the buyer may do with the software. A clean one defines:
- The version covered (often the current major version at purchase).
- What updates are included (bug fixes and minor patches typically yes, new major versions typically no).
- Support terms (how long you will answer tickets, and whether that support is time-limited).
- Who can use it (one named user, a set number of seats, or a set number of installations).
- Activation limits (how many devices one license key can activate, and whether activation needs an online check).
- Transfer rights (whether the buyer can move the license to a new machine or hand it to another company).
- Online dependencies (any account login, sync or hosted service the software needs to run).
- Maintenance price and renewal (what a year of updates and support costs after the first, and what lapsing changes).
Your product page, the order confirmation and the EULA should state the same duration, version, installation rights, support period and upgrade terms.
When those three disagree, buyers will quote the friendliest one back at you.
A perpetual license is a legal permission to keep using the software. It does not promise the software will run on a future operating system.
It also does not keep a hosted service online. If the product calls your servers, say in the EULA what happens when that service changes or closes.
JetBrains built a well-known hybrid around exactly this. Its perpetual fallback license lets subscribers keep a working version of the software if they stop paying.
Buying an annual subscription qualifies right away. On monthly billing, you qualify after 12 consecutive monthly payments.
The fallback covers the major version available at the start of the qualifying period, its minor releases and older versions. Continued subscription payments can advance the fallback version.
It is a subscription on the surface with a perpetual safety net underneath, and it exists because buyers hate the idea of losing access to a tool they depend on.
Perpetual license vs subscription: revenue and buyer tradeoffs
The subscription model won the last decade for good reasons. Recurring revenue is predictable and compounds when customers stay and new ones keep arriving. Investors pay higher multiples for that recurring base, and renewals keep funding development.
But it is not automatically the right call for every product.
Here is the honest breakdown.
| Perpetual license | Annual (term) license | Subscription | |
|---|---|---|---|
| Payment shape | One larger upfront payment | One payment per term | Recurring monthly or annual payments |
| Development funding | Upfront, then new sales, upgrades or maintenance | Renewal each term | Continues while customers stay subscribed |
| Updates and support | Included patches and support depend on the agreement, with more available through paid maintenance | Included for the term, per agreement | Usually included while subscribed |
| Right to use after payments stop | Keeps the licensed version | Ends at term expiry | Access ends when the paid term ends |
| Adding seats | Buy another license | Per agreement | Per plan terms |
| Buyer relationship | No renewal, suits buyers wary of recurring costs or bound by procurement rules | A renewal decision each term | A relationship you keep earning |
An annual license grants use for a set period, usually a year, and the right to use ends at expiry under the agreement. Annual describes duration and subscription describes billing, so one product can be both.
That differs from a perpetual license with yearly maintenance. If maintenance lapses there, only updates and support stop.
The math matters. A $200 perpetual license is a single event, while a $15 per month subscription brings in $210 in cumulative revenue after 14 paid months, before taxes, payment fees and the cost of serving the customer.
If your customers stick around for years, subscriptions usually win on total revenue. If they buy, use the tool, and rarely need the newest features, a perpetual license can capture value you would otherwise leave on the table.
Adobe is the classic cautionary tale in reverse. When it moved Creative Suite from perpetual licenses to Creative Cloud subscriptions in 2013, there was loud backlash.
Adobe's whole-company revenue grew from $4.06 billion in fiscal 2013 to $15.79 billion in fiscal 2021.
The lesson: subscription or perpetual licensing has to match your product and your buyers. Subscriptions do not always win.
When a perpetual license is the right move
Perpetual licensing tends to work best in a few specific situations.
- Your product is stable. Your software does one job well and does not need constant updates. Think a niche desktop utility, a font, a plugin, or a one-off tool. When buyers need no ongoing service, they often just want the thing.
- Your buyers have procurement rules. Some organizations genuinely find it easier to approve a single capital purchase than an ongoing subscription line item.
- Your buyers want to pay once. Developers and prosumers tired of subscription fatigue often pick the tool that lets them pay once, and they talk about it.
- You want a strong launch spike. A perpetual license, sometimes with lifetime deal pricing, can generate a wall of cash on day one. Just be careful: if the deal promises lifetime updates, support or hosted services, a one-time payment now funds costs that keep running. Say whose lifetime you mean (the product's or the major version's) and list exactly what the deal includes.
- You sell self-hosted software to enterprises. Buyers who run software on their own servers want control over their infrastructure and data, and a perpetual license fits that where your product supports it. Any hosted service you run for them still costs you every month, which usually favors recurring billing.
How to sell a perpetual license globally without the tax mess
Here is the part nobody warns you about. Digital products, software included, are taxable in most of the world. Perpetual or subscription, it does not matter.
Whether you personally have to register and collect that tax is a separate question, and each country answers it with its own rules.
- The EU wants VAT on digital sales to EU consumers. If you are based outside the EU, that starts with the very first euro of electronic-service sales to consumers, with no threshold.
- If you are established in only one EU country, you can charge your home VAT on cross-border consumer sales while the EU-wide total of those sales and your distance sales of goods stays at or under €10,000 a year. That limit has to hold for both the current and the previous calendar year.
- Past that limit, the EU's cross-border VAT rules switch you to VAT in each buyer's country.
- The UK wants its own VAT.
- Canada has GST/HST plus provincial rules.
- In the US, each state decides whether digital goods are taxable and when a remote seller has to register, file and remit. Software can be taxable even where other digital goods are exempt.
If you sell from outside the EU, a $200 license sold to a consumer in Germany obligates you to collect and remit German VAT. An EU seller past the €10,000 limit is in the same position.
You have two ways to handle this.
- Option one: become the seller of record yourself. Register for VAT and sales tax wherever the local rules require it, from the first sale in some places and past a threshold in others.
Then collect the right rate on every sale, file returns on different schedules, and keep up as rules change. This is doable, and it is also a real job. Most small software businesses do not have a tax team.
- Option two: use a Merchant of Record. An MoR becomes the legal reseller of your product.
They take on the sale, which means they are the ones responsible for calculating, collecting, and remitting sales tax and VAT on those sales worldwide.
You get paid, and you keep your own business-income taxes plus the work of building, delivering and supporting the software.
This is exactly what Creem does. You sell your software, perpetual or subscription, and Creem is the Merchant of Record.
Tax calculation, collection, and remittance for buyers in 190+ countries, including 28+ US states, are handled for you. Creem also handles fraud protection and payouts, and seller onboarding and payouts cover 87 countries.
On Creem's standard plan, you pay 3.9% + 40¢ per successful transaction, with no monthly fee and no setup fee. A $200 perpetual license leaves $191.80 after that fee, before any optional-feature or payout fees.
Run your own order sizes through the pricing calculator before you launch. Included services, optional charges and payout timing break down as follows:
- Included in the rate: tax handling, invoicing, fraud screening and dispute handling.
- Optional features: affiliates and revenue splits each add 2% before commission. Recovered carts add 5% on the recovered amount.
- Payout fees: payout transfer costs apply, with currency conversion charges if your bank currency differs.
- Payout timing: a payment can be held for 7 to 12 days before it reaches your available balance. Payouts are processed on the 1st and 15th once that balance is at least 50 USD or 50 EUR. Arrival depends on the payout method.
Buyers can pay by card, PayPal, Apple Pay or Google Pay in their own currency, on a checkout that can run on your own domain or embed on your site.
The best part is that the model is license-agnostic. Creem supports one-time payments for perpetual licenses and recurring billing for subscriptions in the same account. If you want to sell a perpetual base license and layer on an optional paid update plan, you can run both through one checkout.
DaisyUI moved to Creem in a few hours, with support replies within a day and zero extra tools needed for profit sharing. Its collaborators receive their share automatically instead of waiting for manual transfers.
Setting up a perpetual license on Creem comes down to four steps:
-
Write down what the price covers. Name the version, the number of devices it installs on, which updates come with it and how long support lasts.
Anything beyond that, such as the next major version, can be sold as a separate upgrade or included in a maintenance plan.
-
Create the one-time product, then the optional maintenance plan. The license is a one-time payment. Maintenance is its own recurring product, so a customer can drop it without touching the license.
Each successful charge pays the standard fee on its own. For example, a $50 yearly maintenance renewal leaves $47.65 after the standard transaction fee.
-
Turn on license keys and file delivery.
Enable License Key Management and File Downloads on the product, set the activation limit, and leave the key's expiration empty for a perpetual grant.
Creem issues a key with each purchase and tracks its activations. Your app activates the key on first launch through the API, validates it to read its status and activations, and deactivates a device when the customer moves machines.
-
Run a full test purchase before launch.
In test mode, confirm the key shows on the confirmation page, in the receipt email and in the customer portal, and that the download link works.
Activate, validate and deactivate the key, then activate it again on a second device.
Finally, cancel the maintenance plan. The base license should keep working, and your terms should name the last version included, whether earlier downloads stay available, when support ends and how the customer can rejoin. Which versions a key grants access to after cancellation is logic you build in your app.
Once the test purchase and the second-device activation both pass, try Creem and put the license on sale. Each real buyer then gets their key the moment they pay.
Sell your software your way, and let someone else handle the tax
Perpetual or subscription is a product decision, and only you know your buyers well enough to make it. Pick the model that fits how people actually use and pay for your software. Do not copy the SaaS crowd just because subscriptions are fashionable.
Whatever you choose, Creem can be the legal seller that collects, files and remits VAT, GST and sales tax. It also issues license keys with activation limits and delivers files through email and the customer portal.
For a SaaS or AI product with a perpetual desktop or self-hosted tier, Creem keeps license sales, subscriptions, seats and prepaid credits in the same store. Affiliates and licensors can receive their share automatically as customers pay for the software and its ongoing usage.
Start selling globally with Creem and see the pricing before you launch your next license.
FAQ
Is a perpetual license the same as a lifetime license?
Not quite. A perpetual license means you can use a specific version forever. A lifetime license often promises future updates too, but only the agreement decides which versions and services are covered and what "lifetime" means.
Do perpetual licenses include updates?
Usually only minor updates and bug fixes for the version you bought. New major versions typically require a paid upgrade or a separate maintenance plan. Always state this clearly at purchase.
Is perpetual licensing dead?
No. Subscriptions dominate SaaS, but perpetual licensing is alive and well for desktop apps, plugins, utilities, fonts, and tools sold to buyers who prefer a one-time purchase. Many companies offer both.
Can I switch from perpetual to subscription later?
Yes, and many do. The safest approach is to grandfather existing perpetual customers and introduce subscriptions for new features or new tiers, rather than forcing everyone onto a recurring plan overnight.
Licenses you already sold keep their rights, with no renewal attached.
Can a perpetual license be terminated?
Yes, if the agreement allows it. A perpetual license has no scheduled end date, but the termination terms in your EULA and the applicable law decide whether and when it can end.
Do I need to charge sales tax on a perpetual license?
Often, yes. Digital products are taxable across the EU, the UK, Canada and in US states that tax software. Your obligation depends on the buyer's location, the product's tax classification and the applicable registration rules.
Using a Merchant of Record like Creem takes that burden off you, because Creem is the legal seller and collects, files, and remits the sales tax and VAT on each sale.
