VirtaMove Corp v. Google LLC

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: VirtaMove, Corp. (Canada)
  • Defendant: Google, LLC (Delaware)
  • Plaintiff's Counsel: Russ August & Kabat
• Case Identification: 5:25-cv-00860-NW, N.D. Cal., 07/27/2026
• Venue Allegations: Plaintiff alleges venue is proper in the Northern District of California because Defendant has a principal place of business in the District and has committed acts of infringement there, including importing, offering to sell, and selling the accused products.
• Core Dispute: Plaintiff alleges that Defendant's cloud and containerization products, including Google Migrate to Containers and Google Kubernetes Engine, infringe patents related to application containerization and executing applications on incompatible platforms.
• Technical Context: The technology at issue is application containerization, a method of packaging software with its dependencies to run reliably across different computing environments, which is foundational to modern cloud computing and application deployment.
• Key Procedural History: The complaint alleges that representatives of VirtaMove and Google met in 2015, 2020, and 2021 to discuss a potential partnership, during which VirtaMove demonstrated its patented V-Migrate software. These meetings are presented as the basis for Google's alleged pre-suit knowledge of the technology and potential willful infringement.

Case Timeline

Date	Event
2003-09-15	Earliest Priority Date for '814 and '762 Patents
2009-04-14	U.S. Patent No. 7,519,814 Issues
2010-08-10	U.S. Patent No. 7,774,762 Issues
2015-01-01	VirtaMove and Google representatives meet (approx.)
2020-01-01	VirtaMove and Google representatives meet (approx.)
2021-01-01	VirtaMove and Google representatives meet (approx.)
2026-07-27	Complaint Filed

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 7,519,814 - "System for Containerization of Application Sets"

• Patent Identification: U.S. Patent No. 7,519,814, "System for Containerization of Application Sets," issued April 14, 2009.

The Invention Explained

• Problem Addressed: The patent addresses the problem that different software applications often have conflicting requirements (e.g., for specific OS versions or resources), forcing them to be deployed on separate, individual computer systems, which is costly and inefficient Compl. ¶14 '814 Patent, col. 1:36-50 While virtual machines (VMs) offer a solution, they impose significant performance overhead and management complexity because each VM requires a full, separate operating system '814 Patent, col. 1:51-62
• The Patented Solution: The invention proposes a method of creating portable "secure containers" that package an application with its necessary system files but exclude the operating system kernel '814 Patent, abstract These lightweight containers can run in isolation on a single host OS, sharing its kernel, which allows multiple, otherwise-conflicting applications to coexist on one server with greater efficiency and lower overhead than traditional VMs '814 Patent, col. 1:63-2:3
• Technical Importance: This approach enabled the consolidation of disparate server applications onto a smaller number of physical machines, reducing hardware and management costs '814 Patent, col. 2:12-15

Key Claims at a Glance

• The complaint asserts claims 1, 2, 4, 6, 9, 10, 13, and 14 Compl. ¶18
• Independent Claim 1, a method claim, includes the following essential elements:
  • Storing in memory a plurality of secure containers of application software.
  • Each container comprising one or more executable applications and a set of associated system files required for execution.
  • The containers are for use with a local kernel residing on a server and exclude a kernel themselves.
  • Application software cannot be shared between the secure containers.
  • Each container has a unique root file system that is different from the host operating system's root file system.

U.S. Patent No. 7,774,762 - "System Including Run-Time Software to Enable a Software Application to Execute on an Incompatible Computer Platform"

• Patent Identification: U.S. Patent No. 7,774,762, "System Including Run-Time Software to Enable a Software Application to Execute on an Incompatible Computer Platform," issued August 10, 2010.

The Invention Explained

