Carriers File Preemptive Suits as Patent Firm Targets Insurance Tech Stacks

From tracking USPTO filings and patent litigation across the insurance industry since 2024, the shift from offensive patent filing to coordinated defensive litigation signals a maturation of how carriers think about technology IP. On April 7, 2026, Hartford Fire Insurance Company and the Hanover Insurance Group filed separate declaratory judgment complaints against Intellectual Ventures and its subsidiaries. Travelers Indemnity Company followed the next day with its own filing. All three suits share a common target: a patent monetization firm that sent licensing demands in the low-to-mid seven figures to each carrier, asserting that their use of Docker, Kubernetes, Apache Spark, Apache Airflow, MongoDB, and Elasticsearch infringes a portfolio of patents covering foundational infrastructure tools. Hartford’s complaint alone runs to 16 counts seeking declarations of non-infringement and invalidity across eight patents. Travelers challenged 14 patents. Hanover targeted three. The total: 25 patents contested across three coordinated filings in two federal courts within 24 hours.

This is not a dispute about proprietary AI models or novel underwriting algorithms. The patents at issue cover general-purpose software infrastructure that nearly every enterprise uses. The carriers’ core argument is straightforward: they did not develop these tools, they did not customize them in patentable ways, and their use of off-the-shelf open-source software cannot constitute infringement. The coordinated timing, the aggressive scope of the complaints, and the cross-industry pattern of Intellectual Ventures’ demands all point to a new strategic reality in insurance technology: defending the right to use foundational infrastructure is now as important as filing offensive patents on proprietary AI systems.

The licensing campaign: two years of escalation

Intellectual Ventures began contacting Hartford in late 2023, seeking to open licensing discussions around its portfolio of more than 7,000 active patents. Over the next two-plus years, communications grew more pointed. According to Hartford’s complaint filed in the U.S. District Court for the District of Delaware (Case 1:26-cv-00392), roughly 10 separate communications flowed between Intellectual Ventures and Hartford between December 2023 and March 2026. The campaign culminated in a March 2026 demand letter from IV’s outside counsel at Kasowitz Benson Torres LLP, accompanied by a $3.5 million licensing demand.

Hanover and Travelers received similar treatment. Each carrier reported contact from Kasowitz in March or April 2026 with demands in the same low-to-mid seven-figure range. The filings describe a pattern where Intellectual Ventures deliberately avoids filing its own infringement suits, instead relying on demand letters calibrated to stay just under the threshold that would give targets a clear basis for declaratory judgment jurisdiction. The insurers’ complaints allege that the March 2026 Kasowitz letters crossed that line, creating the “case or controversy” required under Article III for a DJ action.

The defendants named in Hartford’s filing reveal the corporate structure behind the campaign: Intellectual Ventures I LLC, Intellectual Ventures II LLC, Callahan Cellular L.L.C., Zarbana Digital Fund LLC, OL Security LLC, and Cufer Asset Ltd. L.L.C. These shell entities hold different subsets of IV’s patent portfolio. By asserting patents through multiple subsidiaries, IV complicates the defensive posture for targets who must identify which entity holds which patents before filing suit.

Hartford’s 16-count complaint

Hartford’s Delaware complaint is the most aggressive of the three filings. The 16-count structure seeks declarations on two distinct tracks: non-infringement and invalidity. For each of the eight patents, Hartford requests a declaration that its technology operations do not infringe any valid claim, and a separate declaration that the patent is invalid based on prior art and ineligibility under 35 U.S.C. § 101.

The invalidity challenge is notable. Hartford is not merely arguing that it does not use the patented technology. It is arguing that the patents should never have been issued. This dual-track strategy maximizes the potential payoff: a non-infringement finding protects Hartford but leaves the patents alive to be asserted against others, while an invalidity finding eliminates the patents entirely, benefiting the entire industry.

