Runlayer, a startup specializing in secure Model Context Protocol (MCP) gateways, has initiated legal action against HR software giant Rippling, alleging the theft of its product idea. The lawsuit, detailed in a complaint seen by TechCrunch, highlights the inherent risks for AI infrastructure providers engaging with larger enterprise clients, particularly those with significant in-house engineering capabilities. This dispute underscores the complex challenges and intellectual property vulnerabilities faced by emerging AI companies during extensive product trials.

Key Developments

  • Runlayer, an MCP gateway provider, has filed a lawsuit accusing Rippling of misappropriating its intellectual property.
  • The lawsuit claims Rippling conducted a nearly year-long product trial, gaining access to Runlayer’s product roadmap and source code under NDA.
  • After the trial concluded without a pricing agreement, Runlayer alleges a Rippling insider reported an internal project to clone its product.
  • Rippling has confirmed it is launching its own MCP gateway but denies Runlayer’s allegations of IP misuse.
  • Runlayer has engaged prominent law firm Sullivan & Cromwell, lending optical credibility to its legal challenge.

What Happened

Runlayer, a company focused on providing a secure Model Context Protocol gateway for AI models to access external data and tools, entered into an extensive product trial with Rippling, a prospective customer. During this evaluation period, which reportedly spanned nearly a year, Runlayer shared sensitive information with Rippling, including its product roadmap and actual source code. Both parties had signed a mutual non-disclosure agreement, and Rippling also agreed to a product trial agreement that explicitly prohibited the copying of Runlayer’s intellectual property or the creation of derivative works, a standard clause in enterprise software trials.

The intensive collaboration involved significant engineering effort from both sides. However, the two companies ultimately failed to reach an agreement on pricing, leading Runlayer to terminate the product trial. Shortly after the trial’s conclusion, Runlayer alleges that its founder and CEO, Andrew Berman, received a text message from a “Rippling insider” describing an internal project to build “essentially a clone o[f] Runlayer,” characterized as “almost a 1 to 1 copy.” Runlayer’s complaint asserts that Rippling’s subsequent product development must have relied on its shared intellectual property, constituting trade secret misappropriation, unfair competition, and breach of contract.

Why It Matters

This legal confrontation between Runlayer and Rippling casts a spotlight on the precarious nature of enterprise sales in the burgeoning AI infrastructure market. For startups like Runlayer, sharing deep technical insights and even source code during lengthy trials is often a prerequisite for securing major contracts. However, this case illustrates the significant risk that potential customers, especially well-resourced tech companies, might use such trials to glean enough information to develop their own in-house solutions, circumventing a partnership or purchase. The outcome of this lawsuit could set a precedent for how intellectual property is protected and exchanged in the rapidly evolving AI sector, particularly concerning foundational AI interoperability components like MCP gateways.

Industry Impact

The lawsuit highlights a critical tension within the AI industry: the need for collaboration to advance technology versus the imperative for startups to protect their innovations. MCP gateways, which enable AI models and agents to securely interact with external data and services, are becoming fundamental building blocks for AI interoperability. Anthropic open-sourced its MCP in November 2024, contributing to a rapidly expanding and competitive field. Runlayer, having raised $42 million from notable investors like Khosla Ventures and Felicis, launched its product mid-last year into this increasingly crowded space. This legal battle could prompt a re-evaluation of standard trial agreements and IP protection strategies across the AI infrastructure landscape, particularly for companies selling to other tech firms that possess the engineering capacity to replicate solutions.

Analysis

The Runlayer-Rippling dispute exemplifies a recurring challenge in enterprise technology sales, amplified by the unique dynamics of AI infrastructure. Startups often face immense pressure to demonstrate the efficacy and depth of their technology through extensive trials, which frequently necessitate sharing proprietary information to integrate deeply with a prospective client’s systems. This level of access, while crucial for proving value, simultaneously exposes the startup to the risk of intellectual property exploitation, especially when the client possesses the resources to “build versus buy.”

