TRW & Co · Technology, IP & Data
Software Licensing in Singapore
Software licensing in Singapore decides who may install, run, copy and distribute software, and what happens when usage exceeds what was bought. Licences combine contract and copyright, so non-compliance can be both breach and infringement. This guide explains the legal foundation, licence models, audits, open source and AI model terms, and how to structure your own licences in 2026.
Key pointMost licence shortfalls arise not from copying but from how usage is measured after a change in infrastructure, such as virtualisation, cloud migration or system integrations. Ask vendors how their metrics apply before you move, not after the audit letter arrives.
At a glance
Code is a literary work
Computer programs are protected as literary works under the Copyright Act 2021 automatically on creation; Singapore has no copyright registration system.
Licence, not sale
The licensor keeps ownership and grants defined rights; use beyond scope can be both breach of contract and copyright infringement, with injunctions and damages available.
Some uses are protected
The Copyright Act 2021 sets out permitted uses for computer programs, such as back-up copies and interoperability, some of which cannot be excluded by contract.
Audits follow change
Cloud migrations, virtualisation, integrations and acquisitions are the usual triggers for vendor audits and back-dated licence claims.
Withholding tax may apply
Payments to non-resident licensors may be royalties subject to withholding tax, while payments for software for the payer’s own use are generally treated differently.
Swipe or scroll →
What software licensing in Singapore covers
Software licensing in Singapore is the body of contract and copyright law that decides who may install, run, copy, modify and distribute software, and on what terms. Almost every business is a licensee many times over, and every software company is a licensor whose revenue depends on its licence terms being enforceable.
A licence is permission, not a sale. The licensor keeps ownership of the copyright and grants defined rights, limited by scope, metric, territory, term and purpose. Anything outside those limits may be both a breach of contract and an infringement of copyright. That dual exposure is what gives software audits their bite.
Licensing questions become urgent at specific moments: a vendor audit letter, a migration from on-premise servers to the cloud, a merger that moves software between entities, a product launch that embeds third-party or open source code, or a dispute over whether a perpetual licence survives a vendor's acquisition.
The copyright foundation
Computer programs, including source and object code, are protected as literary works under the Copyright Act 2021. Protection arises automatically when the work is created; there is no registration system for copyright in Singapore, and, as IPOS notes, the copyright symbol is merely a notice and adds no rights.
The owner has exclusive rights to reproduce, publish, communicate to the public and adapt the work. Running software usually involves making copies in memory, which is why use itself needs permission. A licence is the instrument that grants that permission.
Permitted uses without a licence
The Act also sets out limited permitted uses for computer programs, such as making back-up copies and certain acts needed for interoperability or to correct errors, each subject to conditions. Some permitted uses cannot be excluded by contract. Licensees should not rely on them as a general substitute for licence rights, but they matter when a licence is silent or a vendor takes an aggressive position on reverse engineering.
Ownership and the chain of title
A licensor can only license what it owns or is entitled to sublicense. Employers generally own code written by employees in the course of employment, but the author of a commissioned work generally owns it unless agreed otherwise in writing, as IPOS explains. Licensees taking strategic licences, and investors in software companies, should ask how the licensor acquired its rights. Our page on technology transactions covers chain-of-title diligence.
Licence models and metrics
The commercial model drives the legal risk. Licensees most often fall out of compliance not by copying software illegally but by misunderstanding how usage is measured.
| Model | How it is measured | Typical compliance risk |
|---|---|---|
| Perpetual licence with maintenance | One-off fee per user, device or processor, plus annual support | Losing upgrade rights when support lapses; re-instatement fees |
| Term or subscription licence | Periodic fee for a defined period | Continued use after expiry; auto-renewal surprises |
| Named or concurrent user | Individuals authorised, or simultaneous users | Shared accounts; indirect access through other systems |
| Processor or core-based | Hardware capacity where software runs | Virtualisation and cloud deployment multiplying the count |
| Enterprise agreement | Organisation-wide entitlement with periodic true-up | Definition of affiliates; divestments and acquisitions |
| OEM and embedded | Per unit of a product that includes the software | Distribution outside the permitted channel or territory |
| Open source | Licence conditions rather than fees | Copyleft obligations; missing notices and attributions |
The last row deserves emphasis. Open source licences are copyright licences with conditions, and breach of the conditions can end the permission. Permissive licences mainly require notices; copyleft licences may require you to release source code for derivative works you distribute.
Choosing a model as a licensee
The cheapest model on paper is not always the cheapest over the life of the software. Perpetual licences look attractive for stable, long-lived systems, but the maintenance fee, typically recurring every year, often exceeds the original licence cost within a few years. Subscriptions shift spend to operating budgets and bundle upgrades, but leave you with nothing if you stop paying.
Enterprise agreements simplify administration for large groups, yet their true-up mechanisms can lock in growth assumptions that no longer hold after a divestment. Before committing, model the total cost under realistic scenarios, including acquisitions, disposals, headcount changes and infrastructure moves. Good software licensing in Singapore starts with that model, because it shows which contract terms carry real money.
The licence terms that matter most
Whether you are licensing in or licensing out, a small number of clauses do most of the work. Reviewing these first gives a reliable picture of the deal in an hour.
Grant and scope
Who may use the software (the licensee alone, or affiliates and contractors), for what purpose, in which territory and on what infrastructure. A grant limited to "internal business purposes" may exclude service bureau or customer-facing use.
Usage metric and definitions
How users, devices, cores or transactions are counted, including indirect or multiplexed access. Definitions decide audit outcomes, so negotiate them before signature.
Audit rights
Notice period, frequency, who conducts the audit, confidentiality, cost allocation and the pricing of any shortfall. Without limits, audits become a sales tool.
Transfer and change of control
Whether licences can move to a buyer in an asset sale, to group companies after a reorganisation, or survive a change of control of the licensee.
Warranties and IP indemnity
Performance warranties for a defined period and an indemnity against third-party infringement claims, with control of defence and remedies such as modifying or replacing the software.
Termination and survival
When the licensor may terminate, whether perpetual licences survive termination of support, and what happens to data and copies at the end.
Exclusion and limitation clauses in standard licence terms are subject to the reasonableness test in the Unfair Contract Terms Act 1977, and click-through licences are binding under the Electronic Transactions Act 2010 if properly presented. Our article on SaaS agreements covers subscription terms in more depth.
Handling a software audit
Audit letters are a predictable part of software licensing in Singapore, particularly after cloud migrations or corporate transactions. The response determines whether an audit ends with a modest true-up or a large claim for back-dated fees.
- Check the contractual basis. Read the audit clause in the governing agreement: notice, scope, frequency, who may audit and what data you must provide. Many requests exceed what the contract allows.
- Appoint a single point of contact. Route all communications through one person, with legal oversight. Uncoordinated replies from IT staff are a common source of damaging admissions.
- Agree scope and confidentiality. Settle in writing which entities, products and periods are in scope, the tools to be used and how the auditor will treat your data.
- Run your own baseline first. Establish your entitlements and deployment internally before sharing data, so you understand the position and can correct errors in the auditor's analysis.
- Challenge the findings. Test the licensor's assumptions on metrics, virtualisation, indirect access and archived installations against the contract definitions.
- Negotiate the outcome. Most audits settle commercially. Negotiate the price of any shortfall, waiver of back-support and penalties, and a release for the audited period, recorded in a settlement agreement.
An audit is a contract question before it is a counting exercise. Start with what the agreement actually permits the licensor to ask.
Before migrating workloads to a public cloud or a new virtualisation platform, ask each major vendor in writing how its metrics apply to the new environment. Licence terms written for physical servers can multiply the required entitlement many times over once software runs in a virtualised or cloud cluster.
Licensing out: structuring your own terms
For software companies, licence terms are a product feature. They must protect the code, support the revenue model, and be acceptable to the customers you want to sell to, including regulated customers with mandatory contract requirements.
Start with tiered templates: click-through terms for self-service customers, a negotiated master agreement for enterprise customers, and a reseller or OEM agreement for channel partners. Align definitions across all three so that a customer moving up a tier does not find inconsistent rights. Our distribution and agency team handles channel structures.
Protect the code by limiting reverse engineering to what the law permits, restricting use in competing products, keeping source code confidential and registering trade marks for product names. Confidentiality and trade secret protection matter for algorithms and models that copyright does not fully cover; see our trade secrets page.
Regulated customers will often ask for clauses that a standard licence does not contain. Financial institutions may need audit and access rights for their regulator, notice of material subcontracting, business continuity commitments and cooperation in incident reporting. Healthcare and public-sector customers may require data to stay in Singapore. Anticipating these requests in an enterprise schedule shortens sales cycles and avoids conceding them one negotiation at a time.
Price-change and renewal terms deserve equal care. Customers increasingly resist uncapped renewal increases, and unilateral changes to online terms can be challenged if they are not properly notified. A clear renewal mechanism, with notice and a cap or a benchmark, tends to protect recurring revenue better than an aggressive clause that customers later dispute.
Licensing AI models and datasets
AI models and training datasets are increasingly licensed separately from applications. Model licences often include acceptable use policies and restrictions on using outputs to train competing models. Datasets raise copyright and personal data questions at the same time. The Copyright Act 2021 includes a computational data analysis exception with conditions, including lawful access to the source material, and its interaction with licence restrictions needs careful analysis. Our AI governance page covers the wider regulatory picture.
Documents and records to keep
Compliance with software licensing in Singapore is proved by records, not assertions. When an auditor or counterparty challenges your position, the organisation with complete documents usually prevails. Keep the following, centrally and in a form that survives staff turnover.
- Proof of entitlement: signed agreements, order forms, invoices and licence certificates, linked to the legal entity that bought them.
- The governing terms: a dated copy of the terms in force when each licence was bought, because online terms change and the vendor's current version may be less favourable.
- Deployment records: output from software asset management tools showing installations, users and hardware, including virtual and cloud environments.
- Change history: records of infrastructure changes, mergers, disposals and reorganisations that affect where software runs or which entity uses it.
- Vendor correspondence: written confirmations on how metrics apply, consents to transfer and any agreed waivers.
- Open source register: components, licences, versions and the obligations each imposes.
Assign ownership of this file to a named person in procurement or IT asset management, with legal oversight. Review it before each renewal and before any major infrastructure project, so that licensing questions are raised while there is still time to negotiate.
Risks and common mistakes
Indirect access through integrations
Some licensors count users who access their software indirectly, for example through a web portal, a robotic process automation tool or an integration with another system. Organisations that licensed a small number of named users can find themselves facing claims based on every customer or employee whose request touched the system. Map how data flows between licensed systems, check the contract definitions of user and access, and negotiate explicit treatment of integrations and automation before deploying them at scale.
Moving licences in a corporate transaction
In an asset purchase or carve-out, software licences do not automatically transfer to the buyer, and many prohibit assignment without consent. Transitional services agreements, where the seller keeps running systems for the buyer, may also breach licence scope if the seller's licences are limited to its own internal use. Identify critical licences early in the deal, approach vendors for consent with a plan, and budget for new licences where consent is refused or priced high.
Copyleft obligations in distributed products
Incorporating code under a strong copyleft licence into software you distribute to customers can oblige you to make the corresponding source code of the combined work available under the same licence. The trigger often depends on how the components are combined and whether the software is distributed or only provided as a service. Run software composition analysis, keep a register of components and licences, and set an internal policy on which licences are approved for which uses.
Using lapsed or wrongly scoped licences
Continuing to use software after a subscription ends, or deploying it outside the permitted entity, territory or purpose, may be infringement as well as breach of contract. Remedies for copyright infringement can include damages or an account of profits and injunctions, and wilful commercial-scale infringement can be a criminal offence. IPOS's guidance on infringement summarises the options. Keep a central licence register with renewal dates, scope limits and responsible owners.
Ignoring withholding tax on licence fees
Payments to non-resident licensors may be subject to Singapore withholding tax if they are royalties, which affects both the payer's compliance and the commercial price. IRAS distinguishes between payments for the right to exploit copyright and payments for software for the payer's own use, which are generally not treated as royalties. Characterise each payment stream, agree who bears any withholding and whether there is a gross-up, and check the relevant tax treaty. See our double tax treaty page.
Cross-border licensing: Bangladesh, the UK, UAE, China and ASEAN
Software licensing in Singapore often sits within a regional or global structure, with a Singapore entity holding IP and licensing it to affiliates or customers across Asia. That structure must work under each local law, not only Singapore's.
Where a Singapore company licenses software to customers or affiliates in Bangladesh, local foreign exchange and tax rules affect how licence fees can be remitted, and documentation may be needed for banks to process payments. In China, licences of technology into and out of the country can engage technology import and export rules, and data used by the software may face transfer restrictions.
The UK and UAE generally respect freedom of contract in software licensing, but UK competition law, consumer protection rules and the UAE's onshore and free-zone frameworks each add local requirements. Across ASEAN, enforceability of click-through terms, language requirements and consumer protection rules vary. Through TRW's offices and network, we coordinate local review so a single template can be used with country-specific schedules.
How TRW & Co helps with software licensing in Singapore
We act for licensees and licensors, from start-ups to regional groups. Where Singapore court or tribunal representation is required, we work alongside Singapore-qualified counsel.
Licence review and negotiation
We review enterprise agreements and order forms, negotiate metrics, audit clauses and transfer rights, and set up playbooks for repeat procurement.
Audit defence
We manage audit correspondence, test findings against contract definitions and negotiate settlements with releases, working with licence consultants where useful.
Licensing-out programmes
We draft tiered licence and SaaS terms, reseller and OEM agreements, open source policies and AI model licences for software businesses.
Enforcement and disputes
We assess infringement and breach claims, coordinate evidence and work with Singapore counsel on IP litigation where proceedings are needed.
See our practices for related areas, read our note on software copyright, or contact us about a specific licence or audit.
Checklist for decision-makers
- Do we have a central register of software licences, entitlements, renewal dates and scope limits?
- Have we checked how each major vendor's metrics apply to virtualised and cloud environments?
- Do our audit clauses limit frequency, scope, notice and the pricing of any shortfall?
- Can critical licences move with the business in a sale, reorganisation or change of control?
- Do we know which open source licences are in our products, and do we comply with their conditions?
- If we license out, are our templates aligned across self-service, enterprise and channel tiers?
- Is the tax treatment of cross-border licence payments settled, including withholding and gross-up?
Organisations that can answer these questions confidently spend less on software, survive audits with fewer surprises and get more value from software licensing in Singapore, whether they are buying or selling.
Frequently asked questions
01Is a perpetual licence really forever?
A perpetual licence usually lets you use the version you bought indefinitely, provided you stay within its scope and do not breach terms that allow termination. It does not guarantee support, security patches or upgrades, which normally depend on paying annual maintenance. If support lapses, reinstating it can be expensive, and running unsupported software may create security and regulatory problems. Check whether the licence survives termination of the support agreement, whether it can be transferred, and what happens if the vendor is acquired or discontinues the product.
02Can we reverse engineer software we have licensed?
Only within limits. Many licences prohibit reverse engineering, decompilation and modification. The Copyright Act 2021 permits certain acts in relation to computer programs, for example for interoperability, subject to strict conditions, and some permitted uses cannot be excluded by contract. These exceptions are narrow and fact-specific. Before reverse engineering, take advice on whether the specific activity falls within a permitted use, record the purpose, and avoid using the results for anything beyond that purpose, particularly building a competing product.
03What should we do when we receive an audit letter?
Do not ignore it, and do not respond in detail immediately. Check the audit clause in the contract, appoint one point of contact with legal oversight, and agree scope, timing and confidentiality in writing. Establish your own entitlement and deployment position before sharing data. Test the auditor’s findings against contract definitions, especially on virtualisation and indirect access. Most audits are resolved by negotiated settlements, which should include a release for the audited period and agreed pricing for any additional licences.
04Do open source licences create legal obligations?
Yes. Open source licences are copyright licences with conditions. Permissive licences typically require you to keep copyright and licence notices. Copyleft licences can require you to release the source code of derivative works under the same terms when you distribute them, and some extend that obligation to software made available over a network. Breaching the conditions can end your permission to use the code. Keep a register of components and licences, set an approval policy, and review obligations before distributing products.
05Can our licences move to a buyer if we sell the business?
Often not without consent. Many licences prohibit assignment, define the licensee narrowly, or terminate on a change of control. In a share sale the licensee entity stays the same, so change of control clauses are the main issue. In an asset sale or carve-out, each licence must be assigned or replaced. Transitional services arrangements may also breach scope limits. Identify critical licences early in the deal and approach vendors with a plan, budgeting for new licences where needed.
06Are click-through software terms enforceable in Singapore?
Generally yes. The Electronic Transactions Act 2010 recognises contracts formed electronically, and courts will enforce click-through terms where the user was given reasonable notice of the terms and indicated acceptance. Browse-wrap terms, where use alone is said to signify acceptance, are more vulnerable. Exclusion and limitation clauses in standard terms remain subject to the reasonableness test under the Unfair Contract Terms Act 1977, and consumer protection rules may apply to consumer customers. Keep records showing which version each customer accepted.
Sources and official materials
- Copyright Act 2021 — Copyright in computer programs and permitted uses
- IPOS: Copyright — Overview of copyright protection in Singapore
- IPOS: Ownership and commercialisation — Ownership, assignment and licensing of copyright
- IPOS: Infringement and enforcement — Remedies for copyright infringement
- Electronic Transactions Act 2010 — Electronic contract formation
General information only, current as at 20 October 2026. It is not legal advice and does not create a lawyer–client relationship. Singapore law and regulatory practice change; check current official sources and take advice on the facts of your matter.
Talk it through
before you decide.
Share the decision, the jurisdictions and the timetable. A partner will tell you what matters, what can wait and what it will take.