The complaint also seeks injunctive relief to prevent Intellectual Ventures from asserting those patents against Hartford, its affiliates, subsidiaries, representatives, agents, vendors, and customers. That vendor and customer protection language is significant for the insurance technology ecosystem. If Hartford obtains an injunction covering its vendors, the companies supplying Docker, Kubernetes, and Spark deployments to Hartford gain a degree of protection by extension.

Travelers’ Delaware filing covers broader ground, challenging 14 patents on non-infringement grounds. Hanover’s Massachusetts filing is narrower, targeting three patents. The variance in patent counts likely reflects differences in which IV subsidiaries sent demands to each carrier and which specific patents were cited in each demand letter.

The technology at the center: open-source infrastructure

The technologies cited in the complaints are not proprietary insurance systems. They are general-purpose infrastructure tools that run across every major industry:

Technology	Function	Insurance Use Case
Docker	Container runtime for packaging and deploying applications	Isolating ML model inference, standardizing deployment across environments
Kubernetes	Container orchestration for scaling and managing workloads	Auto-scaling claims processing pipelines, managing AI model serving clusters
Apache Spark	Distributed data processing engine	Loss triangle calculations at scale, telematics data processing, catastrophe model aggregation
Apache Airflow	Workflow orchestration and scheduling	Scheduling nightly rate-filing data refreshes, coordinating ETL for regulatory reporting
MongoDB	NoSQL document database	Storing unstructured claims documents, policy metadata, submission intake data
Elasticsearch	Search and analytics engine	Full-text search across policy documents, claims adjuster knowledge bases, compliance query tools

The Kubernetes ecosystem alone has grown into a $2.23 billion market in 2026, expanding at a 27.1% compound annual growth rate according to industry research. A 2025 Cloud Native Computing Foundation survey found that 93% of organizations either run Kubernetes in production or are piloting it in test environments. These are not niche technologies that a handful of companies use. They are the standard infrastructure layer for modern enterprise computing.

Hartford’s complaint emphasizes this point directly: the infringement theory rests entirely on Hartford’s use of off-the-shelf products, not on anything the insurer developed or customized. The carriers did not build Docker. They did not modify Kubernetes. They adopted the same tools that banks, airlines, retailers, and agricultural companies use, tools maintained by open-source communities and commercial vendors with their own IP portfolios.

This distinction matters for the Section 101 analysis. Patents covering the fundamental operation of open-source infrastructure tools face a higher bar for enforceability than patents covering novel applications layered on top of that infrastructure. The Federal Circuit’s decision in Recentive Analytics v. Fox Corp. reinforced that generic applications of known computing techniques to new environments are patent-ineligible, a holding that could be directly relevant to IV’s infrastructure patents if they claim nothing more than containerization or orchestration methods already documented in open-source repositories.

The cross-industry targeting pattern

Insurance carriers are not the only targets. Hartford’s complaint alleges that Intellectual Ventures pursued similar licensing campaigns against companies across multiple industries:

• Banking: JP Morgan Chase, Bank of New York Mellon
• Insurance: Nationwide Mutual, Liberty Mutual, GEICO (in addition to Hartford, Travelers, and Hanover)
• Aviation: American Airlines, Southwest Airlines
• Retail: Home Depot
• Agriculture: Deere & Company

This cross-industry pattern reveals IV’s strategy. The patents do not target insurance-specific technology. They target general-purpose infrastructure tools used by any enterprise with a modern technology stack. The licensing demand is calibrated to fall below the cost of litigation: a $3.5 million demand is expensive enough to generate revenue at scale but cheap enough that many targets will pay rather than fight. When the targets span banking, aviation, retail, agriculture, and insurance, the aggregate revenue potential from even partial compliance is substantial.

