ALID
Menu

trade secret vs patent software

Trade Secret or Patent? A Decision Framework for Software and AI Inventions

By ALID

Two routes, one decision window

Most novel software and AI inventions present a real choice between two protection routes. The patent route trades disclosure for a 20-year exclusionary right. The trade secret route trades disclosure obligations for protection that can in principle last indefinitely, conditioned on continued secrecy.

The two routes are not equivalent. They protect different things, withstand different attacks, and reward different operational practices. The choice between them has to be made before the work goes public, through publication, product release, conference presentation, or third-party access. Once the work is out, the trade secret route is foreclosed.

For in-house IP counsel, the operative question is not “patent or trade secret?” in the abstract. It is “for this invention, given these product, market, and detectability conditions, which route is defensible, and what does the disclosure record need to capture either way?”

The honest answer is that the disclosure intake supports both decisions. The same engineering signal that supports a patent application supports a trade-secret protection program. The decision between them is a function of facts that surface during the same intake.

What each route actually protects

A patent under 35 U.S.C. § 271 defines the acts of infringement that breach the patentee’s right to exclude others from making, using, selling, or importing the claimed invention. The exclusionary right itself runs for the patent term, 20 years from the earliest non-provisional priority date, and reaches any party, including independent re-inventors and reverse-engineerers. It survives publication.

A trade secret under the Defend Trade Secrets Act, 18 U.S.C. § 1836, and parallel state law confers a right against misappropriation. The DTSA defines a protectable trade secret in 18 U.S.C. § 1839(3) as information that derives independent economic value from not being generally known and is the subject of reasonable measures to keep secret. Misappropriation requires acquisition by improper means or use after acquisition by improper means.

Two structural differences follow.

A trade secret does not run against independent derivation or reverse engineering by proper means. The DTSA’s definition of “improper means” in § 1839(6)(B) explicitly excludes “reverse engineering, independent derivation, or any other lawful means of acquisition.” A competitor who arrives at the same invention through their own work is not liable.

A patent does not require ongoing operational discipline to remain valid. Once granted, it persists through the term regardless of whether the patentee maintains internal secrecy. A trade secret evaporates the moment the secrecy lapses, through a careless slide deck, a published paper, an unmasked product release, or an exiting employee.

When the patent route is the right route

Four conditions tend to push toward patent protection.

The invention is reverse-engineerable from the product. If a competitor can buy the product, decompile, instrument, or examine it, and arrive at the technical mechanism, trade secrecy will not survive product launch. Most consumer-facing software falls in this category. So does most hardware. So does any model whose architecture is recoverable from observable behavior.

The invention has a long useful life. A patent’s 20-year term is meaningful for inventions that will still matter in ten or fifteen years. For inventions whose competitive value will be obvious in three years, the term is irrelevant and the disclosure cost of patenting is harder to justify.

The invention is detectable by inspection of competing products. Patent rights are only valuable if infringement is identifiable. A method patent is worth more when the steps of the method leave traces in product behavior, network traffic, or output characteristics that an investigator can document.

The competitive landscape is jurisdictionally diverse. Patents are jurisdiction-specific but enforceable through familiar mechanisms in every major patent jurisdiction. Trade secret law is fragmented internationally, and the procedural mechanics differ widely. For inventions that need protection in multiple jurisdictions, the patent route consolidates the protection regime.

When the trade secret route is the right route

Four different conditions push toward trade secrecy.

The invention is not reverse-engineerable from the product. Server-side ML model architectures, training data compositions, hyperparameter regimes, internal feature stores, and back-end infrastructure choices are often not recoverable from product behavior. They can be operated for years without external exposure.

The invention’s value depends on continuous improvement. A model that benefits from constant retraining and continuous data accumulation can run on the trade-secret route indefinitely. A patent on a model architecture freezes a snapshot. The trade-secret route preserves optionality.

The invention has detectability problems. If infringement would not be visible from outside (a competitor implements the same method in their own infrastructure with no observable trace), patent enforcement is theoretical. Trade-secret protection through DTSA actions, employee NDAs, and contractor restrictions can produce real deterrence even where patent enforcement cannot.

