Paying for custom software in Singapore does not automatically give you copyright in the code. IPOS states that, in general, the author owns copyright—including when the work was commissioned—unless the parties agree otherwise in writing. For a Singapore buyer of custom build, an offshore development centre or a dedicated development team, the contract must separate foreground (project) IP, vendor background IP, open-source licence obligations that travel with the deliverables, and any licence-back / residual-knowledge rights the vendor keeps. Miss those four, and you can ship a product you cannot freely commercialise.
Educational only; not legal advice. Confirm assignment, licence and open-source compliance wording with Singapore counsel before you sign.
Who this is for, and who should skip it
For: Singapore CIOs, CTOs, heads of product, procurement and legal who are buying enterprise custom software, an ODC, a dedicated team, or an MVP and need a clear view of background IP, OSS and licence-backs before redlines.
Skip if: you need a full vendor due-diligence pack (PDPA, security and IP together)—see software vendor due diligence for Singapore; a SOW red-flag list for procurement—see custom software SOW red flags; or an offshore delivery contract checklist—see Singapore contract checklist for offshore software delivery. This article does one job: background IP × OSS × licence-back.
Foreground IP vs background IP (plain language)
Foreground (project) IP is what is created specifically for your engagement: application code, schemas, API contracts, UI assets, documentation and configuration written under your SOW. Buyers usually want this assigned (ownership transferred) or granted under an exclusive licence wide enough to run, modify, commercialise and sell the product.
Background IP is what the vendor already owned or later develops outside your project: frameworks, accelerators, internal libraries, templates, tooling and know-how. Vendors typically retain ownership and grant you a licence to use the background pieces embedded in the deliverables. That is normal. The risk is a carve-out so wide that your “foreground” is hollow—or a licence so narrow you cannot run the product after exit.
IPOS’s Ownership and Commercialisation guidance is clear on the commercial point: copyright can be assigned (sold) or licensed (leased); a written contract should set the nature and scope of the rights granted. Do not treat a purchase order or a Statement of Work as a substitute for that written grant.
Why commissioning software does not auto-assign copyright in Singapore
Under Singapore’s Copyright Act 2021, the default first owner of copyright is generally the maker/author of the work (see Division 8 — Ownership and transactions, including section 133 on SSO). A computer program is treated as a literary work under the Act. The limited “commissioner owns” rule in section 135 applies to photographs, portraits, engravings, sound recordings and films under agreements made before 21 November 2021—not to software you commission today.
IPOS summarises the practical rule: the person who created the work owns the copyright, including where they were paid (commissioned) to create it, subject to contract—the author and commissioner can agree in writing that someone else will own the copyright instead. For software, that means a Singapore buyer should obtain a written assignment of foreground IP or an exclusive licence with enough scope to operate and commercialise—then confirm the wording with counsel. Linking the live texts: IPOS Ownership and Commercialisation and the Copyright Act 2021 on Singapore Statutes Online.
Soft rule for buyers: if the contract is silent on assignment, assume the author (often the vendor or its developers) still holds copyright until you fix it in writing.
Open-source licence obligations that travel with deliverables
Almost every modern delivery includes open-source components. Those components keep their licences. Your product must comply with each dependency you ship, link or distribute. Ask for an inventory (ideally an SBOM) listing component name, version, SPDX licence identifier and how it is used (modified, linked, distributed, SaaS-only).
Educational licence families (examples from the OSI licence catalogue / SPDX licence list; always read the actual licence text):
| Family (educational) | Example SPDX IDs | What buyers usually watch |
|---|---|---|
| Permissive | MIT, Apache-2.0 | Notice/attribution; Apache-2.0 also has patent grant language—read the text |
| Weak copyleft | LGPL-3.0, MPL-2.0 | Source obligations often limited to the library/file; still check linking and modification rules |
| Strong copyleft | GPL-3.0 | Broader reciprocity when you distribute a combined work—treat as a product-architecture decision, not a paperwork afterthought |
No compliance percentage belongs in a sales deck. Know what you ship. Pair the SBOM with a policy: which families are pre-approved for your product shape (on-prem vs SaaS), who can add a strong-copyleft dependency, and what happens if one arrives without approval.
For escrow interaction, keep it light: escrow protects continuity of your source; it does not rewrite open-source licences or hand you ownership of vendor background IP. See software escrow for custom software buyers in Singapore when continuity is the separate risk.
Licence-back, residual knowledge and vendor reuse
Licence-back clauses let the vendor reuse project IP—or a broad residual of ideas and know-how—in other client work. Narrow ones allow generalised methods that do not disclose confidential information. Broad ones are a second ownership grab: the vendor assigns foreground IP to you, then takes a perpetual, royalty-free, transferable licence-back to use that same IP for any purpose, including competing products.
Residual knowledge clauses say individuals may retain in unaided memory general skills, experience and know-how. Reasonable residuals usually exclude your confidential information, trade secrets and unique business logic. Unreasonable ones blur into a free licence to rebuild your product elsewhere.
Negotiate to:
- Keep foreground assignment (or exclusive licence) intact without a broad licence-back that guts exclusivity.
- Limit residual knowledge to unaided memory of general skills—not your schemas, customer lists, pricing logic or unique workflows.
- Require subcontractor flow-down so freelancers and offshore entities cannot keep a wider reuse right than the prime vendor.
- Tie reuse to confidentiality and non-compete boundaries you already care about commercially.
Original element: Background IP × OSS × licence-back decision matrix
Score each row for the draft in front of you. Columns are actions, not vibes.
| Clause / risk area | Accept as-is | Negotiate | Walk-away triggers |
|---|---|---|---|
| Foreground IP assignment wording | Clear written assignment (or exclusive licence with run/modify/commercialise rights) of all project deliverables to the Singapore buyer entity | Add “present and future,” cover employees and contractors, require moral-rights waivers where counsel advises, name deliverable schedule | “All IP remains with vendor”; “licence for internal use only” on a product you must sell; silent SOW with no IP schedule |
| Background IP carve-out scope | Named pre-existing libraries/tools listed in a schedule; licence to use them as embedded in deliverables, surviving exit | Narrow carve-out to scheduled items; require disclosure of any background IP needed to run the product; irrevocable, royalty-free licence for that purpose | Catch-all “all frameworks, methods and know-how forever”; background IP undefined; run-time depends on undisclosed proprietary toolkit |
| OSS inventory / SBOM delivery | SBOM or equivalent inventory with SPDX IDs before each major release; update on material dependency change | Add delivery cadence, machine-readable format, and a right to audit licence notices in the repo | “We use OSS but won’t list it”; no SPDX IDs; refusal to discuss copyleft policy |
| Copyleft contamination risk for proprietary product | Vendor policy matches your distribution model; no new strong-copyleft deps without written approval | Pre-approve permissive/weak-copyleft lists; require notice before introducing GPL-family deps into distributed artefacts | Strong-copyleft already in your on-prem distribution path with no mitigation plan; vendor treats GPL as “fine for everything” |
| Licence-back breadth | None, or narrow reuse of generalised methods that exclude confidential information and unique business logic | Strike perpetual transferable licence-back of assigned foreground IP; limit to residual skills | Assignment plus broad licence-back that lets vendor commercialise your product IP elsewhere |
| Residual knowledge | Unaided memory of general skills/experience only; confidential information carved out | Define residual; exclude schemas, unique workflows, customer data, pricing logic | Residual that expressly allows reconstruction of your product from “memory” |
| Subcontractor / ODC flow-down | Written flow-down of assignment, confidentiality and OSS policy to every person who touches your code | Name Philippines/other delivery entities; require evidence of employee/contractor IP deeds | Prime assigns to you; subcontractors retain rights; no flow-down schedule |
| Escrow interaction (light touch) | Escrow (if used) covers your source and build instructions; separate from OSS and background-IP licences | Clarify escrow does not replace assignment or OSS compliance | Vendor offers escrow instead of IP assignment |
How to fill a cell: read the clause, underline the verbs (assign, licence, retain, reuse), and check whether your product can still ship after the vendor walks away.
Illustrative worked example (not a client case)
A Singapore B2B SaaS company hires a Philippines ODC under a Singapore master services agreement for a customer portal rebuild. The first draft says: vendor retains all IP; buyer gets a non-exclusive licence for internal use; vendor may reuse “all ideas, methods and residual knowledge” freely; OSS is “industry standard” with no inventory.
They apply the matrix. Foreground assignment is a Walk-away trigger. Background IP is undefined. OSS inventory is missing. Licence-back/residual language would let the ODC rebuild portal patterns for a competitor. Subcontractor flow-down is silent even though engineers sit in Manila.
Negotiation outcome (illustrative): foreground IP assigned to the Singapore buyer on payment of each milestone; background IP limited to a scheduled list of vendor accelerators with a perpetual licence to use them in the portal; SBOM with SPDX IDs at each release; no strong-copyleft deps without written approval; residual knowledge limited to unaided general skills; IP and confidentiality flow down to the Philippines delivery entity and named subcontractors. Escrow was deferred—continuity was a separate discussion, not a substitute for assignment.
Buy / not-yet / walk decision rule
Buy (sign the IP schedule) when: foreground assignment or exclusive licence is written and signed; background IP is scheduled with a usable licence; an OSS inventory/SBOM path exists; licence-back (if any) does not gut exclusivity; residuals exclude confidential information; and subcontractors are bound.
Not yet when: the SOW is priced but the IP schedule is blank; the vendor “will send the OSS list later”; or counsel has not reviewed assignment vs exclusive licence for your commercial model. Pause—use the Singapore software buyers pack to line up commercial and legal asks before the next redline round.
Walk when: the vendor refuses written assignment or a workable exclusive licence; background IP is a bottomless carve-out; OSS inventory is refused; or a licence-back lets them commercialise your foreground IP. Change vendor. Continuity tools such as escrow and knowledge-transfer / exit checklists do not repair missing ownership.
Mistakes that turn into expensive rewrites
- Assuming payment equals ownership. IPOS and the Copyright Act point the other way unless you agree otherwise in writing.
- Treating “work made for hire” language copied from another jurisdiction as enough. Use Singapore-appropriate assignment or exclusive-licence wording—confirm with counsel.
- Accepting a hollow assignment plus a broad licence-back. You “own” what the vendor can still freely reuse against you.
- Skipping the OSS inventory because the app is SaaS-only. Licence obligations still matter for distribution, employee devices, on-prem appliances and future M&A diligence.
- Ignoring subcontractor flow-down on an ODC. The engineer in Manila is where the copyright vests first if deeds are missing.
- Using escrow as a substitute for assignment. Escrow is continuity insurance, not a title deed.
- Leaving residuals undefined. “Know-how” without a confidential-information carve-out is a reuse blank cheque.
FAQs
Does a Singapore SOW automatically assign software copyright to the buyer?
No. IPOS states the author generally owns copyright even when commissioned, unless the parties agree otherwise in writing. Put assignment or an exclusive licence in the contract.
Are MIT and Apache-2.0 “safe” for every product?
They are permissive examples (SPDX: MIT, Apache-2.0), not a free pass. You still need attribution/notice compliance and a policy for how dependencies enter the repo. Read each licence text.
What should a licence-back clause look like if we accept one at all?
Narrow: generalised methods only, no confidential information, no right to commercialise your unique product IP. Prefer striking a broad licence-back of assigned foreground IP.
Do we need an SBOM for a Philippines ODC delivery?
You need a usable inventory of open-source components and licences—SBOM is the practical format many buyers request. Geography does not change the licence obligations that travel with the code.
What to do next
Pull the IP schedule from your live draft. Score it against the matrix. Fix foreground assignment, background carve-outs, OSS inventory and licence-back before you argue day rates. If the commercial model is still open, start from the Singapore software buyers pack and the pages for enterprise software development, ODC and dedicated teams—then bring counsel in for the final wording.
Related delivery: custom software in Singapore and software consulting for contract and codebase reviews. Start via contact if you want a red-flag review of ownership clauses.