Runlayer and Rippling Drop Lawsuits, But the Saga Remains a Cautionary Tale for Founders

In a dramatic turn of events, Runlayer and Rippling have mutually agreed to drop their respective lawsuits against each other, according to court documents reviewed by TechCrunch. Notably, the resolution came without any settlement, monetary exchange, or even reimbursement of legal fees. Rippling marked the occasion by swiftly releasing its MCP gateway—the very product at the heart of the dispute—positioning it as a direct competitor to Runlayer's offering. This public confrontation serves as a stark warning for founders: in the age of AI, where software development has become almost commoditized, your next competitor could emerge from the most unexpected place—even a prospective customer. To recap the brief but intense legal clash: Runlayer, an early-stage startup that launched out of stealth in November 2025, had attracted $42 million in funding from prominent VCs, including Keith Rabois of Khosla Ventures and Felicis. The company is led by third-time founder Andrew Berman, whose previous ventures include baby-monitor maker Nanit and AI video conferencing tool Vowel, which was acquired by Zapier in 2024. According to Runlayer's lawsuit, Rippling had been testing Runlayer's MCP gateway for over a year, with the two engineering teams collaborating closely. However, Rippling never signed on as a customer. Instead, Berman received a text message from a Rippling employee stating that his employer was building its own MCP gateway and planned to release it as a product—described by the employee as a clone of Runlayer's. Runlayer subsequently sued, alleging breach of contractual agreements governing the product trials. Rippling countered with a patent infringement lawsuit, which Runlayer interpreted as a tactic to escalate legal costs and pressure them into dropping their claim. An MCP gateway is a critical piece of enterprise AI infrastructure. It securely manages an organization's AI agent requests for data from external software systems. For example, when a hiring manager requests details on top candidates, including email addresses, the gateway retrieves that data from the company's recruitment system—without granting agents direct access to backend systems. It also enables additional features like role-based access control (e.g., managers vs. interns), observability (logs and usage trails), and more. After spending three weeks in discovery, Runlayer decided to drop its suit. Rippling followed suit, also walking away without any settlement. While the legal proceedings ultimately fizzled out, generating more public sparring than substantive resolution, the episode offers deeper lessons for founders. The AI landscape is evolving at breakneck speed, and the traditional "technical shoot-outs" that large enterprises often impose on startups need to be re-evaluated. Between the time a startup enters such a trial and the moment a decision is made—potentially many months later—an enterprise's needs, priorities, and even its internal capabilities can shift dramatically. What may have been a cutting-edge solution during the trial could become obsolete or easily replicated by the time a decision is due. For founders, this case underscores the importance of protecting intellectual property and being cautious about sharing proprietary technology with potential customers, especially in the fast-moving AI sector. It also highlights the need for agility and strategic foresight in navigating partnerships and competitive threats in an era where innovation cycles are measured in months, not years.

via TechCrunch AI