Runlayer and Rippling Drop Dueling Lawsuits Over AI Gateway Technology
Runlayer and Rippling dropped their respective lawsuits against each other on the night of August 19, 2026, with no settlement, no money, and not even attorneys' fees changing hands, according to court documents reviewed by TechCrunch. Reuters confirmed the development the following day, with spokespeople for both companies acknowledging the end of the U.S. intellectual property dispute.
The litigation centered on an MCP gateway — a product category that has emerged as enterprises deploy AI agents that need structured, governed access to downstream software systems. Think of an MCP gateway as a toll booth between AI agents and the software those agents want to use: instead of letting agents connect directly to a company's internal tools, the gateway sits in the middle, checking permissions, logging activity, and enforcing security rules. Runlayer built one. Rippling, historically focused on payroll and benefits management, then built one too — and shipped it.
Runlayer launched out of stealth in November 2025 and has raised $42 million from investors including Khosla Ventures' Keith Rabois and Felicis. The company is led by Andrew Berman, a third-time founder whose previous ventures were baby-monitor maker Nanit and AI video conferencing tool Vowel, the latter sold to Zapier in 2024. For a founder at that stage, taking on a well-funded adversary in court is a calculated bet — and one that, in this instance, produced no financial recovery.
The dispute's origins trace back to an extended evaluation period. According to Runlayer's lawsuit, Rippling tested Runlayer's MCP gateway for more than a year, with the two engineering teams working closely together — but Rippling never signed on as a customer. Runlayer alleges that during this period Rippling gained access to its product and technical approach, and that a Rippling employee later texted Berman to say Rippling was building its own MCP gateway, planned to release it as a product, and described the offering as a clone of Runlayer's. Rippling denied the trade-secret theft allegations.
Runlayer sued first, claiming Rippling violated contractual agreements covering the product tests. The original suit alleged trade secret theft, according to the New York Post. Rippling countersued on August 10, 2026, filing a patent-infringement action in Delaware federal court that accused Runlayer of infringing three of Rippling's patents. Runlayer viewed the countersuit as a litigation tactic designed to drive up legal costs and pressure the smaller company into dropping its claims.
That pressure, if it was the intent, appears to have worked. Runlayer had spent the last three weeks in discovery before dropping its suit. Rippling then dropped its own suit without collecting anything. Both companies walked away with nothing — no admissions, no payments, no licensing arrangements.
Rippling has since released its MCP gateway as a commercial product, competing directly with Runlayer's offering. The Rippling gateway routes to different AI models and tracks token spend by employee, tying AI usage to the same workforce data layer that underpins its payroll and HR platform. For Rippling, the gateway extends its existing employee-data moat into AI governance. For Runlayer, it means competing head-to-head with a company that had over a year of hands-on exposure to its product during evaluation.
The pattern here will be familiar to anyone who has watched enterprise software for long. A large vendor evaluates a startup's technology under NDA or evaluation agreement, then ships a competing product. The startup sues. Discovery grinds. Legal bills mount. The startup, burning runway it cannot afford, drops the suit. The larger company releases its product regardless. The cycle is not new — but the MCP gateway layer is, and the speed at which this dispute cycled from evaluation to litigation to mutual dismissal, roughly nine months from Runlayer's stealth launch to the lawsuits being dropped, compresses the timeline in ways that earlier enterprise software disputes did not.
The structural asymmetry is the real story. A company like Rippling can absorb patent litigation as a cost of doing business. A $42 million-funded startup cannot absorb indefinite discovery costs without it cutting into runway meant for product and go-to-market. The countersuit mechanism — patent claims filed in Delaware federal court — is a well-established pressure point, and Runlayer's characterization of it as a cost-ratcheting tactic is plausible whether or not the patent claims themselves have merit. Neither company litigated the claims to judgment, so the patent questions remain untested.
What this means for the MCP gateway market is straightforward. The category now has at least two competing commercial offerings, one from a payroll-and-HR incumbent leveraging its workforce data, and one from a standalone startup. The legal dispute did not slow either product's trajectory. It did, however, consume time and capital that Runlayer would have preferred to spend elsewhere — and it leaves a precedent that other large vendors evaluating early-stage MCP gateway technology will notice.
In this author's view, the episode is a reminder that the AI infrastructure boom is creating new product categories faster than the norms around evaluation, partnership, and intellectual property can keep up. The MCP gateway is a narrow, technical layer, but the dynamics playing out over it — a startup building something genuinely useful, a larger company evaluating it closely, then building its own version — are the same dynamics that have shaped enterprise software for decades. What is different now is the speed, and that speed leaves founders with even less time to respond when a larger competitor moves.