The competitive context rewards speed over disclosure. Patenting requires public disclosure within a defined window. For inventions where the strategic advantage comes from being faster than competitors at deploying capability they cannot easily replicate, the disclosure cost can outweigh the exclusionary benefit.

The DTSA practicalities counsel actually use

The DTSA gives in-house counsel a federal cause of action with several useful features.

It provides a federal-court forum, removing the procedural burdens of pursuing parallel state-court claims under the Uniform Trade Secrets Act in jurisdictions that adopted it. It supports injunctive relief to prevent actual or threatened misappropriation, damages measured by actual loss plus unjust enrichment (or, alternatively, a reasonable royalty), and exemplary damages up to twice actual damages for willful and malicious misappropriation. The statute of limitations is three years from discovery of the misappropriation, or from when discovery should have occurred with reasonable diligence.

The “reasonable measures” requirement in § 1839(3)(A) is operative. Courts dismiss DTSA claims when the plaintiff cannot show the secret was actually treated as a secret. Reasonable measures typically include: written confidentiality and non-disclosure agreements with employees and contractors, technical access controls, document classification, exit interviews, and written policies on use and disclosure. The disclosure record at intake feeds the same operational discipline: identifying what is being protected and how.

For AI-generated outputs and AI-developed processes, the DTSA’s treatment of trade secrets does not depend on a human inventor. That is one reason trade secrecy has emerged as a route for AI-assisted innovations where inventorship questions complicate the patent route, though the November 2025 USPTO inventorship guidance has narrowed those complications considerably.

Hybrid approaches that actually work

The patent-versus-trade-secret decision is not always binary. Several hybrid approaches preserve optionality.

A team can patent the architectural mechanism while keeping training data, hyperparameters, and operational tuning as trade secrets. The patent covers the structural innovation; the trade secret covers the operational moat. Both can be enforced independently.

A team can file provisional applications to preserve patent option value while continuing to evaluate whether the invention is better-suited to the trade-secret route. The 12-month conversion window under 35 U.S.C. § 119(e) gives counsel real decision time without committing to public disclosure.

A team can patent claim scopes that are detectable from product behavior while keeping non-detectable scopes as trade secrets. The patent claims handle the cases where enforcement is realistic; trade secrecy handles the cases where it is not.

Each hybrid has the same operational requirement. The disclosure intake has to surface the technical specifics in enough detail that the team can decide which route applies to which aspect of the invention. A one-paragraph IDF cannot support that decision.

What the disclosure record should capture for the decision

Whether the eventual route is patent, trade secret, or hybrid, the same intake fields drive the decision.

  • Reverse-engineerability assessment. What technical signal is exposed in the product? In observable behavior? In response patterns? In timing characteristics? An inventor’s honest answer about whether a determined competitor could recover the mechanism is the first input.
  • Useful-life estimate. How long will this invention matter competitively? Three years, ten years, twenty? The answer constrains the value of a 20-year patent term.
  • Detectability of infringement. What evidence would tell counsel that a competitor is using this invention? If the answer is “we would not be able to tell,” patent enforcement is theoretical.
  • Operational secrecy posture. Is the invention currently held under access controls, NDAs, and reasonable measures? If not, the trade-secret route has a baseline problem before the decision is made.
  • Disclosure pressure. Are there upcoming publications, conference presentations, customer demos, or product launches that will expose the invention? The disclosure window constrains the trade-secret route’s viability.

These are not patent-application questions. They are intake questions. The decision they support is the one the team has to make before either route is foreclosed.

The DTSA’s text in 18 U.S.C. § 1836 and § 1839 is short and worth reading directly. The patent counterparts are 35 U.S.C. § 271 (acts of infringement), § 102 (novelty), and § 112 (specification requirements).

For the disclosure-record discipline both routes rely on, see our note on attorney-led invention discovery, the intake mode that surfaces the technical specifics either route requires.

ALID reads engineering artifacts and surfaces invention candidates with the technical specifics that support the route decision: what’s reverse-engineerable, what’s detectable, what’s operationally secret. To see how the discovery and disclosure flow operates, read how ALID works, or request access to run a first discovery against your own engineering data.