• Problem Addressed: Software applications are often designed for a specific computer platform (i.e., a particular operating system) and cannot run on other, "incompatible" platforms without being rewritten, which can take "weeks, months or years" Compl. ¶25 '762 Patent, col. 1:43-64
• The Patented Solution: The invention provides a system to run an application on an incompatible platform using a "capsule" and "capsule runtime software" '762 Patent, abstract The capsule contains the application along with the specific files (e.g., libraries) from its original environment '762 Patent, col. 2:19-33 The runtime software, which includes a kernel module and filter libraries, intercepts system service requests from the application and provides "capsule specific values" or redirects file access to the files within the capsule, effectively tricking the application into running on the foreign host OS '762 Patent, col. 2:34-49
• Technical Importance: The technology facilitates the modernization of legacy software by allowing older applications to run on new hardware and operating systems without costly and time-consuming recoding efforts '762 Patent, col. 1:54-64

Key Claims at a Glance

• The complaint asserts an independent claim Compl. ¶29
• Independent Claim 1, a system claim, includes the following essential elements:
  • A set of associated capsule-related files, comprising the first software application and a second group of files (e.g., libraries) specific to its original operating system.
  • Capsule runtime software for managing the state and file location of the application.
  • The runtime software includes a kernel module and at least one application filter library.
  • The filter library is for filtering system service requests and providing modified values, such that execution uses the capsule-related files instead of the host's local system files.

III. The Accused Instrumentality

Product Identification

• The complaint names several accused products and services, primarily Google's "Migrate to Containers" tool Compl. ¶15 Other accused instrumentalities include Google Kubernetes Engine (GKE), GKE Autopilot, GKE Enterprise, Cloud Run, Google Container Registry, Google Artifact Registry, and the Google Cloud Platform Compl. ¶15 Compl. ¶26

Functionality and Market Context

• The complaint alleges that "Migrate to Containers" is a tool for modernizing traditional applications by moving them from virtual machine (VM) instances into "native containers" that run on Google's cloud platforms like GKE and Cloud Run Compl. p. 6
• This functionality allows customers to "containerize" existing workloads from environments like VMware or Compute Engine VMs, including applications such as IBM WebSphere, JBoss, Apache, and WordPress Compl. p. 6 The complaint presents this as a key part of Google's cloud modernization strategy Compl. ¶11 Compl. ¶12
• The complaint includes a "Virtualization Landscape" diagram from a 2009 Gartner report, which positions Plaintiff's predecessor (AppZero) as having "No direct competition" in the server-based application virtualization space, distinct from machine or OS virtualization competitors like VMWare Compl. p. 4

IV. Analysis of Infringement Allegations

The complaint states that claim charts are attached as exhibits but does not include them in the provided document Compl. ¶18 Compl. ¶29 The infringement theory is therefore summarized below in prose.

• '814 Patent Infringement Allegations: The complaint alleges that Google's "Migrate to Containers" product performs the patented method of containerization Compl. ¶15 The core of the allegation is that when a user employs this tool to modernize a VM-based application, the tool analyzes the application and its dependencies and packages them into a container that runs on GKE or Cloud Run Compl. p. 6 Plaintiff's theory appears to be that this process of creating a portable, isolated application package that shares a host kernel constitutes infringement of the method claims of the '814 Patent.
• '762 Patent Infringement Allegations: The complaint alleges that a broader set of Google products, including GKE, Cloud Run, and Migrate to Containers, infringe the '762 Patent Compl. ¶26 The infringement theory suggests that Google's cloud ecosystem functions as the claimed system for running an application on an incompatible platform. In this narrative, a traditional VM environment is the "first computer platform," and Google's Kubernetes-powered cloud is the "incompatible computer platform" Compl. p. 9 The combination of a container created by "Migrate to Containers" (the "capsule") and the GKE/Cloud Run environment (the "runtime software") is alleged to provide the filtering and redirection necessary to make the application run, thereby infringing the system claims of the '762 Patent.
• Identified Points of Contention:
  • Technical Questions: A central factual dispute will likely concern the precise technical operation of Google's products. For the '814 Patent, a question is whether Google's process creates a "secure container" with a "unique root file system" as required by Claim 1. For the '762 Patent, a question is whether GKE and its associated components perform the specific functions of the claimed "capsule runtime software," such as filtering system calls and providing modified values.
  • Scope Questions: For the '762 Patent, a primary legal question will be one of claim scope: does the term "incompatible computer platform" cover the migration from a VM-based environment to a Kubernetes-based container orchestration platform? The interpretation of this term may be dispositive for the infringement analysis of the '762 Patent.

