Runlayer says Rippling used a year-long product trial to learn its MCP gateway and then built a rival product. If you sell AI infrastructure to deep-pocketed software companies, this is the risk you can't treat as theoretical.
Runlayer's lawsuit against Rippling, filed July 28 in the Southern District of New York, is not just a small startup complaining about a bigger company. The allegation is blunt. Runlayer says Rippling got access to its roadmap, source code, and deployment architecture under contract, then moved toward launching a competing MCP gateway of its own.
That is the trap.
Runlayer makes a gateway for the Model Context Protocol, the open standard that lets AI agents connect to business systems and use their data and tools. MCP has become more important because companies don't want agents wandering through payroll, HR, finance, and customer systems without rules. You need identity, permissions, logging, and a way to shut down bad behavior. A gateway is where much of that control sits.
According to reports from TechCrunch and the New York Post, Runlayer claims Rippling came in as a prospective customer and signed both a mutual non-disclosure agreement and a product trial agreement. The trial agreement allegedly barred Rippling from copying Runlayer's intellectual property or creating derivative works. That sounds like ordinary enterprise paperwork until you get to the uncomfortable part: Runlayer says the technical collaboration lasted nearly a year and included access to sensitive engineering material.
Then the deal broke.
Runlayer says pricing talks failed, the startup cut off Rippling's access in June 2026, and it later learned of internal Rippling work on a similar product. The complaint, as summarized by TechCrunch-linked coverage, alleges trade secret misappropriation, unfair competition, and breach of contract. Runlayer is seeking damages and an injunction. The company has retained Sullivan & Cromwell, which is not the kind of firm you bring in for a casual warning letter.
Rippling denies the allegation. A spokesperson told TechCrunch, according to Neura Market's republication of the report: "Runlayer's panicked effort to avoid competition by fabricating claims is not an effective way to deal with its business failures." Rippling added that it is launching a "superior product" using only its own proprietary information. That denial matters, because complaints are not findings of fact. But so does the sequence Runlayer is asking the court to examine.
The buyer was never just a buyer #
Rippling is not a passive HR software customer. The company was valued at $16.8 billion in its 2025 Series G financing, according to The Information, after previously reaching a $13.5 billion valuation in its 2024 Series F. It also spends heavily on engineering. In a June TechCrunch interview, CEO Parker Conrad said Rippling spends 45% to 50% of revenue on R&D, compared with roughly 8% to 9% at public HR companies such as Paylocity and Paycom.
You don't need to guess what that means. Rippling likes to build.
TechCrunch reported in June that Rippling's Data Cloud product is meant to pull more business analytics into its own system, including employee data, Salesforce support tickets, AI spend, and performance ratings. Rippling has also pitched Rippling AI as a way to answer questions and act across HR, IT, and finance using live company data. An MCP gateway fits naturally into that strategy. If agents are going to touch business data, Rippling has every incentive to own the control point.
That is exactly why Runlayer's claim is worth taking seriously without pretending the case is already decided. If a product is obvious for Rippling to build, the court still has to ask a narrower question: did Rippling build it independently, or did Runlayer's confidential material shorten the path?
MCP is getting crowded fast #
The market around Runlayer is moving quickly. Freshworks announced Freddy AI Agent Studio and an MCP Gateway in May 2026, with Freshservice using MCP to connect AI tools to service data and to let Freddy agents act across outside systems. AWS also has Bedrock AgentCore Gateway, which its documentation describes as a managed gateway for connecting agents to tools, other agents, and models through MCP-compatible interfaces.
But one detail in the original draft needed correction: AWS documentation currently lists AgentCore Gateway support for MCP versions 2025-03-26, 2025-06-18, and 2025-11-25. It does not show support for the 2026-07-28 MCP version. The Model Context Protocol project did publish a 2026-07-28 release candidate, with the final specification scheduled for July 28, 2026, but that is not the same as AWS support.
Frankly, this is the part founders should read twice. A startup can be right about the need, early to the market, and backed by serious investors, and still find itself selling to customers that can become competitors. Runlayer has reportedly raised $42 million, according to the New York Post, and says it shared sensitive technical material under strict agreements. That may help in court. It doesn't remove the commercial risk.
The Deel case gives Rippling an awkward backdrop here. Rippling sued Deel in 2025, alleging corporate espionage by its HR software rival, and Deel has denied wrongdoing and countersued. That earlier case does not prove anything about Runlayer's complaint. It does mean Rippling is already publicly associated with a bruising fight over trade secrets, insiders, and competitive conduct.
Runlayer now has to prove more than bad timing. Rippling has to show its gateway came from its own work. For every AI infrastructure startup running long technical trials with large software buyers, the lesson is more immediate than the lawsuit: if the evaluation requires source code, roadmap detail, and deployment architecture, you are not just selling. You are exposing the machinery.
Also read: Micron has sold out its 2027 AI memory production and the cost is coming for everyone • OpenAI resets Sol usage limits and fixes the efficiency gap that caught power users off guard • Epsagon founders raise $34M seed round for Harmony, an AI agent platform built inside Slack and Teams