Virtamove v. Oracle: Infringement Suit Over OCI Moves to Austin in 43 Days
Virtamove, Corp. asserted US7774762B2 against Oracle’s cloud container ecosystem — including OCI, OKE, and OCNE — in the Western District of Texas. Before any substantive ruling, the parties jointly stipulated to transfer the case to the Austin Division, where Judge Alan D. Albright will retain it on his docket.
Container IP assertion targets Oracle’s full cloud-native stack
On August 27, 2025, Virtamove, Corp. filed a patent infringement action against Oracle in the Western District of Texas, asserting US7774762B2 against a broad set of Oracle cloud-native products: Oracle Cloud Infrastructure (OCI), Oracle Cloud Infrastructure Container Registry, Oracle Cloud Native Environment (OCNE), and Oracle Kubernetes Engine (OKE). The case was assigned to Judge Alan D. Albright, a highly experienced patent jurist with a substantial patent docket in the Western District.
Just 43 days after filing, on October 9, 2025, the parties filed a joint motion and stipulation to transfer the case from its original division to the Austin Division of the same court. Judge Albright granted the motion, directing the Clerk to effectuate the transfer while expressly ordering that the case remain on his own docket. No merits-based rulings, claim construction orders, or dispositive motions appear to have been issued prior to the transfer.
The speed of the transfer — less than six weeks post-filing — and its joint, stipulated nature suggest the parties agreed on venue mechanics early, possibly to align with prior related proceedings or logistical convenience, rather than as a contested venue dispute. Critically, Judge Albright’s retention of the case means no disruption to judicial familiarity. The substantive infringement and validity questions remain entirely open, and the public record does not indicate whether any licensing negotiations are ongoing.
Filing to Case Transferred in 43 days
43 days from filing to transfer — resolved at the venue stage before any merits briefing
Joint transfer to Austin Division: what the venue change means for both parties
What a stipulated transfer order actually means
A stipulated transfer is not a dismissal or a merits ruling — it is a procedural agreement between the parties to move the case to a different division within the same court. Here, both Virtamove and Oracle jointly moved to relocate from the Waco Division to the Austin Division of the Western District of Texas. The court granted the motion without prejudice to any substantive rights. The case, the judge, and all claims survive intact.
No merits decidedVirtamove’s infringement claims remain fully alive
Virtamove retains all asserted claims under US7774762B2 against Oracle’s full cloud-native stack. The transfer does not affect the scope of the complaint, the products accused, or Virtamove’s ability to seek damages and injunctive relief. Because the parties stipulated jointly, this transfer is unlikely to reflect any strategic concession by Virtamove — rather, it suggests logistical alignment, possibly with related proceedings or counsel location.
Claims intactOracle moves venue but faces same judge and same claims
Oracle’s agreement to the transfer indicates it did not mount a venue challenge, or resolved any such concern by consent. Critically, the transfer order explicitly keeps the case on Judge Albright’s docket, meaning Oracle does not benefit from a change of judicial assignment. The full suite of accused products — OCI, Container Registry, OCNE, and OKE — remains at risk. Oracle’s substantive defences on infringement and validity are preserved but untested.
Same judge, different cityCloud container IP risk: the litigation clock has restarted in Austin
The transfer signals that this case is entering its substantive phase in Austin. For the broader cloud-native and Kubernetes ecosystem, the assertion of US7774762B2 against Oracle’s OCI stack is a marker worth monitoring. Container orchestration and virtualisation patents are increasingly active in litigation, and a damages or injunction outcome against OCI could reverberate across competing cloud providers offering similar container registry and managed Kubernetes services.
Cloud container IP risk elevatedFull party and counsel information
| Role | Name | Type | Detail |
|---|---|---|---|
| Plaintiff | Virtamove, Corp. | Company | Cloud software IP licensor — holder of US7774762B2 covering container-based application virtualisationSearch in Eureka ↗ |
| Defendant | Oracle | Individual | Oracle Corporation — provider of Oracle Cloud Infrastructure and cloud-native container servicesSearch in Eureka ↗ |
| Plaintiff counsel | Christian W. Conkle | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Daniel B. Kolko | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Jacob R. Buczko | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | James Milkey | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | James S. Tsuei | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Jefferson Cummings | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Jonathan Ma | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Linjun Xu | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Mackenzie Paladino | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Marc A. Fenster | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Neil A. Rubin | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Qi (Peter) Tong | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff counsel | Reza Mirzaie | Attorney | Counsel for Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff law firm | Russ August & Kabat LLP | Law Firm | Representing Virtamove, Corp.Search in Eureka ↗ |
| Plaintiff law firm | Russ August Kabat LLP | Law Firm | Representing Virtamove, Corp.Search in Eureka ↗ |
| Defendant counsel | Darryl Adams | Attorney | Counsel for OracleSearch in Eureka ↗ |
| Defendant law firm | Slayden Grubert Beard PLLC | Law Firm | Representing OracleSearch in Eureka ↗ |
| Presiding judge | Judge Alan D Albright | Judge | Texas Western District CourtSearch in Eureka ↗ |
Official order — verbatim text
The transfer order is purely procedural — the court found no substantive issue to resolve, simply directing the Clerk to move the case to the Austin Division while Judge Albright retains jurisdiction. The joint stipulation means neither party contested venue, and the order preserves all claims and defences. The phrase ‘will remain on the docket of United States District Judge Alan D Albright’ is the operationally significant language: it forecloses any tactical benefit from judicial reassignment that a divisional transfer might otherwise provide.
US7774762B2 — Container-based application isolation and virtualisation
US7774762B2, filed under application number US11/380285, covers technology in the domain of container-based application isolation and server virtualisation — a foundational area predating the mainstream containerisation wave associated with Docker and Kubernetes. The patent’s mid-2000s application vintage places its priority date in an era when lightweight OS-level virtualisation was an emerging alternative to hypervisor-based VMs. Its claims likely relate to methods or systems for isolating application environments within a shared operating system kernel — the conceptual ancestor of modern container runtimes.
The strategic significance of US7774762B2 lies in its potential to read on the core mechanisms of modern container orchestration platforms. Oracle’s accused products — OCI, Container Registry, OCNE, and OKE — collectively represent a complete cloud-native stack built on containerisation principles. If Virtamove’s claim mapping survives Markman, the royalty exposure across Oracle’s enterprise cloud customer base could be substantial. Competing cloud providers — AWS (EKS, ECR), Google (GKE, Artifact Registry), and Microsoft (AKS, ACR) — should evaluate whether the same claims present parallel exposure.
Should your cloud-native product team run an FTO against US7774762B2?
Any company building, licensing, or embedding container orchestration, managed Kubernetes, or container registry functionality should treat this case as a prompt for FTO review. Virtamove’s willingness to assert US7774762B2 against Oracle’s full OCI stack — one of the largest enterprise cloud platforms in the market — signals that the patent holder views the claim scope as commercially broad and litigation-ready. R&D and product teams shipping container-based workload isolation or image registry services are the primary exposure population.
PatSnap Eureka’s FTO Search Agent can map the independent and dependent claims of US7774762B2 against your product’s technical architecture, surface relevant prior art that may narrow the claims, and identify related family members or continuation applications that could extend the risk surface. Given the case’s early procedural stage — no Markman order has issued — now is the optimal window to run an FTO analysis before claim construction narrows or expands the operative claim language.
Run a freedom-to-operate analysis on US7774762B2 to assess your product’s exposure
Run FTO in Eureka →Similar container and cloud virtualisation patent cases in W.D. Texas
Cases involving container, Kubernetes, and cloud virtualisation patents before Judge Albright in the Western District of Texas, including related Virtamove assertions.
What this case signals for the cloud container IP landscape
Virtamove’s rapid, broad assertion against Oracle’s entire cloud-native stack reflects a sharpening focus on container and Kubernetes IP in enterprise cloud litigation.
Judge Albright retains the case: no benefit from judicial reassignment
Despite the divisional transfer, Oracle faces the same experienced patent judge. Albright’s retention removes a common tactical benefit of venue transfer. Any party monitoring this case — or involved in related proceedings — should assume full Albright-style case management, including aggressive scheduling and early Markman hearings, will apply in Austin.
Four accused Oracle products signal a broad damages theory
Virtamove named OCI, Container Registry, OCNE, and OKE — Oracle’s full cloud-native orchestration and container stack. Accusing the entire ecosystem rather than a single product typically signals that the plaintiff is pursuing a large royalty base. IP teams at competing cloud providers offering comparable container services should assess their own exposure to US7774762B2.
Virtamove v Oracle — key questions answered
The case was transferred to the Austin Division of the Western District of Texas on October 9, 2025, pursuant to a joint stipulation by the parties. Judge Alan D. Albright retains the case on his docket. No merits rulings have issued; all infringement and validity questions remain open.
Virtamove accused four Oracle products: Oracle Cloud Infrastructure (OCI), Oracle Cloud Infrastructure Container Registry, Oracle Cloud Native Environment (OCNE), and Oracle Kubernetes Engine (OKE). The complaint targets Oracle’s full cloud-native container and orchestration stack.
The transfer is procedural and does not affect any substantive rights. The case moves from one division of the Western District of Texas to another. Crucially, Judge Albright’s retention of the case means judicial familiarity is preserved and no reassignment advantage accrues to either party. The litigation continues on its full merits.
US7774762B2, filed under application US11/380285, relates to container-based application isolation and server virtualisation technology. Its mid-2000s filing predates Docker and Kubernetes, potentially giving it broad claim language that could read on modern container runtime and orchestration mechanisms used in managed cloud services like OCI, OKE, and competing platforms.
Potentially, yes. The patent’s technical domain — container-based application isolation — is foundational to managed Kubernetes services and container registries across all major cloud providers. AWS EKS, Google GKE, and Microsoft AKS all operate on comparable architectural principles. Until a Markman order defines the operative claim scope, assessing exposure via FTO analysis is advisable for any provider in this space.
PatSnap Eureka searches patents and litigation data to answer instantly.