Rippling’s public denial of misusing Runlayer’s IP, coupled with its assertion of launching a “superior product” based solely on proprietary information, sets the stage for a contentious legal battle. The involvement of a high-profile law firm like Sullivan & Cromwell on Runlayer’s side suggests a serious commitment to pursuing the claim, lending weight to the startup’s allegations. Regardless of the legal outcome, this case serves as a stark reminder for AI infrastructure providers to meticulously craft and enforce their contractual agreements, particularly those pertaining to intellectual property, during all phases of customer engagement. It also underscores the strategic dilemma for enterprises: whether to invest in external innovation or leverage internal capabilities to develop similar solutions, a decision often influenced by cost, control, and perceived competitive advantage.

Competitive Landscape

The market for Model Context Protocol (MCP) gateways is experiencing significant growth and competition. Initially, Anthropic’s open-sourcing of MCP in November 2024 provided a foundational standard for secure AI interoperability. Since then, numerous products have emerged, offering enhanced control, security, and agent management features atop the basic protocol. Runlayer launched its product in the middle of last year, entering a field that has become considerably more competitive. Rippling’s confirmed entry into this market with its own MCP gateway product further intensifies this competition, particularly as more enterprises seek robust solutions for connecting AI tools to their proprietary data. The dispute highlights the high stakes in this rapidly developing segment of the AI ecosystem, where differentiation and intellectual property are key to market positioning.

Future Implications

Near-term (3-6 months): The lawsuit will likely proceed with initial discovery phases, potentially revealing more details about the extent of information shared and Rippling’s development timeline. Other AI infrastructure startups may review and strengthen their trial agreements and IP protection clauses.
Medium-term (1-2 years): The legal proceedings could influence standard practices for enterprise software trials, particularly in the AI sector, leading to more stringent contractual protections or alternative engagement models. Companies may become more cautious about the depth of information shared during evaluations.
Long-term (3-5 years): The outcome could establish significant legal precedents regarding trade secret misappropriation and breach of contract in the context of AI technology development. It may also shape how venture capitalists evaluate and invest in AI infrastructure startups, emphasizing robust IP strategies.

Actionable Insights

  • Review and strengthen all non-disclosure and product trial agreements to explicitly address AI-specific intellectual property and derivative works.
  • Implement strict controls on the scope and nature of proprietary information shared during prospective customer evaluations.
  • Consider phased access to source code or sensitive data, escalating access only as trust and commitment solidify.
  • Document all communications and technical exchanges meticulously throughout the trial period to build a strong evidentiary record.
  • Consult legal counsel specializing in intellectual property and technology law before engaging in deep technical collaborations with larger enterprises.

What is Runlayer’s core accusation against Rippling?

Runlayer accuses Rippling of stealing its product idea for a secure Model Context Protocol (MCP) gateway, alleging that Rippling used information shared during an extensive product trial to build a “clone” of Runlayer’s technology.

What is a Model Context Protocol (MCP) gateway?

An MCP gateway is a standard and product that allows AI models and agents to securely and reliably pull in outside data and tools, providing a secure way for AI to access external information and services.

What information did Runlayer share with Rippling during the trial?

During the nearly year-long product trial, Runlayer shared extensive details, including its product roadmap and actual source code, with Rippling under mutual non-disclosure and product trial agreements.

How has Rippling responded to the allegations?

Rippling has confirmed it is launching its own MCP gateway but denies Runlayer’s allegations, stating it is launching a “superior product” using only its proprietary information and that Runlayer’s claims are a “panicked effort to avoid competition.”

Why is this lawsuit significant for the AI industry?

The lawsuit highlights the risks for AI infrastructure startups when engaging with larger enterprise customers, particularly concerning intellectual property protection during extensive product trials and the potential for clients to build competing in-house solutions.

Key Takeaways

  • Runlayer has sued Rippling, alleging intellectual property theft related to its MCP gateway product after a prolonged trial.
  • The lawsuit centers on claims that Rippling gained access to Runlayer’s source code and roadmap under NDA, then developed a similar product.
  • Rippling denies the allegations, asserting its new MCP gateway is based on its own proprietary information.
  • The case underscores the significant IP risks for AI infrastructure startups during deep enterprise customer engagements.
  • The competitive landscape for MCP gateways is rapidly expanding, with both open-source protocols and commercial products vying for market share.