Book a demo

Cut patent&paper research from weeks to hours with PatSnap Eureka AI!

Try now
HyperQuery LLC v. Atlassian Pty Ltd — Patent Infringement Dismissed | PatSnap
Explore in Eureka
Case ID2:25-cv-00037
FiledJan 2025
ClosedFeb 2025
Patent Litigation

HyperQuery LLC v. Atlassian Pty Ltd — Dismissed With Prejudice in 37 Days

HyperQuery LLC asserted US9529918B2 — covering systems and methods for downloading applications via a communication network — against Atlassian Pty Ltd in the Eastern District of Texas. The plaintiff voluntarily dismissed the case with prejudice just 37 days after filing, before Atlassian had filed any response.

Resolution time
37days
37 days from filing to closure — well below the median E.D. Tex. patent case lifespan
Patents asserted
1
US9529918B2 — system and methods for downloading applications via a communication network
Outcome
Voluntary dismissal
Plaintiff voluntarily dismissed with prejudice under Rule 41(a)(1)(A)(i); claims permanently barred
Cost ruling
Own Costs
Court ordered each party to bear its own costs, expenses, and attorneys’ fees
Published by PatSnap Insights Team · Verified by PatSnap Eureka Data
Case overview

A swift voluntary exit: HyperQuery drops Atlassian suit with finality

On January 15, 2025, HyperQuery LLC filed a patent infringement complaint against Atlassian Pty Ltd in the Eastern District of Texas (Case No. 2:25-cv-00037), asserting US9529918B2, which covers systems and methods for downloading applications via a communication network. HyperQuery is represented by Isaac Phillip Rabicoff of Rabicoff Law LLC, a firm with an established presence in patent assertion matters. Atlassian, the Australian enterprise software company behind products such as Jira and Confluence, did not file an answer or move for summary judgment before the case ended.

On February 21, 2025 — just 37 days after filing — HyperQuery filed a Notice of Voluntary Dismissal with Prejudice. The court accepted the notice and, pursuant to Rule 41(a)(1)(A)(i), dismissed all pending claims with prejudice. Each party was ordered to bear its own costs, expenses, and attorneys’ fees. A dismissal with prejudice is a final adjudication on the merits: HyperQuery cannot re-file these same claims against Atlassian based on the same patent.

The speed of this resolution — 37 days, before any substantive response from the defendant — is consistent with cases that settle or resolve through private agreement shortly after filing. The public record does not disclose whether any consideration changed hands between the parties. What is clear is that HyperQuery chose permanent closure over continued litigation, which may reflect a licensing resolution, a strategic reassessment of claim strength, or other undisclosed commercial factors.

Case at a glance
Case no.2:25-cv-00037
CourtTexas Eastern
JudgeN/A
FiledJanuary 15, 2025
ClosedFebruary 21, 2025
Duration37 days
OutcomeVoluntary dismissal
Verdict causeInfringement Action
BasisVoluntary dismissal
Prior Art Intelligence
See what prior art exists on this patent.
Eureka scans millions of patents and papers to surface prior art that may have invalidated these claims before costly litigation begins.
Check Prior Art
Case data sourced from PACER / Texas Eastern District Court via PatSnap Eureka Litigation Intelligence Explore similar cases ↗
Case timeline

Filing to Voluntary dismissal in 37 days

37 days from filing to closure — well below the median E.D. Tex. patent case lifespan

Case timeline: Complaint filed JAN 15 2025, FEB–MAR — 37 days total Horizontal timeline showing the three key events in HyperQuery LLC v Atlassian Pty Ltd from filing to resolution. Source: PACER, Texas Eastern District Court. JAN 15 2025 Complaint filed Pre-trial proceedings FEB 21 2025 Voluntary dismissal 37 DAYS TOTAL
Dismissal terms

Dismissed with prejudice: what the voluntary exit means for both parties

Legal mechanism

Rule 41(a)(1)(A)(i): plaintiff’s unilateral right to dismiss

Under Rule 41(a)(1)(A)(i), a plaintiff may voluntarily dismiss a case without a court order before the defendant has served an answer or moved for summary judgment. Here, Atlassian had not yet responded, so HyperQuery exercised this right. Because the notice specified ‘with prejudice,’ the court treated it as a final adjudication — permanently extinguishing HyperQuery’s ability to reassert these claims against Atlassian.

