Software Patents and Intellectual Property
Software Patents and Intellectual Property
Definition: Legal protections covering original creative and technical work: patents protect novel inventions (including some software techniques), copyright protects the actual code and creative expression, trademarks protect brand names and logos, and trade secrets protect confidential business information kept secret.
How It Works
- Copyright applies automatically the moment original code is written, no registration required, though registration strengthens enforcement and is required before filing a US infringement lawsuit
- Patents require a formal application and examination process and cover a specific novel, non-obvious technical method, not just “an app that does X”
- Trademarks protect names, logos, and other identifiers used to distinguish a product in commerce, separate from the code or invention itself
- Trade secrets protect confidential information (algorithms, formulas, internal processes) for as long as it’s actually kept secret, with no filing or expiration involved, protection ends the moment the secret leaks, intentionally or not
- Software sits at an odd intersection: the code itself is copyrighted automatically, while a genuinely novel technical process implemented in that code may separately be patentable
- Patent eligibility for software has narrowed since the US Supreme Court’s Alice Corp. v. CLS Bank (2014) decision, which held that merely implementing an abstract idea on a generic computer isn’t patentable
- Utility patents (the type covering most software inventions) protect how something works; design patents protect how something looks (an icon, a UI layout), each has a different term and a much faster, cheaper examination for design patents
- Open source licenses (like MIT License or GPL License) operate on top of copyright, they’re permission grants from the copyright holder, not a separate form of IP protection
| Patent type | Protects | Term |
|---|---|---|
| Utility | How an invention works or functions | 20 years from filing |
| Design | How a product visually appears | 15 years from grant |
International filing adds another layer: a US patent only protects against infringement inside the US, a company that wants coverage in Europe or Asia has to file separately in each jurisdiction, or use the Patent Cooperation Treaty (PCT) process to preserve the option across many countries at once before committing to the cost of each one.
Under the Hood
Worked example 1: provisional to grant
- Given: a founder files a provisional patent application in January 2020 for a novel caching algorithm, to lock in an early priority date while still refining the invention
- Step 1: the provisional isn’t examined, but starts a 12-month clock, “patent pending” status begins immediately
- Step 2: within 12 months, a non-provisional application must be filed claiming priority back to the provisional, or that earlier date is lost
- Step 3: the non-provisional enters the examination queue, first office action typically arrives 12-18 months later
- Step 4: after one or two rounds of office actions and claim amendments, a notice of allowance issues, average total pendency for software patents runs around 2-3 years from the non-provisional filing
- Answer: patent issues roughly 3 years after the non-provisional filing, enforceable for 20 years from that filing date
Worked example 2: rejection and response cycle
- Given: an examiner rejects all 10 claims of a filed application, citing two prior-art patents that appear to cover similar ground
- Step 1: applicant’s attorney reviews the cited prior art and narrows the claims to a more specific, distinguishing implementation detail
- Step 2: response is filed within the standard 3-month deadline (extendable to 6 months with fees)
- Step 3: examiner either allows the narrowed claims or issues a second office action, often a “final” rejection if unresolved
- Answer: most applications go through at least one full rejection-and-response cycle before allowance or abandonment
Worked example 3: patent vs trade secret decision
- Given: a company invents a novel data-compression technique and must decide whether to patent it or keep it as a trade secret
- Step 1: patenting requires publishing the full technical details, once granted, competitors can read exactly how it works, they just can’t use it without a license for 20 years
- Step 2: a trade secret never expires, but only works if the company can actually keep it hidden, reverse engineering a shipped product can reveal it anyway
- Step 3: if the technique is easily reverse-engineered from the product itself, a patent is usually the better bet, since secrecy wouldn’t hold up regardless
- Answer: patent when the invention would be discoverable by inspecting the product; keep as a trade secret when it’s an internal process competitors can’t observe
Worked example 4: freedom-to-operate check
- Given: a team is about to launch a feature using a specific real-time synchronization technique
- Step 1: before launch, they run a freedom-to-operate search across issued patents in that technical area
- Step 2: the search surfaces a patent held by a competitor with claims that closely match the planned implementation
- Step 3: legal counsel reviews the claim language and finds the implementation can be redesigned around the specific claimed steps without meaningfully changing the user-facing feature
- Answer: the team ships a re-engineered version that avoids the patent’s specific claimed method, avoiding likely infringement without abandoning the feature
Why It Matters
- Determines what a company can legally build, and what existing patents or copyrighted code might expose it to infringement risk before a single line ships
- A patent is a tradeable, licensable asset, startups sometimes use patent portfolios as leverage in fundraising, litigation defense, or acquisition negotiations
- Choosing patent vs trade secret is a real strategic decision: a patent requires public disclosure of how the invention works, a trade secret protects only as long as it stays hidden
- Trademark clearance before naming a product avoids a costly rebrand later, once a name has real market recognition
- Investors and acquirers routinely review a startup’s IP position during diligence, weak or missing IP assignment agreements with contractors or early employees can stall or kill a deal
- Open source license compliance is a form of IP risk management too, shipping GPL-licensed code inside a proprietary product without honoring its terms creates real legal exposure
- Patent litigation, even a weak claim, is expensive enough to settle that “patent troll” (non-practicing entity) demand letters are a real cost of doing business in some software categories
- Trademark registration in the right classes and jurisdictions matters before international expansion, a name can be free to use in one country and already claimed in another
Common Pitfalls
This is general information, not legal advice, consult a patent or IP attorney before filing or launching anything with real exposure.
- Assuming an idea itself can be protected, copyright covers the specific expression (the actual code), not the general concept behind it
- Building a product without a freedom-to-operate search, only discovering a blocking patent after significant investment
- Publicly disclosing an invention (blog post, conference talk, demo) before filing, the US has a 1-year grace period but most other countries have none, permanently losing patent rights there
- Filing a patent for something better protected as a trade secret, publication in the patent itself teaches competitors exactly how it works
- Treating “we didn’t copy their code” as a complete defense, patent infringement doesn’t require copying, independent invention still infringes
- Letting a provisional application lapse past the 12-month window without filing the non-provisional, losing the earlier priority date entirely
- Not having IP assignment agreements signed with every contractor and co-founder, leaving ambiguity over who actually owns code written before incorporation
- Reusing GPL-licensed code inside proprietary software without understanding the copyleft obligations that come with it
- Filing only in the US and assuming that patent blocks competitors internationally, patent protection is territorial, not global
- Assuming a granted patent is automatically valid and enforceable, patents get invalidated in litigation regularly when prior art surfaces that the examiner missed
- Skipping trademark clearance searches before launch, then facing a rebrand demand once the product has real market traction and press coverage
Comparison
| Patent | Copyright | Trademark | Trade Secret | |
|---|---|---|---|---|
| Protects | Novel inventions or methods | Original expression (code, text, art) | Brand names, logos, identifiers | Confidential business information |
| Requires registration | Yes, examined application | No, automatic on creation | Strengthened by registration, exists via use | No, exists only while kept secret |
| Duration | 20 years from filing | Life of author plus 70 years (or 95 years for corporate works) | Indefinite, while in active use | Indefinite, while kept secret |
| Requires public disclosure | Yes, full disclosure published | Yes, in effect, the work itself is visible | Yes, used openly in commerce | No, secrecy is the entire protection |
| Typical cost | High, often $10,000-30,000+ with attorney fees | Low, registration around $65 | Moderate | Low filing cost, but ongoing internal security effort |
| Enforcement need | Litigation to stop infringement | Litigation or takedown notices | Litigation or opposition proceedings | Litigation, must prove secrecy was maintained |
| Blocks independent invention | Yes, infringement doesn’t require copying | No, independent creation is a full defense | Yes, within the same market/goods category | No, someone else can legally discover it independently |
| Governing US body | USPTO | US Copyright Office (registration optional) | USPTO | No filing body, protected by state and federal trade secret law |
A single product typically relies on several of these at once: the codebase is copyrighted automatically, the product name is trademarked, a genuinely novel underlying algorithm might be patented, and the training data pipeline or internal tuning process might be kept as a trade secret instead of published.
Example
Amazon’s “1-Click” ordering patent (US Patent 5,960,411), filed in 1997 and granted in 1999, is one of the most widely cited software patents in tech history. Amazon used it to obtain an injunction against Barnes & Noble’s similar “Express Lane” checkout in 1999, and later licensed it to Apple for use in the iTunes Store, a real, well-documented case of a software patent directly shaping competitive checkout design across the industry for years.
On the copyright side, Google LLC v. Oracle America, Inc. went all the way to the US Supreme Court, decided in 2021, over Google’s use of Java API declarations in Android. Oracle argued copying the API structure infringed its copyright; the Court ruled Google’s use was fair use, a landmark decision clarifying how much of an API’s structure can be reused without infringing the underlying code’s copyright.
Open source licenses layer on top of this framework rather than replacing it: MIT License grants broad permissive reuse, GPL License requires derivative works to stay open under the same terms, and Apache License 2.0 adds an explicit patent grant on top of permissive copyright terms, protecting users from patent claims by the code’s own contributors.
Related Terms
Referenced by