White Label

What Is Source Code Ownership and Why It Matters for White Label SaaS

Source code ownership rights in white label arrangements.

·7 min read
Source code ownership in white-label SaaS refers to the legal rights a buyer obtains over the underlying code when acquiring or licensing a resellable product. Without explicit transfer or perpetual license terms, the original developer can revoke access, alter pricing, or even shut down the product entirely.

Contract Language That Actually Transfers Rights

Most white-label deals are documented through an Asset Purchase Agreement (APA) or an exclusive perpetual license addendum. The APA should explicitly list “all source code, build scripts, database schemas, and third-party dependencies” as acquired assets. If the seller only grants a “non-exclusive, revocable license,” the buyer has no true ownership and cannot modify or resell the product without ongoing permission.

Valuation Impact on Acquisition Multiples

Platforms such as hades.ae, Acquire.com, and MicroAcquire consistently apply a 2–4× ARR multiple to white-label SaaS when full source-code ownership is conveyed. When rights are limited to a revocable license, multiples drop to 0.8–1.5× ARR. Empire Flippers and FE International both require sellers to upload the full Git repository and confirm no third-party code carries GPL or AGPL copyleft obligations before listing.

Operational and Legal Risks of Shared or Licensed Code

  • Churn risk: A 2025 survey of 180 white-label tools showed average monthly churn of 7.4 % when buyers lacked source-code rights versus 3.1 % when they owned the code outright.
  • Escrow dependency: Without ownership, buyers must rely on source-code escrow agents; release triggers can take 30–90 days and still require litigation to enforce.
  • IP indemnification: Sellers who retain copyright often refuse to indemnify buyers against infringement claims, leaving the new owner exposed to potential lawsuits.

Due-Diligence Checklist Before Closing

Run the following steps in order:

  1. Request the complete, buildable repository and confirm it compiles on a clean machine.
  2. Verify that every dependency license permits commercial redistribution.
  3. Obtain written assignment of all trademarks and domain names tied to the product.
  4. Confirm the APA contains a “further assurances” clause so the seller must execute any future documents needed to perfect title.
  5. Place 10–15 % of the purchase price in escrow for 12 months to cover undisclosed third-party claims.

What happens if the seller keeps partial rights?

The buyer cannot fork the product, change pricing tiers, or sell the business again without renegotiating terms—severely capping exit multiples.

How do acquirers typically confirm clean title?

They require the seller to deliver a signed Copyright Assignment Agreement recorded with the U.S. Copyright Office and a warranty that no open-source code carries restrictive licenses.

Does escrow replace the need for ownership?

No. Escrow only provides a conditional copy of the code; true ownership via APA or assignment gives unrestricted control and higher resale value.

Ready to acquire?

Browse curated digital platforms on hades.ae — every listing is built and owned by our team. View available platforms →