People Center Inc v. Anysource Inc

I. Executive Summary and Procedural Information

• Parties & Counsel:
  • Plaintiff: People Center, Inc., d/b/a Rippling (Delaware)
  • Defendant: Anysource, Inc., d/b/a Runlayer (Delaware)
  • Plaintiff's Counsel: Young Conaway Stargatt & Taylor, LLP
• Case Identification: 1:26-cv-01007, D. Del., 08/10/2026
• Venue Allegations: Venue is alleged to be proper in the District of Delaware as the Defendant, Runlayer, is a Delaware corporation and thus a resident and corporate citizen of the district.
• Core Dispute: Plaintiff alleges that Defendant's platform for deploying and using AI agents infringes three patents related to computer-implemented methods for integrating third-party applications, synchronizing organizational data, and automating workflows using data-driven triggers.
• Technical Context: The technology at issue involves enterprise software platforms designed to unify disparate business management tools (e.g., human resources, IT, finance) into a single, cohesive system, thereby eliminating data silos and manual integration efforts.
• Key Procedural History: The complaint states that U.S. Patent No. 12,032,940 is a continuation of the application that led to U.S. Patent No. 11,435,994, indicating they share a common specification. Plaintiff also alleges to have provided Defendant with notice of the asserted patents via email on August 9, 2026, one day prior to filing the complaint.

Case Timeline

Date	Event
2016-01-01	Rippling was founded
2021-07-01	Priority Date for '994 and '940 Patents
2021-07-22	Priority Date for '941 Patent
2022-09-06	U.S. Patent No. 11435994 Issued
2023-10-17	U.S. Patent No. 11,789,941 Issued
2024-07-09	U.S. Patent No. 12032940 Issued
2026-08-09	Plaintiff allegedly sent notice email to Defendant
2026-08-10	Complaint Filed

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

U.S. Patent No. 11,435,994

• Patent Identification: U.S. Patent No. 11,435,994, titled "Multi-Platform Application Integration and Data Synchronization," issued on September 6, 2022.

The Invention Explained

• Problem Addressed: The patent addresses the problem of "siloed data and software systems" within organizations that use multiple, unintegrated software applications Compl. ¶17 This situation leads to inconsistent and inaccurate organizational information, requiring "endless manual updates and numerous, bespoke software integrations" to maintain data consistency '994 Patent, col. 1:15-33
• The Patented Solution: The invention is a computer-implemented method for integrating data from various third-party applications into a central computing system that serves as the organization's "data of record" Compl. ¶25 The system obtains data from a third-party application, analyzes it based on rules and integration information, and processes it. The rules are determined by analyzing data structures, including an "object graph data structure" that defines entities and their relationships, such as permissions for groups of employees '994 Patent, cl. 1 This allows the system to perform operations and synchronize data across multiple applications (Compl. ¶19; Compl. ¶20, Compl. ¶abstract).
• Technical Importance: The patented method is described as a "rigorous computerized process" that provides more efficient integration and synchronization of organizational data across different applications, using fewer computing resources than conventional manual or custom-built processes Compl. ¶¶19-20

Key Claims at a Glance

• The complaint asserts independent Claim 1 Compl. ¶25
• The essential elements of Claim 1, a computer-implemented method, include:
  • obtaining third-party application data from an application separate from a central computing system that maintains organizational data as a "data of record";
  • determining whether to obtain other third-party application data from a different third-party application;
  • generating and providing information associated with the organizational data to a plurality of other third-party applications;
  • analyzing the third-party application data based on rules, where the rules are determined by analyzing data structures, at least one of which is an "object graph data structure" that indicates permissions for a "first group of employees" relative to devices;
  • processing the third-party application data based on integration information and organizational structure data;
  • performing operations associated with the organizational data based on the processing; and
  • providing information associated with the organizational data to other third-party applications.
• The complaint focuses its allegations on at least Claim 1 Compl. ¶26

U.S. Patent No. 12,032,940

• Patent Identification: U.S. Patent No. 12,032,940, titled "Multi-Platform Application Integration and Data Synchronization," issued on July 9, 2024. The complaint notes this patent is a continuation of the '994 patent and shares a common specification Compl. ¶16

The Invention Explained