IV’s previous campaign confirms the pattern. In late 2023, Intellectual Ventures I and II filed infringement suits in the Eastern District of Texas against JP Morgan Chase, Liberty Mutual, and Comerica, asserting six patents covering the use of Docker, Kafka, Apache Spark, and Kubernetes. Four of those patents were asserted against all three defendants over many of the same open-source products now at issue in the insurer DJ actions. JP Morgan Chase subsequently settled the Texas lawsuit, the terms undisclosed. Liberty Mutual, already a target of the earlier Texas campaign, now faces additional demand-letter pressure alongside the newer insurer targets.

Intellectual Ventures: the entity behind the demands

Understanding the scale and history of Intellectual Ventures provides essential context. Founded in 2000 by Nathan Myhrvold, a former Microsoft chief technology officer, and Edward Jung, also of Microsoft, IV has raised over $5.5 billion from investors including Microsoft, Intel, Sony, Nokia, Apple, Google, and Yahoo, along with institutional investors such as Stanford University and the Mayo Clinic.

At its peak, IV controlled approximately 70,000 intellectual property assets, including patents and pending applications, generating roughly $3 billion in revenue primarily through license fees from large corporations. The company’s business model centers on acquiring patents, aggregating them into large portfolios, and licensing them to third parties or pursuing litigation against companies it claims are infringing. Critics have described it as the largest patent assertion entity in the United States. Defenders argue it provides a market for inventors who lack the resources to commercialize their own innovations.

The current portfolio of 7,000+ active patents represents a smaller but still formidable collection after years of portfolio sales and expiration cycles. IV’s shift toward open-source infrastructure patents represents an evolution from its earlier campaigns, which targeted proprietary software features. By asserting patents against the use of open-source tools, IV can reach any company that runs Docker or Kubernetes, dramatically expanding its addressable target base.

The open-source defense ecosystem fights back

The insurer DJ filings are not the only defensive response to IV’s infrastructure patent campaign. The open-source community has been mounting its own challenges through inter partes review (IPR) and ex parte reexamination proceedings at the USPTO.

In May 2024, Unified Patents filed an ex parte reexamination against U.S. Patent 7,949,785, held by Intellectual Ventures II LLC. The ’785 patent relates to systems of communication via virtual networks, which IV asserts covers open-source container orchestration systems such as Kubernetes. Less than three weeks after filing, the USPTO’s Central Reexamination Unit granted the request, finding “substantial new questions of patentability on the challenged claims.” That reexamination remains pending.

Docker, Inc. has separately filed an inter partes review petition (IPR2025-00840) against U.S. Patent 8,332,844, also held by Intellectual Ventures II LLC. The CNCF (Cloud Native Computing Foundation), which stewards the Kubernetes project, has partnered with Unified Patents on prior art crowdsourcing campaigns, inviting the developer community to contribute prior art that can be used to challenge IV’s patent claims.

These parallel proceedings create a multi-front defensive environment. If the USPTO invalidates IV’s infrastructure patents through reexamination or IPR, the underlying basis for the licensing demands collapses. If the insurer DJ suits succeed on invalidity grounds, the same result flows to other targets. The coordinated timing of the insurer filings, combined with the open-source community’s patent challenges, suggests at least an awareness of complementary litigation strategy, even if formal coordination between the insurers and the open-source defenders has not been disclosed.

Why carriers chose offense over settlement

The default response to a patent licensing demand, particularly one below the cost of litigation, is to negotiate and settle. The cost of defending a patent infringement suit through trial averages $3 million to $5 million for cases with less than $25 million at stake, according to the American Intellectual Property Law Association’s economic survey. A $3.5 million licensing demand is precisely calibrated against that cost curve: paying the demand is cheaper than fighting.

Hartford, Travelers, and Hanover chose to fight anyway. Several factors explain why.

Precedent value. Paying a licensing demand for the use of open-source infrastructure tools sets a precedent that any future patent assertion entity can exploit. Once a carrier pays for the right to use Docker, the next demand letter will target Kubernetes, then Spark, then every other component in the stack. The total cost of serial capitulation dwarfs the cost of a single defensive action.