Procedural — Rule 41(a)(1)(A)(i)
Plaintiff outcome

HyperQuery permanently forfeits these claims against Atlassian

By dismissing with prejudice, HyperQuery voluntarily gave up its most significant litigation right: the ability to refile. This is an unusually strong concession for a plaintiff who controls the timing. It may indicate that the parties reached a private resolution — such as a licensing agreement — making continued litigation unnecessary, or that HyperQuery reassessed the merits of its infringement position. The public record does not confirm either interpretation.

Claims permanently extinguished
Defendant outcome

Atlassian exits without filing a single pleading

Atlassian Pty Ltd was never required to answer the complaint or engage in substantive litigation. The dismissal with prejudice provides Atlassian with a strong procedural shield: the same plaintiff cannot reassert the same patent claims in a new action. The court’s ruling that each party bears its own costs means Atlassian recovers no fees, which is the default outcome under U.S. patent law absent an ‘exceptional case’ finding.

No liability, no costs awarded
Commercial implications

What this outcome signals for app-download patent assertions

Quick voluntary dismissals with prejudice — particularly before any defendant response — are a recurring pattern in patent assertion entity litigation and often suggest a licensing resolution reached off the docket. For competitors in the enterprise software and application distribution space, this case is a reminder that US9529918B2 remains an active patent asset. Other defendants facing similar assertions from HyperQuery or related entities should monitor the portfolio’s litigation history closely.

Patent remains enforceable
Legal analysis based on PACER docket records for case 2:25-cv-00037 and PatSnap Eureka litigation intelligence Search PatSnap Eureka ↗
Parties and representation

Full party and counsel information

RoleNameTypeDetail
PlaintiffHyperQuery LLCCompanyPatent assertion entity — holder of US9529918B2 covering app download network systemsSearch in Eureka ↗
DefendantAtlassian Pty LtdCompanyAtlassian Pty Ltd — Australian enterprise software company; maker of Jira, Confluence, and related toolsSearch in Eureka ↗
Plaintiff counselIsaac Phillip RabicoffAttorneyCounsel for HyperQuery LLCSearch in Eureka ↗
Plaintiff law firmRabicoff Law LLCLaw FirmRepresenting HyperQuery LLCSearch in Eureka ↗
Presiding judgeJudge N/AJudgeTexas Eastern District CourtSearch in Eureka ↗
Official verdict

Official order — verbatim text

“Before the Court is the Notice of Voluntary Dismissal with Prejudice (the “Notice”) filed by Plaintiff HyperQuery LLC (“Plaintiff”). (Dkt. No. 6.) In the Notice, Plaintiff represents that the above-captioned case against is voluntarily dismissed with prejudice. (Id. at 1.) Defendant Atlassian Pty Ltd. has not yet answered the Complaint or moved for summary judgment. In light of the Notice, which the Court ACCEPTS AND ACKNOWLEDGES, and pursuant to Rule 41(a)(1)(A)(i), all pending claims and causes of action in the abovecaptioned case are DISMISSED WITH PREJUDICE. All pending requests for relief in the above-captioned case not explicitly granted herein are DENIED AS MOOT. Each party is to bear its own costs, expenses, and attorneys’ fees. The Clerk of Court is directed to CLOSE the above-captioned case as no parties or claims remai”
Source: PACER Docket, Case 2:25-cv-00037, Texas Eastern District Court

The court’s order accepted HyperQuery’s Rule 41(a)(1)(A)(i) notice and dismissed all claims with prejudice — the strongest form of voluntary exit available to a plaintiff. Critically, this is not a merits ruling: no court found the patent valid or invalid, and no infringement determination was made. The ‘with prejudice’ designation is significant because it is self-imposed by the plaintiff and forecloses any future refiling of these specific claims against Atlassian. The costs order — each party to bear its own — is standard in Rule 41 dismissals absent exceptional circumstances.

PACER case 2:25-cv-00037 · Public docket record Explore in Eureka ↗
Patent at issue

US9529918B2 — System and methods for downloading applications via a communication network

Publication No.US9529918B2
Application No.US14/103500
Patent details
ProductSystem and methods for downloading applications via a communication network
Cited in actionJanuary 15, 2025

