
Commissioning an application specific integrated circuit (ASIC) represents a substantial investment in specialist engineering. But payment alone does not settle who owns the resulting intellectual property (IP). Here, Ross Turnbull, Director of Business Development at custom IC design and supply specialist Swindon Silicon Systems, explains why IP ownership in ASIC development deserves early and explicit attention.
The question of IP ownership tends to surface early in a new engagement. A company arrives with a novel sensor concept or a proprietary approach to signal processing and wants a chip built around it. Understandably, they want confidence that the innovation behind their product remains theirs. At the same time, the engineering work required to realise that concept in silicon, from architecture decisions through to verification, is itself a substantial body of intellectual effort, and questions naturally follow about where those rights sit too.
This distinction is more prevalent in ASIC design than in most other engineering disciplines. There are no standard parts; every ASIC is purpose-built for a specific application, which means a customer’s own IP is embedded in the brief from the very first conversation, rather than sitting alongside an off-the-shelf design.
Why ownership isn’t automatic
It’s a common assumption that paying for a chip design means owning everything created in the process. This isn’t a reliable rule to work from. As a general principle of UK IP law, copyright in commissioned engineering or design work belongs to its creator unless ownership is expressly assigned in writing. Purchasing the resulting product does not, by itself, transfer ownership of the underlying IP rights, although specific rights and licenses depend on the terms agreed between the parties.
This doesn’t mean customers are left exposed. It means the allocation of rights depends on the specific terms agreed for that engagement, which is precisely why those terms are worth establishing clearly rather than assumed.
Two kinds of IP in one project
Every custom silicon project tends to involve at least two categories of IP. The first is the customer’s own innovation: the concept, application knowledge or system-level insight that makes their product distinctive. The second is the engineering work generated in the course of design, including schematics, test methodologies and, in many cases, reusable design blocks or techniques that a design house draws on across multiple projects.
These categories are not always neatly separable and treating them as identical can lead to confusion later. A customer’s underlying innovation deserves protection regardless of who authored the silicon that embodies it. Equally, an ASIC designer’s own accumulated methods and building blocks, developed over years of practice, are not automatically handed over simply because they were used to build one customer’s chip.
Protecting what customers bring
Given how much of a customer’s competitive advantage can be wrapped up in a single design brief, confidentiality must be treated as a starting condition, not an afterthought. In practice, this starts before any technical discussion takes place, with non-disclosure agreements (NDAs) signed upfront and confidentiality terms agreed as standard rather than optional.
Internally, access to a customer’s application details and design data is restricted to the engineers working directly on that programme, and customer-specific design information is kept separate from any general-purpose tools, blocks or methodologies used across other projects. Protection, in this sense, comes less from any single safeguard and more from consistently narrowing who sees what, and why.
Transistor-level simulations
The most effective way to avoid disagreement later is to agree IP terms before detailed design work begins, not after. Setting out clearly what belongs to the customer, what remains with the design house, and how any jointly developed elements will be treated gives both parties a shared understanding to work from throughout the project, rather than a difficult conversation once the chip is already in production.
At Swindon Silicon Systems, these conversations take place at the outset of a project rather than once development is underway. IP ownership, confidentiality obligations and the treatment of any reusable design elements are discussed and agreed before detailed engineering begins, ensuring both parties have a clear understanding of their rights and responsibilities throughout the programme.
Every engagement is different, and the right allocation of rights depends on what is being designed, how it will be used and the commercial relationship between the parties. What stays constant is the principle: customers should know exactly what they own, design partners should know what they retain, and neither should be left to assume.
To discuss how Swindon Silicon approaches IP protection and confidentiality in custom silicon engagements, get in touch with the team here.





