Source Code License Agreement Fully Paid-Up, Royalty Free Template

In plain language: Identifies both parties by legal name, describes the licensed source code, and defines all capitalized terms used throughout the agreement.

Common mistake: Describing the licensed source code too vaguely — e.g., 'all software created by Licensor.' Without a precise Exhibit A identifying specific repositories, file names, or version numbers, disputes arise over what was actually licensed.

In plain language: States the scope of rights conveyed — typically a perpetual, irrevocable, fully paid-up, royalty-free license to use, copy, modify, and distribute the source code — and whether the license is exclusive or non-exclusive.

Common mistake: Omitting 'irrevocable' from the grant. A fully paid-up license that can be revoked at will provides minimal commercial value — the licensee has paid in full but can lose access at any time.

In plain language: Defines exactly what the licensee may and may not do with the source code — including whether it may be sublicensed, embedded in commercial products, distributed to third parties, or reverse-engineered.

Common mistake: Failing to address sublicensing rights. If the licensee later sells their product to an acquirer, the acquirer needs rights to the embedded source code — silence on sublicensing creates a legal gap at the worst possible time.

In plain language: Confirms that the licensor retains all copyright, patent, and trade secret rights in the original source code, and addresses ownership of derivative works created by the licensee.

Common mistake: Leaving derivative work ownership unaddressed. If the licensee builds a product on top of the licensed code and the agreement is silent on who owns the derivative, both parties may have colorable claims — creating serious problems in any future M&A transaction.

In plain language: States the one-time license fee, the payment deadline, and confirms that no further royalties, maintenance fees, or usage-based charges are owed under the fully paid-up structure.

Common mistake: Not expressly stating 'no further fees are owed.' Without this language, a licensor may later argue that support, updates, or new versions require separate payment — undermining the fully paid-up structure the parties intended.

In plain language: The licensor represents that it owns or has authority to license the source code, that it does not infringe third-party IP rights, and that the code does not contain undisclosed malware or open-source components with conflicting license obligations.

Common mistake: Omitting the open-source component warranty. Embedded GPL or AGPL code can impose copyleft obligations on the licensee's entire codebase — a risk that only a specific warranty and a software composition analysis (SCA) scan can meaningfully address.

In plain language: Caps the licensor's total financial exposure — typically at the license fee paid — and excludes indirect, consequential, and punitive damages.

Common mistake: Setting no cap at all, or setting the cap at a nominal amount like $100 on a multi-million-dollar technology deal. Courts may enforce these clauses literally — leaving the injured party with no meaningful remedy for a material breach.

In plain language: For a fully paid-up license the term is typically perpetual, but the agreement should specify grounds for termination — e.g., material breach, insolvency — and what happens to the licensee's rights and existing derivative works if termination occurs.

Common mistake: Termination language that immediately voids derivative works already deployed in the licensee's products. A perpetual, fully paid-up structure should survive termination for existing derivative works — otherwise the licensee loses the benefit they paid for.

In plain language: Requires both parties to protect non-public information — including the source code itself — from disclosure to third parties, and specifies the standard of care and permitted disclosures.

Common mistake: No time limit on confidentiality for source code. Unlike general business information, source code may retain trade secret status indefinitely — but a five-year sunset clause in a boilerplate NDA can inadvertently allow disclosure of code still in active commercial use.

In plain language: Specifies the jurisdiction whose law governs the agreement and the mechanism for resolving disputes — arbitration, litigation, or a tiered negotiation-then-arbitration process.

Common mistake: No carve-out for injunctive relief. IP disputes involving ongoing use of misappropriated source code are exactly the scenario where a party needs emergency court relief — a mandatory arbitration clause without this carve-out can delay critical action for months.

A fully paid-up, royalty-free source code license grants the licensee the right to use, modify, and deploy identified source code in exchange for a single one-time payment, with no ongoing royalties, per-seat fees, or revenue-based charges owed. The licensor retains ownership of the underlying intellectual property, but the licensee's right to use the code is not contingent on any further payment. This structure is common in technology acquisitions, strategic partnerships, and enterprise software procurement where predictable, perpetual access is valued over variable licensing costs.

A software assignment permanently transfers ownership of the source code and all associated IP rights to the buyer — the original creator no longer owns it. A source code license grants usage rights while the licensor retains ownership. For a fully paid-up, royalty-free license, the practical day-to-day difference can be small, but the licensor retains the right to license the same code to others (if non-exclusive) and owns any improvements they make independently. Assignment is typically preferred when complete control over the IP is essential.

No — fully paid-up and royalty-free describe the payment structure, not the exclusivity scope. A fully paid-up license can be exclusive (only the licensee may use the code) or non-exclusive (the licensor can license the same code to multiple parties). Exclusive fully paid-up licenses command significantly higher one-time fees because the licensor foregoes all future licensing revenue from that code. The agreement must state explicitly which applies.

The primary risk is embedded open-source components with copyleft licenses — particularly GPL, LGPL, or AGPL — that impose obligations on the licensee's entire derived product, including mandatory disclosure of proprietary source code. Before signing, require the licensor to provide a software bill of materials (SBOM) and conduct an independent software composition analysis (SCA) scan using tools like FOSSA, Black Duck, or Snyk. The licensor should also warrant in the agreement that no conflicting open-source components are present.

It depends on the contract. A well-drafted fully paid-up license should be perpetual and irrevocable in normal circumstances, with termination only available for material breach or insolvency. Even where termination is permitted, the agreement should include a survival clause allowing the licensee to continue using derivative works already completed and deployed before termination. Without these protections, the licensee's significant upfront investment is exposed to forfeiture.

Both the licensor and the licensee must sign — typically authorized signatories of each legal entity (e.g., CEO, CTO, or a person with a board-delegated signing authority). If the IP is held in a subsidiary or SPV rather than the operating company, the IP-holding entity must be the named licensor and signatory. For transactions above $250K, consider having legal counsel review and confirm each party's signing authority before execution.

No — like all contracts, a source code license requires consideration to be enforceable. For a fully paid-up structure, the one-time license fee serves as consideration from the licensee; the grant of rights serves as consideration from the licensor. If the fee is nominal (e.g., $1), courts in some jurisdictions may scrutinize whether adequate consideration was exchanged, particularly in disputes involving large-scale commercial use. Set the license fee at a commercially reasonable amount reflecting the actual value of the rights granted.

For straightforward domestic licensing transactions under $100K with clear permitted uses, a high-quality template reviewed by a technology attorney for one to two hours is typically sufficient. Engage a lawyer for the full drafting or review process when the transaction value is material, the license is exclusive, the code will be embedded in a commercial product sold to third parties, there are international parties involved, or open-source component risk is significant. Technology IP attorneys typically charge $350–$700 per hour for license review.

This depends entirely on whether the license is assignable. Many source code licenses include anti-assignment clauses requiring licensor consent before the license can be transferred to an acquirer. In an asset purchase, the acquirer typically needs the license assigned to them — if consent is required and the licensor refuses or demands additional payment, the transaction can stall. When drafting the license, negotiate an express right to assign to a successor in connection with a merger, acquisition, or sale of substantially all assets, without requiring licensor consent.

An object code license grants rights only to the compiled, executable version of the software — the binary that runs on a computer but cannot easily be read, modified, or rebuilt. A source code license grants rights to the human-readable instructions, enabling the licensee to inspect, modify, compile, and build derivative products. Source code licenses are therefore far more valuable commercially and carry significantly greater IP risk for the licensor, which is why they command higher fees and more detailed contractual protections.