US9529918B2 (application number US14/103500) covers systems and methods for downloading applications via a communication network. This category of patent — broadly framed around networked application delivery — sits at the intersection of app marketplace infrastructure, cloud software distribution, and SaaS platform architecture. The application predates many modern cloud-native deployment paradigms, suggesting it may capture foundational methods that contemporary platforms implement without differentiation.

For the enterprise software sector, a patent covering networked application download systems presents meaningful exposure to vendors operating app marketplaces, plugin ecosystems, or cloud-based software delivery pipelines. Atlassian’s product suite — which includes marketplace-distributed integrations and cloud-hosted applications — is precisely the category of technology such claims are typically directed toward. That this case closed before Atlassian filed any response leaves the patent’s validity and claim scope entirely untested by adversarial proceedings.

Patent data sourced from USPTO via PatSnap Eureka patent database Search patent records in Eureka ↗
Freedom to operate

Should you run an FTO analysis against US9529918B2?

Any enterprise software company, SaaS vendor, or cloud application distribution platform that facilitates the download or delivery of applications via a network should assess its exposure to US9529918B2. The patent’s broad subject matter — systems and methods for networked app delivery — could potentially read on app marketplace functionality, plugin distribution mechanisms, automated update pipelines, or cloud-based onboarding flows. The fact that this case resolved before any claim construction or invalidity analysis means the patent’s scope has never been judicially tested.

PatSnap Eureka’s FTO Search Agent can map US9529918B2’s independent claims against your product architecture, flag overlapping prior art that could support an invalidity challenge, and surface related HyperQuery LLC patents in the same family or portfolio. Running an FTO now — before a demand letter or new filing — gives your legal and product teams the lead time needed to design around, license proactively, or build an invalidity record.

PatSnap Eureka FTO Search

Run a freedom-to-operate analysis on US9529918B2 to assess your product’s exposure

Run FTO in Eureka →
Related litigation

Similar patent infringement cases: app download systems in E.D. Texas

Cases involving networked application download and distribution patents litigated in the Eastern District of Texas, including other patent assertion entity actions against enterprise software defendants.

🔍
Access 40+ similar cases in PatSnap Eureka
HyperQuery LLC patent enforcement history, Texas Eastern case history, HyperQuery LLC’s full IP portfolio, and comparable case analysis
HyperQuery v. other defendantsApp download patent cases E.D. Tex.PAE actions vs. SaaS platformsUS9529918B2 related litigation
Unlock similar cases in Eureka →
Strategic implications

What this case signals for the enterprise software patent assertion landscape

A 37-day lifecycle and a prejudice-laden exit raise pointed questions about patent assertion strategy and licensing economics in the app-delivery sector.

Dismissed with prejudice ≠ no risk — the patent survives

HyperQuery’s dismissal bars only claims against Atlassian. US9529918B2 remains fully enforceable against other parties. Enterprise software vendors and cloud application distribution platforms should treat this case as an early indicator of the patent’s litigation trajectory, not a signal that the risk has passed.

Pre-answer dismissals often mask private licensing activity

When a plaintiff dismisses with prejudice before any defendant filing — as here — it frequently reflects an undisclosed agreement rather than a unilateral retreat. IP and legal teams monitoring HyperQuery LLC should track whether similar short-lifecycle cases appear against other defendants in the app-download or SaaS distribution space.

🔒
Full strategic analysis in PatSnap Eureka
Unlock PAE assertion trends in the Eastern District of Texas and full claim-scope analysis for US9529918B2 across enterprise software defendants.
E.D. Tex. PAE filing trendsHyperQuery portfolio mapApp download patent claim scope
Unlock full analysis →
Analysis powered by PatSnap Eureka Litigation Intelligence Explore in Eureka ↗
Frequently asked questions

HyperQuery v Atlassian — key questions answered

Still have questions? PatSnap Eureka can answer them instantly from patent and litigation data. Ask Eureka ↗
PatSnap Eureka

Monitor app-download patent assertions before the next filing hits

US9529918B2 is still live and enforceable. PatSnap Eureka helps you track HyperQuery LLC’s portfolio, run FTO searches against your product stack, and monitor new Eastern District of Texas filings in real time.

Ask anything about this case.
PatSnap Eureka searches patents and litigation data to answer instantly.
Powered by PatSnap Eureka
Link copied to clipboard

Related Litigation Cases

Help us improve this page

Found incorrect or outdated information? Let us know and we'll get it fixed.