Collective action dynamics. Three carriers filing simultaneously in two courts within 24 hours is not coincidental. Coordinated DJ filings distribute the cost of defense, create multiple forums for testing the patents, and send a signal to IV and other patent assertion entities that the insurance industry will not acquiesce. If all three carriers had settled quietly, IV would have moved to the next six targets with a validated demand template.

Strength of the non-infringement defense. As the Above the Law analysis noted, “nothing blocks a license transaction more than when the target feels that they have a killer noninfringement defense.” All three insurers believed their use of off-the-shelf open-source software provided strong grounds to resist IV’s demands. When the accused technology is not something the carrier built, but rather a community-maintained open-source project used by millions of organizations, the non-infringement argument carries particular weight.

Technology procurement protection. Hartford’s request for injunctive relief covering vendors and customers reflects a strategic calculation about the broader technology supply chain. If IV can assert patents against carriers for using Docker, it can also assert patents against the cloud vendors who host those Docker deployments, the managed service providers who operate them, and the consultancies who implement them. Protecting the supply chain protects the carrier’s ability to procure and deploy technology without patent encumbrances.

Implications for carrier technology strategy

The IV campaign forces a question that most carrier technology leaders have not had to answer: what is the patent exposure of our infrastructure stack?

Carriers have invested heavily in modern technology infrastructure. Travelers allocated $1.5 billion annually to technology as of its most recent disclosures, with strategic AI spend more than doubling over eight years and 20,000 employees using AI tools built on top of open-source infrastructure. Hartford, Chubb, AIG, and Progressive have made comparable commitments. These investments assume that the underlying infrastructure, the container runtimes, orchestration platforms, data processing engines, and workflow schedulers, can be used without licensing fees beyond the standard commercial support contracts already in place.

If patent assertion entities can extract licensing revenue from the infrastructure layer, the economics of technology investment shift. Every carrier running Docker owes a royalty. Every carrier running Kubernetes owes another. Every carrier running Spark, Airflow, MongoDB, and Elasticsearch adds incremental patent exposure with each tool adoption. The cumulative cost transforms the total cost of ownership for technology modernization programs that carriers have already committed to.

The procurement implications are concrete. Carrier technology teams evaluating open-source tools now need to consider:

• Patent indemnification clauses in vendor contracts for managed services (AWS EKS, Google GKE, Azure AKS) that host open-source infrastructure
• Contribution to defensive patent pools such as the Open Invention Network, which provides royalty-free cross-licenses for patents covering Linux and adjacent open-source projects
• IP due diligence on open-source components before adding them to the technology stack, particularly for tools without strong patent defense organizations behind them
• Insurance coverage for patent infringement claims, including whether existing general liability or technology E&O policies cover demands from patent assertion entities

The offensive-defensive patent divide

Previous actuary.info coverage of insurance patent strategy has focused on the offensive side: State Farm, USAA, and Allstate building a 77% concentration of insurer AI patents, AIG filing patents on agentic underwriting systems, EXL patenting insurance-specific LLM applications. These are carriers and vendors creating IP to protect their own innovations.

The IV dispute exposes the other side of the ledger. Carriers must also defend against patent claims on technology they did not create. This defensive exposure scales with technology adoption. The more aggressively a carrier modernizes its infrastructure, the more open-source tools it deploys, and the more surface area it creates for patent assertion campaigns.

This creates a tension in carrier IP strategy. On the offensive side, carriers want strong patent protection for their proprietary AI models and workflows. On the defensive side, carriers want weak patent protection for the infrastructure tools those models run on. The Section 101 eligibility framework that determines whether AI patents survive legal challenge also governs whether infrastructure patents can be enforced. A carrier that benefits from strong patent eligibility standards for its own AI filings faces the same strong standards when defending against infrastructure patent claims.

