Perpetual Subscriptions: Pay Once, Access Forever
Subscriptions do not have to renew to be useful. Perpetual Subscriptions give customers permanent access with a single purchase—no billing cycles, no renewals, no churn. Here is where they fit and where the model still has room to grow.
Sasank Ganapathiraju
Senior Software Engineer at Salable. Building the future of SaaS billing infrastructure.
The subscription economy taught software businesses to think in cycles. Monthly revenue, annual plans, churn rates, renewal reminders—the whole mental model of modern SaaS revolves around recurring billing. But not every software purchase fits that shape. Some customers want to buy something once, own it indefinitely, and never think about it again. Perpetual Subscriptions are how Salable supports that expectation without forcing you to build separate access infrastructure for the cases where recurring billing is the wrong tool.
What a Perpetual Subscription Is
A Perpetual Subscription is a subscription configured to run indefinitely. It carries entitlements, supports grantee groups, and participates in all the standard access control machinery—it simply never expires and never renews. The subscription stays active until you explicitly cancel it. There are no billing cycles to manage and no renewal dates to track.
A standard Perpetual Subscription goes through the standard Stripe checkout flow: the customer pays once and receives permanent access, with no further charges. A Salable Only Perpetual Subscription is created as a Salable Only Subscription configured as perpetual, granting indefinite access without the checkout process—useful for internal teams, partners, or goodwill access you want to persist without a billing relationship.
From your application's perspective, both look identical. Entitlement checks return the same result regardless of how the subscription was created or whether money changed hands. The customer's access is indistinguishable from someone on a monthly plan. The distinction is entirely in the lifecycle: one will renew next month, the other will still be active in ten years unless you act.
Where Perpetual Subscriptions Fit
Desktop Applications
Desktop software has a long tradition of perpetual licensing. A customer buys a version of an application, installs it, and uses it for as long as they choose without any ongoing obligation. The software works whether or not the vendor is still in business, and the customer's relationship with the product is defined by what they purchased on day one.
This model persists because it maps to how many customers think about desktop tools. A video editor, a CAD application, or a professional writing tool is more like a power drill than a streaming service—you buy it, it lives on your machine, and it does what it does. Many customers actively prefer this arrangement, particularly in professional contexts where budget approval is easier for capital expenditure than recurring operating costs.
Perpetual Subscriptions let you honour that preference without stepping outside your entitlement system. The customer pays once through your standard checkout flow, receives a Perpetual Subscription, and their access is established for life. If you want to offer upgrades to future major versions as separate purchases, you can cancel the old subscription and direct the customer through a new checkout. The model gives you flexibility without requiring you to build parallel access infrastructure for perpetual buyers.
Perpetual Licenses and Software Licensing
Enterprise software sales often involve formal licensing agreements with legal terms around what the customer can do with the software, how many seats they can use, and for how long. A perpetual license in this context is a contractual right to use a specific version of the software indefinitely, typically accompanied by a separate maintenance agreement that covers updates and support.
This structure has real advantages for enterprise procurement. Finance teams can capitalise the cost of a perpetual license as an asset rather than treating it as an operating expense. Legal teams have a clear, defined agreement with no automatic renewal clauses. Procurement has a single approval process rather than annual renewals that require re-justification.
Perpetual Subscriptions in Salable provide the access infrastructure for this arrangement. You handle the contractual side through your normal sales process. When the deal closes, you create a Perpetual Subscription with the appropriate plans, and the customer's access is active. If their maintenance agreement expires and you want to gate updates or new features, you can adjust their plans accordingly. The entitlement system reflects the commercial agreement without you having to build custom licensing logic.
Video Games
The games industry has its own version of perpetual access. When someone buys a game, they expect to own it—to be able to play it in five years without paying anything more. Base game access is almost universally perpetual in games, even when additional content is sold through subscriptions or one-off purchases.
This creates an interesting hybrid model. A player might buy the base game perpetually, subscribe to a season pass for ongoing content drops, and make individual purchases for cosmetic items. Each of those relationships has different billing characteristics, but all of them need to be reflected in the entitlement system that controls what the player can access.
Perpetual Subscriptions handle the base game access cleanly. The player pays once, gets a Perpetual Subscription covering base game entitlements, and that subscription never needs to be touched again unless they refund or violate terms of service. The subscription layer for ongoing content sits alongside it. The entitlement check that decides whether someone can enter a game session sees both subscriptions and grants access accordingly.
Where the Model Is Still Evolving
The use cases above share a common property: access is granted to a specific owner—a person or organisation—and the lifecycle never renews. Whether the subscription was created through a paid checkout or provisioned directly as a Salable Only Subscription, Salable handles these cases well today.
There are adjacent models where the full picture is more complex, and where we are still working to understand the best way to support them.
Transferable licenses are common in the desktop software world. When you sell a perpetual license for a professional tool, customers sometimes expect to be able to transfer that license to another person—reselling a purchased copy, or transferring it within an organisation when the original user moves roles. Today a Perpetual Subscription is tied to the owner who holds it. Transferring access requires cancelling one subscription and creating another, which works but loses the history of the original purchase.
Version-locked access reflects the fact that perpetual licenses in the enterprise world often cover a specific version of the software, not all future versions. A customer who bought a perpetual license for version 3 has not necessarily paid for version 4, even if their maintenance agreement provides upgrade rights. Expressing this constraint precisely within an entitlement system requires thinking carefully about how entitlements are structured across versions.
Reseller and distribution channels add another layer. Independent software vendors who sell through app stores, VAR partners, or retail channels often need to issue perpetual licenses that originate from a third party rather than the developer directly. The access infrastructure needs to connect the downstream purchase to the upstream entitlement system without requiring the customer to complete a first-party checkout.
These are patterns Salable is actively thinking about. The right solutions will emerge from working with developers who are building in these spaces, understanding the specific constraints they face, and iterating on the platform to address them. If any of these use cases describe your situation, we want to hear how you're approaching it.
The Shape of Access That Fits Your Customer
Subscriptions that renew are the right model for a lot of software. Ongoing access to a service, regular feature updates, support relationships—these all make sense as recurring billing. But the recurring model is not universally right, and insisting on it for customers who want to buy something once and own it creates friction that costs you sales.
Perpetual Subscriptions give you a way to meet those customers where they are. The access infrastructure is the same. The entitlement checks are the same. The difference is that you have matched the billing shape to what the customer actually wants—and that is usually worth doing.
Join the Community
A growing community of developers helping each other navigate SaaS monetisation and billing.
Related Posts
Introducing Salable Only Subscriptions: Access Without Payment
Not every access relationship starts with a transaction. Salable Only Subscriptions let you provision access for internal teams, partners, and beta testers using the same entitlement system your paying customers rely on—no checkout required.
Why Monthly Subscriptions Are a Bad Default
Monthly billing is the SaaS default because it's easy, not optimal. The right billing interval unlocks better cash flow and lower churn.
Implementing Board-Based Access Control in Miro
Miro users live in boards, so your plugin's access control should too. Scope subscriptions to boards, not individual users.