Can you handle the open-source licence review on a research-origin codebase?

Yes. We work alongside your engineering team to identify GPL/AGPL/LGPL components, assess the contamination risk, and produce a remediation plan that doesn't slow the commercial roadmap.

Our customer wants a perpetual licence with source-code escrow — is that worth agreeing?

Often, yes — but the trigger events, escrow agent and release conditions need careful drafting. A loose escrow clause can be more dangerous than no escrow at all.

Do you draft licences for AI models as well as conventional software?

Yes. The structure is similar but the warranty, indemnity and output-ownership clauses need bespoke drafting — boilerplate from a 2020 SaaS template doesn't survive a serious AI customer's review.

Software licensing · Oxford

Software Licensing Solicitor in Oxford

Software licensing is where the commercial economics of an Oxford technology business actually live: who can use what, where, on what hardware, for how long, with which derivatives, and what happens when the contract ends. Get the licence grant wrong and the rest of the contract is decoration.

Who this is for

Software Licensing Solicitor in Oxford.

Oxford-area SaaS vendors, on-prem software businesses, AI-model providers, and the increasing number of hybrid businesses that ship both. We also act for businesses inbound-licensing third-party software where the terms are about to become load-bearing.

Oxford's mix of academic-origin technology, enterprise customers and growing AI sector means licensing questions land here that don't surface in the wider Thames Valley — model-output ownership, training-data licences, open-source compliance from a research codebase, and dual-track academic-versus-commercial licensing.

Local legal context

Oxford — courts, councils and commercial hubs.

Commercial matters involving Oxford businesses are typically dealt with at the Oxford Combined Court for County Court proceedings and Reading Employment Tribunal for employment claims. The commercial counterparty mix is shaped by the University, the NHS trusts around the John Radcliffe and the deep concentration of research-led occupiers at Begbroke, Harwell and the Oxford Science Park.

Courts & tribunals: Oxford County Court · Oxford Combined Court (Crown / County) · Reading Employment Tribunal · First-tier Tribunal (Tax) — Reading hearings
Local authorities: Oxford City Council · Oxfordshire County Council · South Oxfordshire District Council
Business hubs: Oxford Science Park · Begbroke Innovation Accelerator · Harwell Campus · Oxford BioEscalator · Milton Park (Didcot)
Dominant industries: applied AI and deep tech · life sciences and medtech · university spin-outs · professional services and consultancy

Scenarios we handle

Common matters on this page.

SaaS subscription terms

Drafting or refreshing a vendor-side SaaS subscription agreement — usage rights, named users vs concurrent, environments, service levels, suspension and exit.

On-prem / hybrid licence

Term or perpetual licences for on-prem deployments with optional cloud components — getting the licence grant, audit rights and updates clauses to actually match the deployment model.

AI model licence

Licensing a proprietary model (or weights) to a customer — covering allowed uses, fine-tuning rights, output ownership and training-data warranties.

Relevant: EU AI Act · UK GDPR

Open-source compliance review

Spin-out and research-origin codebases often carry copyleft components that need cleaning before commercial licensing. We audit and advise on remediation.

Legal risks & how we manage them

What can go wrong — and how we contain it.

Implied licences that swallow the explicit licence grant.
We draft the grant tightly and exclude implied licences explicitly.
GPL / AGPL contamination from a research codebase.
An OSS audit before any commercial licensing — we work alongside your engineers, not over their heads.
AI training-data warranties that the business can't actually back.
We rewrite the warranty to reflect what the model was actually trained on, with carve-outs the customer can live with.

Relevant law

Legislation that shapes this work.

Copyright, Designs and Patents Act 1988: The foundation of every software licence in the UK — sets what can be licensed and what must be expressly granted.
EU AI Act: Drives the risk-tier classification and provider obligations referenced in AI model licences.
UK GDPR: Governs the data-processing layer that sits inside almost every SaaS subscription.

FAQs

Questions we get asked.

Can you handle the open-source licence review on a research-origin codebase?: Yes. We work alongside your engineering team to identify GPL/AGPL/LGPL components, assess the contamination risk, and produce a remediation plan that doesn't slow the commercial roadmap.
Our customer wants a perpetual licence with source-code escrow — is that worth agreeing?: Often, yes — but the trigger events, escrow agent and release conditions need careful drafting. A loose escrow clause can be more dangerous than no escrow at all.
Do you draft licences for AI models as well as conventional software?: Yes. The structure is similar but the warranty, indemnity and output-ownership clauses need bespoke drafting — boilerplate from a 2020 SaaS template doesn't survive a serious AI customer's review.

Topical cluster.

Talk to a software licensing solicitor in Oxford.

Speak to Radcliffe Enterprise Law for clear, commercial legal advice — by phone, video or in person.

Start the conversation