The resolution, as the DJ filings implicitly argue, lies in the specificity of the claims. Patents on novel AI applications tied to specific actuarial workflows are defensible. Patents on generic uses of containerization and orchestration tools, the kind Intellectual Ventures appears to hold, are not. The revised USPTO inventorship guidance and the Recentive Analytics precedent both push in this direction: toward rewarding technical specificity and punishing broad, functional claiming.

What to watch in 2026 and beyond

Several developments will shape how this dispute unfolds and what it means for the broader insurance industry.

Early motions in the Delaware and Massachusetts cases. Hartford’s invalidity challenge under Section 101 could produce an early ruling on whether IV’s infrastructure patents meet the post-Recentive eligibility standard. A motion to dismiss or early summary judgment on those grounds would resolve the dispute without full discovery, which is precisely the accelerated timeline the carriers are seeking.

Whether other targeted carriers join the fight. Nationwide, Liberty Mutual, and GEICO have reportedly received similar demands. If they file their own DJ actions, the coordinated defense expands and the cost-sharing dynamics improve further. If they settle quietly, IV pockets revenue that funds continued assertion against the holdouts.

The USPTO reexamination and IPR outcomes. The Unified Patents reexamination of the ’785 patent and Docker’s IPR of the ’844 patent are proceeding on separate tracks from the district court cases. Favorable outcomes at the Patent Trial and Appeal Board would narrow IV’s portfolio and weaken its negotiating position across all targets, not just insurers.

Cross-industry coordination. If JP Morgan, American Airlines, Home Depot, and Deere & Company are also fighting rather than settling, the combined defensive front becomes formidable. Joint defense groups and shared prior art resources reduce per-company costs and increase the probability of invalidating the asserted patents.

Legislative and regulatory response. The Patent Eligibility Restoration Act, reintroduced in the 119th Congress, would replace the Alice/Mayo framework with a statutory list of ineligible categories. If passed, it could either strengthen or weaken IV’s position depending on how the new standard treats infrastructure-level patents. The NAIC’s ongoing work on AI governance frameworks for insurance has not yet addressed the intersection of patent assertion risk and technology procurement, but the IV campaign may force that conversation.

Why this matters for actuaries

Patent litigation against carrier technology stacks has direct actuarial implications across several dimensions.

Technology expense assumptions. Actuarial pricing models embed assumptions about carrier operating costs, including technology expenses. If patent licensing fees become a recurring cost of maintaining open-source infrastructure, those assumptions need updating. A $3.5 million demand from one entity is a rounding error; serial demands from multiple entities targeting different components of the stack could become material.

Contingent liability disclosures. Hartford’s Q1 2026 10-Q, filed with the SEC, covers the period when the DJ action was filed. The legal proceedings section of carrier financial statements now includes IP litigation as a category alongside traditional insurance coverage disputes. Reserving actuaries tracking contingent liabilities should monitor whether patent defense costs appear as a line item.

Vendor risk in AI model deployment. Carriers building AI systems on top of open-source infrastructure face layered risk: the AI model itself may be patented (offensive IP), and the infrastructure running that model may also be subject to patent claims (defensive exposure). ASOP No. 56 on modeling requires consideration of material risks in model governance. If the infrastructure layer faces patent encumbrance, that risk belongs in the model documentation.

Technology procurement actuarial input. Enterprise risk management functions increasingly involve actuaries in technology investment decisions, particularly for AI systems subject to regulatory scrutiny. The patent exposure of the technology stack is a dimension of that risk assessment. Actuaries participating in ERM processes should understand that open-source does not mean patent-free.

The coordinated DJ filings by Hartford, Hanover, and Travelers mark a visible inflection point in how the insurance industry manages technology IP risk. Patterns we have tracked across the full AI patent landscape in insurance show carriers investing heavily in offensive patent strategies to protect proprietary AI. This dispute reveals the complementary requirement: a defensive strategy to protect the right to use the foundational tools that every AI system depends on.