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.
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.
Filing to Voluntary dismissal in 37 days
37 days from filing to closure — well below the median E.D. Tex. patent case lifespan
Dismissed with prejudice: what the voluntary exit means for both parties
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)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 extinguishedAtlassian 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 awardedWhat 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 enforceableFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | HyperQuery LLC | Company | Patent assertion entity — holder of US9529918B2 covering app download network systemsSearch in Eureka ↗ |
| Defendant | Atlassian Pty Ltd | Company | Atlassian Pty Ltd — Australian enterprise software company; maker of Jira, Confluence, and related toolsSearch in Eureka ↗ |
| Plaintiff counsel | Isaac Phillip Rabicoff | Attorney | Counsel for HyperQuery LLCSearch in Eureka ↗ |
| Plaintiff law firm | Rabicoff Law LLC | Law Firm | Representing HyperQuery LLCSearch in Eureka ↗ |
| Presiding judge | Judge N/A | Judge | Texas Eastern District CourtSearch in Eureka ↗ |
Official order — verbatim text
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.
US9529918B2 — System and methods for downloading applications via a communication network
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.
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.
Run a freedom-to-operate analysis on US9529918B2 to assess your product’s exposure
Run FTO in Eureka →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.
Related patent case — similar technology
Comparable case in the same technology domain. Patent holder and defendant reached resolution after proceedings.
SettledRelated infringement action — same court
Comparable System and methods thereof for downloading applications via a communication network-adjacent infringement action. Patent enforcement dynamics analysed in depth.
Active · District CourtRelated invalidity challenge — appellate outcome
Combined invalidity and infringement action in the same technology space. Decided after substantive proceedings.
DecidedHyperQuery LLC’s broader IP enforcement history
HyperQuery LLC’s full litigation history covering prior enforcement, licensing activity, and inter partes review proceedings.
Portfolio viewWhat 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.
E.D. Tex. remains a strategic venue for PAE assertions
The Eastern District of Texas continues to attract patent assertion entity filings. HyperQuery’s choice of this venue for a claim against an Australian defendant is consistent with the court’s plaintiff-friendly reputation. Legal teams defending software IP in this district should prepare for accelerated early-stage pressure.
US9529918B2 claim scope warrants FTO scrutiny for SaaS platforms
The asserted patent covers systems and methods for downloading applications via a communication network — broad language that could encompass app marketplace functionality, cloud deployment pipelines, or SaaS onboarding flows. R&D and product teams at enterprise software companies should assess their exposure before a demand letter arrives.
HyperQuery v Atlassian — key questions answered
A dismissal with prejudice permanently bars HyperQuery LLC from refiling the same patent infringement claims against Atlassian Pty Ltd based on US9529918B2. The court accepted HyperQuery’s voluntary notice under Rule 41(a)(1)(A)(i) and closed the case. No merits determination was made — the patent was neither validated nor invalidated.
HyperQuery LLC asserted US9529918B2 (application number US14/103500), which covers systems and methods for downloading applications via a communication network. The patent was the sole intellectual property asset asserted in this complaint filed in the Eastern District of Texas.
The public record does not disclose the reason for the rapid dismissal — 37 days after filing, before Atlassian filed any response. This pattern is consistent with cases that resolve through private licensing negotiations or settlement agreements reached off the public docket. It may also reflect a reassessment of claim strength, though no such finding appears on the record.
No. The dismissal with prejudice applies only to claims against Atlassian Pty Ltd. US9529918B2 remains an enforceable patent, and HyperQuery LLC retains the right to assert it against other defendants. Enterprise software vendors and app distribution platforms should not interpret this outcome as a neutralisation of the patent’s enforcement potential.
HyperQuery LLC was represented by Isaac Phillip Rabicoff of Rabicoff Law LLC. The firm is associated with patent assertion entity litigation, frequently representing plaintiffs in infringement actions in plaintiff-favoured venues including the Eastern District of Texas. No defendant agents or law firms were listed on the docket for this case.
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.
PatSnap Eureka searches patents and litigation data to answer instantly.