Introduction
Trademark, copyright, or patent. Which one protects your software? It is a trick question. The real answer is usually all of them, applied to different parts of the product, and the one founders chase hardest is the one most of them cannot even obtain.
So let us kill the most common mistake we see, which is treating these three as a contest with one winner. They are not rivals. Your software is not a single thing. It is code, a brand, a look, and a secret sauce, and each of those needs a different kind of protection. Pick up the wrong tool and you leave everything else wide open. What follows matches each tool to the part it actually protects.
Your Code: Copyright
Start with the code. Under Directive 2009/24/EC on the legal protection of computer programs, source code and object code are protected by copyright as literary works, and that protection arises automatically the moment the work is created. There is no form to file, no fee, and no waiting period. Under the Berne Convention the enjoyment and exercise of copyright cannot be made subject to any formality, so it is yours on creation.
Here is the catch most founders miss. Article 1(2) of that Directive protects the expression of the program in any form and expressly states that ideas and principles underlying any element of a program, including those underlying its interfaces, are not protected. In Case C-406/10 SAS Institute v World Programming, the Court of Justice confirmed the practical consequence, holding that neither the functionality of a computer program, nor the programming language, nor the format of data files constitutes a form of expression protected under the Directive. Translated into founder terms: copyright stops someone copying your actual code. It does not stop a competitor building the identical feature in code of their own. Copyright is your baseline, not your moat.
A Real Invention: Maybe a Patent
Now the one everyone asks about, and the honest answer nobody wants. For most software, a patent is the wrong tool, and frequently you could not obtain one anyway.
Under Article 52(2)(c) and Article 52(3) of the European Patent Convention, programs for computers are excluded from patentability as such. The route through that exclusion is technical character. A computer-implemented invention can be patented where it produces a technical effect going beyond the ordinary physical interactions between program and computer, and where the features relied on for inventive step actually contribute to solving a technical problem by technical means.
Even where you clear that hurdle, weigh the cost. Patent prosecution is expensive, it takes years, and it is a disclosure bargain rather than a secrecy tool. Under Article 93 EPC your application is published 18 months after the filing or priority date, which means you teach the world how your invention works in exchange for a time-limited monopoly. Unless you have a genuine technical breakthrough that justifies both the expense and the publication, stop chasing the patent. It is the shiniest tool in the box and the wrong one for most software companies.
Your Brand: Trademark
Next, your brand. Your name, your logo, the thing customers type into a search bar to find you. That is protected by trade mark law, and it has nothing to do with your code.
An EU trade mark registered at the EUIPO under Regulation (EU) 2017/1001 gives you the rights in Article 9 across all Member States, allowing you to stop identical and confusingly similar signs used in the course of trade, and, where your mark acquires a reputation, to act against use that takes unfair advantage of or damages its distinctive character or repute. Registration runs for 10 years and can be renewed indefinitely for 10-year periods. Compared with a patent, it is inexpensive, comparatively fast, and potentially perpetual.
Two practical points. The EU operates a first-to-file system, so priority generally goes to whoever files first rather than whoever used the name first, which is why filing before a copycat or a professional filer gets there matters so much. And registration is not the end of it. Under Article 18, if you do not put the mark to genuine use in the Union within five years of registration, it becomes vulnerable to revocation for non-use, so purely defensive filings that never see real commercial use are not as safe as they feel. For most software companies the brand becomes one of the most valuable assets on the balance sheet, so protect it like one.
Your Secret Sauce: Trade Secrets
Here is the tool founders forget exists. If your genuine edge is a clever algorithm or a particular way of doing something, think hard before you patent it. A patent forces publication. Copyright will not protect the idea. Very often the smartest move is the opposite of going public.
Directive (EU) 2016/943 protects trade secrets, and Article 2(1) sets three cumulative conditions. The information must be secret, meaning not generally known or readily accessible to people in the relevant circles. It must have commercial value because it is secret. And it must have been subject to reasonable steps, under the circumstances, by the person lawfully in control of it, to keep it secret. That third condition is doing real work: confidentiality agreements, access controls, need-to-know segmentation, and documented internal policies are not merely prudent, they are the legal precondition for having a trade secret at all. Get them right and protection lasts as long as secrecy lasts, potentially forever.
Two limits deserve honesty, because trade secrecy is not a monopoly. Article 3 of the Directive makes independent discovery or creation lawful, and also makes observation, study, disassembly, or testing of a lawfully acquired product lawful, meaning legitimate reverse engineering. So a competitor who works it out honestly owes you nothing. And in software specifically, Article 5(3) of the Software Directive allows a lawful user to observe, study, and test the program to determine its underlying ideas and principles, Article 6 permits decompilation within limits for interoperability purposes, and Article 8 renders contractual provisions contrary to those rights null and void. Your NDA cannot contract around them. Trade secrecy is powerful, but it protects against misappropriation, not against being figured out.
Your Look: Registered Design
And the tool almost nobody uses. You can protect the appearance of your software, meaning your interface, your icons, and the way your product moves.
This was already possible in practice, and the EU design reform has now put it beyond argument. Regulation (EU) 2024/2822 amended the design definition in Regulation 6/2002 so that a design is the appearance of the whole or part of a product resulting from its features, expressly including the movement, transition or any other sort of animation of those features. The product definition was modernised in parallel to cover any industrial or handicraft item, “other than a computer program, regardless of whether it is embodied in a physical object or materialises in a non-physical form”. Note that exclusion carefully, because it is exactly the point. The software itself is not a design, but the interface it renders can be. The first phase of the reform applied from 1 May 2025, when Registered Community Designs became Registered EU Designs, and the second phase applied from 1 July 2026, which brought filing improvements including animated file formats such as MP4 and a higher permitted number of views.
Commercially this is attractive. The EUIPO protection runs for five years and can be renewed in five-year periods up to a maximum of 25 years, and a design must be new and have individual character. There is also an unregistered EU design right, which arises automatically on first disclosure in the Union but lasts only three years and protects against copying alone, so registration is materially stronger. Quietly, this remains one of the best-kept secrets in software intellectual property.
One footnote that ties the last two sections together. In Case C-393/09 BSA, the Court of Justice held that a graphic user interface is not a form of expression of a computer program under the Software Directive, but that it may nonetheless be protected by ordinary copyright where it constitutes its author’s own intellectual creation, and that elements dictated purely by technical function do not meet that threshold. So your interface may attract copyright as well, but a registered design is the far more reliable instrument.
The Real Answer: Build the Stack
So the answer to trademark, copyright, or patent is not “or”. It is a stack. Copyright and trade secrets protect the product. A trade mark protects the brand. A registered design protects the look. And a patent belongs in the stack only where you genuinely have a technical invention worth the cost and the disclosure. Build the whole stack rather than fixating on one impressive lock while every other door stands open.
One reminder that underpins all of it. You can only protect what you actually own. Where contractors, agencies, or founders working before incorporation wrote parts of your product, the default position in most European jurisdictions is that the author holds the copyright and paying an invoice transfers nothing without a written agreement. No assignment means no ownership, and no ownership means nothing to protect, however carefully you file.
Conclusion
Reflecting on the framework, the confusion between trademark, copyright, and patent persists because founders instinctively look for the one right answer, and intellectual property law does not work that way. It gives you a set of narrow, specialised rights, each with its own subject matter, term, cost, and disclosure trade-off. The companies that end up genuinely defensible are not the ones that found the single strongest right. They are the ones that identified the four or five distinct assets inside their product and matched each to the tool built for it, early enough that the filings were cheap and the ownership paperwork was still easy to gather.
