Rippling Sued for Cloning Startup Tech After Year Trial

HR and IT software giant Rippling has countersued the small AI startup Runlayer for patent infringement, escalating a fight that erupted last month over stolen product ideas. According to TechCrunch, this new lawsuit follows Runlayer's July 28 complaint alleging Rippling used a nearly year-long product trial as a blueprint to clone its core technology. This battle serves as a stark case study in the new, high-stakes calculus for startups selling critical infrastructure to deep-pocketed software companies that have the resources and incentive to build it themselves.

This isn't a simple breach-of-contract dispute. Runlayer made a gateway for the Model Context Protocol (MCP), an open standard that lets AI agents connect securely to business software. Rippling, with its intense focus on internal R&D, was a natural customer and became an early tester in mid-2025. The ensuing legal war is a test of where collaboration ends and misappropriation begins in the age of generative AI, where the line between prospective client and future competitor is vanishingly thin.

The Anatomy of a Doomed Tech Courtship

The root of the conflict lies in an extended commercial dance that never culminated in a sale. Runlayer claims Rippling entered into both a mutual non-disclosure agreement and a product trial agreement, which allegedly barred copying Runlayer's intellectual property or creating derivative works. According to the initial lawsuit summaries, this wasn't a casual demo. The technical collaboration lasted nearly a year and reportedly included Runlayer sharing its product roadmap, source code, and deployment architecture with Rippling's team.

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.

Then, the deal collapsed over price. Runlayer says pricing talks failed, and it cut off Rippling's access in June 2026. Soon after, Runlayer alleges it learned from a Rippling insider about an internal project to build "essentially a clone" of its MCP gateway. Rippling has since confirmed it is building its own MCP server to compete with Runlayer. For Rippling, which turns internally used tech into products like its AI Spend Console, building a control layer for AI agents accessing HR, IT, and finance data is a logical strategic move.

The central question for the court is narrow: Given that an MCP gateway is a strategically obvious product for Rippling to own, did Rippling build it independently, or did Runlayer's confidential material provide an unfair shortcut? Runlayer's claim isn't that Rippling copied a general idea, but that it used protected technical specifics to accelerate its own competing product's development.

A Whistleblower's Text and a Swift Reversal

The most dramatic piece of evidence in Runlayer's original complaint is a text message from a Rippling employee to Runlayer CEO Andrew Berman. The employee, Tim Fall, allegedly wrote on June 12: "There's been a project internally to build essentially a clone o[f] Runlayer…It's not feature complete by any means, but it's almost a 1 to 1 copy of Runlayer."

That text is the linchpin of Runlayer's claim of a direct copy. However, in a legal declaration filed by Rippling, Fall recanted. He stated, "Now that I have seen and used Rippling’s MCP Gateway, it is clear to me that it is not a ‘clone’ and did not copy the Runlayer MCP Gateway. I would not make those statements knowing what I know now, as they are not correct." He added he was disappointed Runlayer disclosed the messages without his permission.

This reversal is a critical battlefield. Runlayer is betting the original, panicked text reflects the true internal reality at Rippling. Rippling is arguing the recantation proves its product was developed independently and that Runlayer's entire case hinges on a single misunderstood message.

Rippling's Counterpunch: A Patent Infringement Gambit

Rippling's response on August 10 was not just a denial. It was a full counteroffensive. The company filed a separate lawsuit in Delaware accusing Runlayer of infringing on three of Rippling's patents. Rippling's complaint states Runlayer's platform "infringes Rippling’s patents, steals its intellectual property, and drafts off the substantial time and resources Rippling spent developing this technology over the past decade," causing damages through lost sales and price erosion.

Rippling's spokesperson framed the move as calling out hypocrisy: "It takes a certain boldness to accuse a competitor of violating intellectual property laws while infringing on that competitor’s inventions. But that’s exactly what Runlayer has done here."

Runlayer CEO Andrew Berman fired back, calling the countersuit "a desperate, retaliatory ploy to distract from the fact Rippling misappropriated our proprietary technology." He asserted Runlayer's product has "nothing to do with these patents."

XOOMAR Analysis: The patent lawsuit is a classic asymmetrical warfare tactic. For a well-funded company like Rippling, litigating patent claims is expensive but manageable. For a startup like Runlayer, which has raised $42 million, fighting a two-front legal war, defending against patent claims while prosecuting its own trade secret case, can be an existential drain on capital and focus. The goal is often to increase the cost and risk for the smaller opponent to force a settlement on favorable terms.

Why This Battle Is a Flashpoint for the AI Infrastructure Market

The Runlayer lawsuit is not happening in a vacuum. The MCP gateway space is rapidly becoming crowded, proving Runlayer was correct about the market need. Freshworks announced its Freddy AI Agent Studio and an MCP Gateway in May 2026. AWS has its Bedrock AgentCore Gateway supporting MCP. The protocol itself, launched open-source by Anthropic in late 2024, is gaining traction as enterprises seek to safely deploy AI agents.

This context makes Runlayer's plight a textbook founder nightmare. A startup can be first to market, backed by serious investors like Khosla Ventures and Felicis, and have a technically sound product, yet still be crushed if a potential enterprise client becomes a competitor. Runlayer's heavy-hitting legal team, Sullivan & Cromwell, suggests it is prepared for a serious fight, but that doesn't offset the commercial peril.

Furthermore, Rippling is already engaged in a separate, high-profile trade secret lawsuit with rival Deel, which it accuses of corporate espionage. While unrelated, this history means Rippling's leadership is no stranger to aggressive IP litigation, potentially shaping its approach to the Runlayer conflict.

A Warning for Startups Beyond the Courtroom Docket

Regardless of the legal outcome, which will likely be a confidential settlement, the Runlayer vs. Rippling saga delivers immediate, practical lessons for the ecosystem.

For AI infrastructure startups: Deep technical trials with large software platforms now carry an extreme, binary risk. If the evaluation requires access to source code, detailed roadmaps, and system architecture, you are not just selling a product. You are exposing the proprietary machinery that gives you a competitive edge. The due diligence process becomes a potential blueprint for in-house development if the deal sours.

For enterprise buyers (and builders) like Rippling: The episode underscores the legal and reputational dangers of prolonged product testing without a clear path to purchase. What looks like rigorous due diligence can be construed in court as a fishing expedition for R&D. Companies must manage these relationships with explicit, scoped agreements and clear internal firewalls between evaluation teams and product development units.

The market takeaway is already clear: In the platform economy, especially in the frenzied AI tooling layer, collaboration is fraught. The terms of engagement are no longer just about pricing and service-level agreements. They are about constructing legal moats around your core IP during every sales conversation. For startups, the old adage holds truer than ever: be careful whose boat you build, because you might be teaching them how to sail.

Why This Changes Everything

• This legal battle sets a new precedent for how startups must approach collaboration with potential enterprise customers, turning sales cycles into IP armor.
• It highlights the disappearing line between vendor and competitor in AI infrastructure, threatening the trust small innovators rely on to survive.
• The outcome will shape whether startups can safely sell critical tools to giants without fear of being reverse-engineered.