Software Licensing

How it works

Copyright in software attaches automatically the moment code is written; no registration is required for the protection to exist. The licence agreement is what defines legitimate use, and stepping outside its terms is often infringement of copyright rather than a mere breach of contract, which changes the remedies available to the licensor.

Perpetual licensing sells the right to run a given version indefinitely, bundled with an annual maintenance and support fee that pays for updates and bug fixes. The one-time licence fee is not the recurring income; the maintenance line is, and it is what turns a single sale into a multi-year revenue stream. Subscription licensing dispenses with the perpetual grant entirely, charging per user, per device, per core or per environment on a recurring term, with access terminating the moment payment stops. Consumption pricing goes further and meters an actual activity, such as API calls, transactions processed or gigabytes stored, billing in arrears so revenue moves in step with the customer's own volume.

Embedded or original-equipment royalties sit closest to a classic royalty arrangement: a hardware maker or another software vendor ships the licensor's component inside its own product and pays a fee per unit shipped, typically reported by the partner and subject to periodic audit. White-label and reseller deals let a partner sell under its own brand at a wholesale rate, trading margin for reach the licensor could not build alone. Dual licensing offers the identical code base free under a copyleft open-source licence and for a fee under commercial terms, aimed at companies unwilling to accept copyleft obligations.

App stores and platform marketplaces impose a defined revenue share and control pricing mechanics, refund policy and listing eligibility. Compliance across all these models is enforced with licence keys, telemetry and contractual audit rights, and enterprise licence audits are a standard, budgeted revenue-recovery mechanism in the industry. Enterprise buyers commonly require source-code escrow, so they can obtain the code from a neutral third party if the vendor fails or stops maintaining the product.

What it pays

Pricing is quoted per seat, per core, per device, per unit shipped, or per unit of metered consumption, with a maintenance percentage of licence value layered on top of perpetual deals. What moves the number is the count of users or units in place, the customer's own growth in metered arrangements, renewal and expansion rates at contract time, and how deeply the software has become embedded in the customer's workflow — deep embedding raises switching costs and supports price increases.

Embedded royalties scale with the partner's hardware or product shipment volumes, a variable entirely outside the licensor's control; a slowdown in the partner's end market lowers royalty income with no action by the licensor.

Recurring revenue commands a premium over one-off licence sales because it is measurable, forecastable and renewable, which is why the industry broadly shifted from perpetual licences toward subscription and consumption pricing. Free-tier and open-core models generate no direct income from the large majority of users; the entire revenue line depends on the smaller share that need the commercial licence or paid features, so conversion rate matters more than total user count. On app-store distribution, the platform's revenue share is deducted before the developer sees any proceeds, which sets a hard ceiling on realized take-rate regardless of list price.

Costs and taxes

Keeping a licence sellable requires continued engineering: security patching, operating-system and dependency upgrades, and compatibility work do not stop once the product ships. Support obligations written into the maintenance agreement create ongoing staffing costs and, often, service-level exposure with financial penalties for missed response times. Anything delivered as a service carries hosting and infrastructure costs that scale with usage, and licence-compliance tooling, legal review of enterprise agreements, and open-source licence auditing are recurring line items rather than one-time setup costs.

US tax treatment depends on who is earning the income and how. Licence revenue earned inside an operating business is ordinary business income, reported on the entity's own return. An individual who licenses software without carrying on a trade or business generally reports the income as royalties on Schedule E, while someone in the business of developing and licensing software reports on Schedule C or through their entity instead.

Cross-border payments raise a separate question: whether the payment is for a transfer of copyright rights or merely a transfer of a copy. US tax regulations distinguish the two, and the answer determines foreign withholding treatment on the payment. Separately, state sales tax increasingly reaches prewritten software and software as a service, with the rules varying widely by state and changing as legislatures catch up to how software is actually delivered.

Liquidity and time commitment

Small software businesses and standalone code assets do trade, on marketplaces and through brokers, priced off recurring revenue and churn much like a small operating business. A sale is nonetheless a diligence-heavy process measured in months, not days, and buyers scrutinize customer concentration, code quality and contractual obligations before closing. Predictable, contracted licence revenue is sometimes financed against directly, since lenders treat recurring revenue as lendable collateral in a way one-off sales are not.

For a solo developer, the capital investment is engineering time rather than cash, which makes the entry cost low in dollar terms but high in hours. The work is rarely passive in any of these models: customers expect support, security disclosures require a timely response, and an unpatched dependency left unaddressed can end the business outright. Embedded royalty deals are the least demanding of the group once integration work is complete, since the partner owns the end-customer relationship and the licensor mainly collects and verifies royalty statements.

How it goes wrong

A capable open-source alternative can appear and remove the commercial product's reason to exist, particularly where the paid version offered convenience rather than unique capability. Revenue can also concentrate in a small number of enterprise customers, so a single non-renewal removes a large share of income in one event rather than gradually.

Codebases accumulate dependencies over time, and an open-source component carrying a copyleft licence can be pulled in inadvertently, creating obligations that conflict with the commercial licence being sold and forcing costly remediation. Distribution risk sits with the platform: an app store or marketplace can change its rules, its revenue share or its eligibility criteria, and a sales channel can disappear overnight with no negotiation.

Licence terms that are unclear about virtualization, containers or multiplexing let customers legitimately run far more workload than the licence was priced for, eroding revenue without any breach occurring. A security vulnerability can force emergency engineering work at the vendor's expense and damage the customer relationship enough to prevent renewal.

If the product stops being actively maintained, enterprise customers can invoke source-code escrow or simply leave at the next renewal date. In embedded royalty arrangements, under-reporting by the partner is a recurring risk, discoverable only through an audit that the licensor itself must fund and pursue.