• Problem Addressed: The '940 patent addresses the same problem as the '994 patent: the inefficiencies, inaccuracies, and "delays, inconsistencies, and errors" caused by siloed enterprise software systems that are not integrated '940 Patent, col. 1:23-41 '940 Patent, col. 3:65-4:5
• The Patented Solution: Like the '994 patent, the '940 patent describes a method for third-party application integration. It focuses on analyzing data structures to generate rules for access rights, then analyzing and processing third-party application data based on those rules and an "object graph data structure" that defines entities and permissions '940 Patent, cl. 1 The complaint characterizes this patent as addressing the "other side of integration" by claiming ways to integrate third-party data into organizational data Compl. ¶19
• Technical Importance: The technology provides a "high-throughput, resilient, and rapid synchronization of organizational data across distributed applications," improving upon expensive and brittle proprietary integration solutions '940 Patent, col. 4:35-41

Key Claims at a Glance

• The complaint asserts independent Claim 1 Compl. ¶36
• The essential elements of Claim 1, a computer-implemented method, include:
  • obtaining third-party application data from an application separate from a computing system that maintains organizational data as a centralized "system of record";
  • analyzing data structures associated with the organizational data to generate rules for access rights;
  • analyzing the third-party application data based on these rules and data structures, where at least one structure is an "object graph data structure" indicating permissions for a "first group of employees";
  • processing the third-party application data based on integration information; and
  • performing operations associated with the organizational data based on the processing.
• The complaint focuses its allegations on at least Claim 1 Compl. ¶37

Multi-Patent Capsule: U.S. Patent No. 11,789,941

