Runlayer vs. Rippling: The Battle Over MCP Innovation Accusations

TL;DR

• Runlayer has sued Rippling, alleging that Rippling evaluated Runlayer’s MCP gateway during partnership talks and then moved to build a competing product using Runlayer’s trade secrets and NDA-protected information.
• Rippling has denied the allegations, framing the lawsuit as an effort to block competition rather than a legitimate IP claim.
• The case could become an important test of how enterprise AI startups protect proprietary know-how during sales, evaluation, and partnership discussions.

Runlayer vs. Rippling: The Battle Over MCP Innovation Accusations

A new flashpoint in enterprise AI

A legal fight between startup Runlayer and HR software giant Rippling has put a fast-growing corner of the AI infrastructure market under the spotlight: Model Context Protocol, or MCP, gateways. Runlayer says Rippling evaluated its product during partnership talks, then took the underlying idea and began building a rival system of its own.

What Runlayer says happened

According to the complaint described in reporting on the case, Runlayer claims it shared product demos, technical documentation, and architectural details with Rippling while the companies were exploring a possible integration or longer-term collaboration. Runlayer further alleges that the discussions later went quiet, only for Rippling to surface with plans for a similar MCP gateway product.

The startup also says the dispute is not just about a broad business concept. Runlayer alleges trade secret misappropriation and violations of non-disclosure agreements signed during the evaluation period, and it is seeking both injunctive relief and damages.

Why MCP gateways matter

MCP gateways are part of the software layer that lets AI systems securely connect to enterprise tools and data. In practical terms, they are meant to help organizations control how AI agents access internal systems, which makes the technology especially valuable for companies trying to deploy AI without creating security or compliance problems.

That strategic importance helps explain why the lawsuit has drawn attention beyond the two companies involved. If Runlayer’s claims hold up, the case could show how easily technical evaluations can blur into competitive risk when startups reveal enough product detail for a potential partner to understand, imitate, or replicate the idea.

Rippling’s response

Rippling has denied the allegations and reportedly described the lawsuit as an attempt to prevent competition. That defense matters because it signals the company is likely to argue that any product it is building relies on its own information and internal development, not on Runlayer’s confidential materials.

At this stage, the public reporting available does not show a court ruling on the merits of the case, so the claims remain allegations rather than findings of fact.

The legal stakes

Runlayer is reportedly seeking to block Rippling’s competing product launch through injunctive relief, along with damages that could exceed $10 million. If the court grants an injunction, it could delay or prevent Rippling from moving forward with its MCP offering while the case proceeds.

The broader legal question is whether Runlayer can prove that specific confidential disclosures were used to create a substantially similar product. Trade secret cases often turn on documentation, access controls, and evidence of what was shared versus what was independently developed, so the technical record will likely matter as much as the business narrative.

Why the case resonates across tech

This dispute highlights a recurring tension in enterprise software: startups often need to show enough of their product to win enterprise deals, but doing so can expose them to imitation risk. That tension is especially acute in AI infrastructure, where a startup’s differentiation may live in architecture, integration design, or workflow details rather than in a consumer-facing feature set.

The case may also influence how future partnerships are structured. If startups perceive evaluation periods as higher-risk, they may tighten NDAs, limit technical access, or insist on narrower proof-of-concept terms before sharing sensitive system design.

Runlayer’s position in the market

Runlayer launched publicly in 2025 with $11 million in seed funding from investors including Khosla Ventures’ Keith Rabois and Felicis, and it said at the time that it had already signed customers including several prominent unicorns and public companies. That early traction suggests the company had already positioned itself as a serious player in MCP security and governance before the dispute with Rippling became public.

Its own marketing has emphasized a broader enterprise MCP platform spanning security scanning, shadow MCP detection, skills, plugins, and agents, which puts the company squarely in the infrastructure layer now attracting intense attention from large software vendors.

What happens next

The next major developments will likely come from court filings, motions over injunctive relief, and any public evidence that clarifies what Rippling reviewed, what Runlayer disclosed, and how the alleged competing product was developed. If the case advances, it could become a closely watched example of how U.S. courts handle AI-era trade secret disputes involving product demos, technical evaluations, and enterprise collaboration talks.

For now, the lawsuit is a reminder that in AI infrastructure, the line between partnership exploration and competitive intelligence can be unusually thin.

AndroGuider Team

Articles written by the AndroGuider team. We try to make them thorough and informational while being easy to read.