V. Key Claim Terms for Construction

• Term: "secure containers of application software" ('814 Patent, Claim 1)

  • Context and Importance: This term is the central object of the '814 Patent's claimed method. The definition will be critical for determining whether the containers generated by Google's "Migrate to Containers" tool fall within the scope of the claims.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The specification provides a functional definition, stating a "secure application container" is an environment where an application set is "insulated from effects of other application sets" '814 Patent, col. 2:37-43 This could support a reading based on the functional outcome of isolation.
    • Evidence for a Narrower Interpretation: Claim 1 itself adds structural limitations, requiring the container to have a "unique root file system that is different from an operating system's root file system" and to "exclud[e] a kernel" '814 Patent, col. 18:52-61 The specification also distinguishes the invention from VMs, which could be used to argue for a definition that is distinct from other known virtualization technologies '814 Patent, col. 1:51-2:3

• Term: "incompatible computer platform" ('762 Patent, Claim 1)

  • Context and Importance: The purpose of the '762 Patent is to enable execution on an "incompatible" platform. If Google's GKE is not considered "incompatible" with the source VM environment, there may be no infringement. Practitioners may focus on this term as it is fundamental to the applicability of the patent to the accused scenario.
  • Intrinsic Evidence for Interpretation:
    • Evidence for a Broader Interpretation: The patent provides examples of incompatibility between different versions of the same OS family, such as "Solaris version 2.6" on a "Solaris 9 platform" '762 Patent, col. 2:50-54 This suggests "incompatible" does not require completely different OS types (e.g., Linux vs. Windows) and could support a broader reading that includes different architectural paradigms like VMs versus Kubernetes.
    • Evidence for a Narrower Interpretation: The background section describes the problem as applications being "designed to run on a specific computer platform" and being unable to run on others '762 Patent, col. 1:43-46 This could support a narrower definition tied to fundamental OS-level or instruction set architecture conflicts, rather than differences in higher-level management and orchestration frameworks.

VI. Other Allegations

• Indirect Infringement: The complaint alleges induced infringement for both patents, asserting that Google "actively encourage[s] and instruct[s] its customers and end users (for example, through user manuals and online instruction materials on its website)" to use the accused products in ways that directly infringe Compl. ¶17 Compl. ¶28
• Willful Infringement: The complaint alleges willfulness based on pre-suit knowledge. It claims that during meetings in 2015, 2020, and 2021, VirtaMove demonstrated its technology to Google, and that "Google would have learned that VirtaMove entities marketed and/or advertised that V-Migrate software was patented" or was willfully blind Compl. ¶9 It also alleges continued infringement after the filing of the original complaint provides direct notice Compl. ¶17 Compl. ¶28

VII. Analyst's Conclusion: Key Questions for the Case

1. Definitional Scope: A central issue will be whether the term "incompatible computer platform" in the '762 Patent, which the specification illustrates with examples of different OS versions, can be construed to cover the plaintiff's alleged scenario of migrating an application from a traditional virtual machine environment to a modern Kubernetes-based cloud platform.

2. Technical Equivalence: A key evidentiary question will be one of functional operation. Does Google's accused ecosystem, particularly the combination of "Migrate to Containers" and the "Google Kubernetes Engine," perform the specific technical functions required by the asserted claims, such as creating a "secure container" with a "unique root file system" ('814 Patent) and employing "capsule runtime software" that filters system calls to provide modified values ('762 Patent)?

3. Willfulness and Pre-Suit Knowledge: The viability of the willfulness claim will depend on the factual evidence surrounding the alleged 2015-2021 meetings between the parties. A critical question for the court will be what was specifically disclosed to Google during these meetings and whether that disclosure was sufficient to put Google on notice of the asserted patents, or to create a duty to investigate that it allegedly disregarded.