• Patent Identification: U.S. Patent No. 11789941, titled "Systems, Methods, Applications, and User Interfaces for Providing Triggers in a System of Record," issued on October 17, 2023.
• Technology Synopsis: The patent addresses the problem of organizational data becoming "out of sync" when managed separately across different third-party applications Compl. ¶22 The patented solution is a computer system and method that uses a "trigger" to support inter-application integration, where the trigger includes "conditions for activation" and a "set of one or more operations" to be executed based on a custom query language (Compl. ¶23, citing '941 Patent, col. 48:41-52:26).
• Asserted Claims: The complaint asserts independent Claim 1 Compl. ¶47
• Accused Features: The complaint alleges that Runlayer's platform infringes by relying on "triggers that are evaluated based on organizational data" Compl. ¶12, and that the Runlayer platform as a whole meets the limitations of the claimed computer system Compl. ¶51

III. The Accused Instrumentality

Product Identification

• The accused instrumentality is the "Runlayer platform" Compl. ¶26

Functionality and Market Context

• The Runlayer platform is described as a system for the "deployment and use of AI agents in enterprise applications" Compl. ¶4 Its allegedly infringing functionality includes enabling "third-party application integration by brokering calls between an organization's AI agents and separate third-party applications using MCP connectors and syncing organizational data" Compl. ¶12
• The complaint alleges the platform ensures "granular permissions on each of the MCP tool calls" and relies on "triggers that are evaluated based on organizational data" Compl. ¶12 To support this, the complaint provides a screenshot from Defendant's documentation that shows its policy definitions, which delineate access based on categories like 'User,' 'Group,' 'Role,' and 'Attributes' Compl. ¶13 The complaint presents this as strikingly similar to Plaintiff's own approach to permissions management Compl. ¶13 A screenshot from Plaintiff's website illustrates its 'Supergroups' feature, which creates dynamic permission lists based on user attributes like level or location Compl. ¶11
• The complaint alleges that Runlayer uses the patented inventions to "compete directly with Rippling," resulting in damages from lost sales and price erosion Compl. ¶14

IV. Analysis of Infringement Allegations

The complaint does not contain claim charts in its body but states that detailed charts for U.S. Patent Nos. 11,435,994, 12,032,940, and 11,789,941 are attached as Exhibits 2, 3, and 4, respectively Compl. ¶12 As these exhibits were not provided, a formal claim chart cannot be constructed. The narrative infringement theory is summarized below.

• '994 Patent and '940 Patent Infringement Allegations:
  The complaint alleges that the Runlayer platform directly infringes at least Claim 1 of the '994 patent and Claim 1 of the '940 patent Compl. ¶26 Compl. ¶37 The core of the infringement theory is that the Runlayer platform performs a method of third-party application integration that mirrors the patented inventions Compl. ¶12 The complaint alleges the Runlayer platform obtains data from third-party applications, syncs organizational data, and ensures granular permissions, which it contends maps to the claimed steps of obtaining, analyzing, processing, and synchronizing data based on rules and permissions derived from the organizational data structure Compl. ¶12 Compl. ¶19 The complaint relies on unprovided exhibits for the specific element-by-element mapping of the Runlayer platform's functions to the claim limitations Compl. ¶29 Compl. ¶40

• Identified Points of Contention:

  • Scope Questions: The asserted claims of the '994 and '940 patents are framed around managing data for an "organization," with specific limitations referencing a "group of employees" '994 Patent, cl. 1 '940 Patent, cl. 1 The accused product is described as a platform for "AI agents" Compl. ¶4 This raises the question of whether an autonomous "AI agent" can be considered an "employee" or a member of a "group of employees" within the scope of the claims, or if the claims are limited to human actors within an organization.
  • Technical Questions: Claim 1 of both the '994 and '940 patents requires analyzing data based on rules determined from or associated with an "object graph data structure." While the complaint alleges similarity in high-level permissioning concepts Compl. ¶13, it does not provide public-facing evidence that the accused Runlayer platform specifically uses an "object graph data structure" to implement its access control policies. The case may turn on evidence of the Runlayer platform's underlying data architecture and whether it meets this specific technical limitation.

V. Key Claim Terms for Construction

• The Term: "object graph data structure" (asserted in Claim 1 of the '994 patent and Claim 1 of the '940 patent)

• Context and Importance: This term describes a specific technical component at the heart of the claimed invention. Practitioners may focus on this term because the infringement analysis will likely depend on whether the Defendant's data architecture, which the complaint alleges uses "attributes" for permissions Compl. ¶13, can be proven to be an "object graph data structure" as required by the claims.

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The specification states that the data structures "can include one or more object graphs providing information about entities, relationships, and/or any other aspects relating to the definition, structure, and rules associated with organizational data" '994 Patent, col. 12:65-13:2 This language could support an interpretation that covers a wide range of data models that represent entities and their relationships in a graph-like manner.
  • Evidence for a Narrower Interpretation: The specification also provides concrete examples, such as defining relationships where "each employee must be assigned to a department" '994 Patent, col. 12:53-55 and notes that organizational structure can be "encoded within links or edges defined between objects" '941 Patent, col. 6:1-3 This may support a narrower construction requiring a formal graph database with explicit nodes and edges, rather than any relational data that can be abstractly represented as a graph.

• The Term: "first group of employees" (asserted in Claim 1 of the '994 patent and Claim 1 of the '940 patent)

• Context and Importance: This term appears in the context of defining permissions. Its construction is critical because the accused platform is described as managing "AI agents" Compl. ¶4 The dispute may turn on whether an "AI agent" falls within the definition of an "employee."

• Intrinsic Evidence for Interpretation:

  • Evidence for a Broader Interpretation: The specification defines organizational data broadly to include entities like "individuals (e.g., employees, vendors, independent contractors), departments, teams, groups..." '994 Patent, col. 12:45-47 This expansive list of human and group entities could be argued to support a functional definition, where any actor (human or AI) performing a role for the organization could be considered part of a "group."
  • Evidence for a Narrower Interpretation: The plain language of the term "employees" has a common meaning tied to human workers. The claims consistently use this term without providing an explicit, broader definition that includes non-human agents. A party could argue that the term should be given its plain and ordinary meaning, which would likely exclude autonomous AI agents.

VI. Other Allegations

• Indirect Infringement: The complaint alleges that Runlayer induces infringement by "actively encouraging others" (i.e., its customers) to use the infringing platform. This allegation is supported by references to Runlayer's "extensive documentation," website, and other public promotions Compl. ¶27 Compl. ¶38 Compl. ¶49
• Willful Infringement: The complaint alleges willful infringement based on Runlayer's purported knowledge of the asserted patents. This knowledge is alleged to have been established, at the latest, by a "Notice Email to Runlayer" sent on August 9, 2026, the day before the complaint was filed Compl. ¶31 Compl. ¶42 Compl. ¶53

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

1. A core issue will be one of technical architecture: Does the evidence show that the accused Runlayer platform utilizes an "object graph data structure" to define and apply permissions, as specifically required by the asserted claims, or does it employ a fundamentally different access control mechanism that falls outside the claims' scope?
2. A second central issue will be one of definitional scope: Can the term "employees," as used in the context of managing human-centric organizational data in the patents, be construed to encompass the autonomous "AI agents" that the accused platform is designed to deploy and manage?
3. A key question regarding damages will be the effect of willfulness allegations: Given that the pre-suit notice was allegedly sent only one day before the lawsuit was filed, the case will explore whether this is sufficient to establish the subjective bad faith required for enhanced damages based on pre-suit conduct, or if the willfulness inquiry will be effectively limited to post-filing conduct.