Runlayer and Rippling Drop Legal Claims as AI Gateway Battle Ends Without Settlement

Early-stage startup Runlayer and enterprise software firm Rippling have mutually dismissed their legal disputes against each other, resolving a conflict centered on artificial intelligence gateway technology. Court filings indicate that neither party agreed to a financial settlement, nor did any funds exchange hands to cover attorney fees. Shortly after the dismissal, Rippling publicly unveiled its Model Context Protocol (MCP) gateway, the exact software category that catalyzed the conflict.

What Happened

The disagreement began after Rippling conducted tests on Runlayer’s MCP gateway for over a year. According to Runlayer’s complaint, the engineering units from both companies collaborated closely during this trial phase. However, Rippling ultimately did not sign a commercial agreement to become a Runlayer customer.

Instead, Runlayer founder and chief executive Andrew Berman received a text message from an employee at Rippling stating that the firm was designing an in-house MCP gateway intended for commercial release. The message reportedly described Rippling’s upcoming tool as a clone of Runlayer’s architecture. Runlayer subsequently filed a lawsuit alleging that Rippling had breached contractual agreements governing the product trials.

In response, Rippling initiated a countersuit claiming that Runlayer infringed on several of its patents. Runlayer characterized the counter-claim as a tactical move intended to escalate litigation expenses and pressure the startup into withdrawing its initial complaint. After three weeks in the discovery phase, Runlayer chose to withdraw its legal action, and Rippling simultaneously dismissed its counterclaims without receiving any settlement.

Key Highlights

• No Financial Exchange: Both lawsuits were dropped unconditionally without monetary settlements or reimbursement of legal expenses.
• Runlayer Background: Runlayer emerged from stealth in November 2025, having raised $42 million from venture capital firms including Felicis and Khosla Ventures’ Keith Rabois. The company is led by serial founder Andrew Berman, whose previous ventures include Nanit and Vowel.
• Origins of the Dispute: The clash arose after more than 12 months of collaborative testing, following an internal communication stating Rippling was constructing an identical tool.
• Immediate Commercial Rollout: Rippling introduced its own MCP gateway immediately following the dismissal of both lawsuits.
• Market Expansion: The release expands Rippling beyond its primary payroll and human resources offerings into artificial intelligence access management and model routing.

Why This Matters

An MCP gateway functions as a control layer for artificial intelligence agents interacting with internal corporate databases. When an automated agent attempts to retrieve records—such as an HR representative querying candidate information and contact details from a recruitment platform—the gateway facilitates the interaction rather than granting the agent direct system access. This framework enables organizations to implement role-based access restrictions and maintain detailed system logs.

The brief litigation illustrates the operational friction that can emerge when startups engage in prolonged proof-of-concept testing with established technology firms. In fast-moving software environments, an enterprise evaluating an emerging tool can shift from a prospective customer to a direct competitor. Rippling has historically operated in the payroll and employee benefits space, but its recent product additions position it against companies offering AI infrastructure, model routing, and system monitoring.

What to Watch Next

Following the litigation, both companies are taking distinct approaches to the enterprise AI infrastructure market:

• Rippling’s AI Strategy: Rippling has rolled out tools that track employee token expenditure and direct workflows across various AI models, placing the company in competition with platforms such as Stripe, Ramp, and Databricks. Its role-tied MCP gateway also competes with offerings from Docker, Amazon Bedrock, and Runlayer.
• Runlayer’s Product Scope: Runlayer continues to offer an expanded portfolio of agent security tools tied to its gateway, focusing on the deployment of agents and the identification of unauthorized or unmanaged AI agents operating inside corporate networks.

Frequently Asked Questions

What is an MCP gateway?

An MCP gateway is an enterprise software system that safely directs requests from artificial intelligence agents to company databases. It prevents direct system access, enforces employee role-based permissions, and maintains audit logs of agent operations.

Why did Runlayer originally sue Rippling?

Runlayer filed suit alleging that Rippling breached evaluation contracts after testing Runlayer’s software for more than a year and subsequently developing an internal tool that a Rippling employee described as a clone.

Why did Rippling file a countersuit?

Rippling filed counterclaims alleging patent infringement by Runlayer, an action Runlayer argued was intended to increase legal costs and force a withdrawal of the initial lawsuit.

Did either company win damages or legal fees?

No. Both parties agreed to drop their respective lawsuits without any monetary payout, settlement agreement, or compensation for legal expenses.

Source: Information reported from court documents and industry coverage by TechCrunch.