Loading today’s stories
Product1 distinct publisher3 min readUpdated
No settlement, no money, no fees. Runlayer's year-long design partner released a rival MCP gateway the same night the litigation ended, and that is the lesson for founders.
The Product Desk · Product desk
Compiled by The Product DeskSomething wrong?How this is made
No settlement, no money, no fees. Runlayer's year-long design partner released a rival MCP gateway the same night the litigation ended, and that is the lesson for founders.
Runlayer and Rippling dropped their lawsuits against each other on Wednesday night, with no settlement, no money changing hands, and not even lawyers' fees, according to court documents seen by TechCrunch [1]. Rippling marked the occasion by immediately releasing its MCP gateway, the product at the heart of the dueling suits and the one that competes with Runlayer's [2].
The sequence matters more than the pleadings. According to Runlayer's lawsuit, Rippling tested Runlayer's MCP gateway for more than a year, with the two engineering teams working closely together, and never signed on as a customer [3]. Runlayer's founder Andrew Berman then received a text from a Rippling employee saying his employer was building its own MCP gateway and planned to ship it as a product, which the employee described as a clone of Runlayer's [4]. Runlayer sued, claiming Rippling violated contractual agreements covering the product tests [5]. Rippling countersued over patents, a move Runlayer read as an attempt to run up its legal bill and force a withdrawal [6]. Runlayer dropped its case after three weeks of discovery, and Rippling dropped its own [7].
Nothing was adjudicated and nothing was licensed. Because both sides walked away without a settlement or a payment [1], neither bought peace: the contractual theory and the patent theory both remain unresolved [14].
The product is not exotic, which is the point. An MCP gateway sits between an enterprise's AI agents and its software systems, retrieving data on request rather than handing agents direct access, and then layering on role-based access control, logging and usage trails [8]. Rippling, whose historic business is payroll and benefits management [9], has moved into two adjacent markets in a span of weeks: an AI gateway that routes across models and dashboards token spend by employee, putting it against Stripe, Ramp and Databricks [10], and now an MCP gateway that ties AI access to employee roles, putting it against Runlayer, Docker and Amazon Bedrock [11]. Runlayer, which came out of stealth in November 2025 and has raised $42 million from investors including Khosla Ventures' Keith Rabois and Felicis [12], is selling a broader bundle around the gateway, from agent creation to finding shadow AI agents running inside an enterprise without IT's knowledge [13].
For operators, the design-partner arithmetic is what changed. TechCrunch's read is that the long technical shoot-outs enterprises like to impose on startups need rethinking, because a buyer's needs can shift drastically between the start of an evaluation and its end [15]. The harsher version: a multi-quarter evaluation is a detailed specification handover, delivered for free, to an engineering organisation that can now build the thing. Berman is a third-time founder whose previous companies include Nanit and Vowel, which sold to Zapier in 2024 [16], and that experience did not prevent the outcome. The relevant math is that a test running more than a year, ending on or near this month, began well before Runlayer's November 2025 launch [17], which is to say the entire stealth period was spent teaching a prospect the product.
What to watch: whether Runlayer's differentiation holds now that the gateway itself is table stakes and the pitch rests on shadow-agent discovery and agent creation [13]; whether Rippling's patents reappear against anyone else, given nothing was settled [14]; and whether enterprise pilots in agent tooling start getting shorter, paid, or papered with real build restrictions.
Follow any of these and your For You feed starts watching them — no settings page required.
Ranked by verification strength, evidence, and original report placement.
On Wednesday night, Runlayer and Rippling dropped their respective lawsuits against each other. No settlement was made, no money changed hands, and not even lawyers' fees, according to court documents seen by TechCrunch.
According to Runlayer's lawsuit, Rippling tested Runlayer's MCP gateway for more than a year, with the two engineering teams working closely together, and Rippling never signed on to become a customer.
Runlayer dropped its suit after spending the last three weeks in discovery, and Rippling also dropped its own suit without collecting a settlement.
Rippling celebrated by instantly releasing its MCP gateway, the product at the heart of the dueling lawsuits and the one that competes with Runlayer's offering.
Runlayer CEO Andrew Berman received a text from a Rippling employee saying his employer was building its own MCP gateway and planned to release it as a product; the employee described Rippling's product as a clone of Runlayer's.
Runlayer sued, claiming that Rippling violated contractual agreements covering the tests of its products.
Evidence-backed comparisons of source perspectives and observed adoption signals. Read the methodology
Which Builder, Operator, and Investor concerns the observed source mix emphasized—not a truth score.
Evidence, demonstrated adoption, hype gap, incentives, and confidence are assessed independently, each on its own current evidence. How these are measured.
Docketed outcome solid, disputed facts one-sided
The core outcome — mutual dismissal with no settlement, money or fees — is grounded in court documents the reporter reviewed, and the competing product release is directly observed. But the contested narrative (year-plus evaluation, non-conversion, 'clone' text message) is drawn from one party's complaint with no reported Rippling response, and the cluster has only a single publisher.
Products shipped, uptake unmeasured
Two Rippling launches and Runlayer's funded market entry are documented, so the category has real shipping activity. However the only usage datapoint reported is a year-plus evaluation that produced no purchase, and no customer counts, revenue, deployment scale or benchmark results appear anywhere in the sources.
Mild overstatement in framing and competitive set
The verifiable core is modest — two suits dropped without money and a product shipped — yet the framing escalates it into a general lesson about enterprise pilots, and the competitive lists (Stripe, Ramp, Databricks, Docker, Amazon Bedrock) assert head-to-head rivalry with no feature or share evidence. The report is otherwise careful to attribute allegations and to state that nothing was settled.
Plaintiff-sourced narrative plus launch-timed publicity
Most of the disputed detail originates in Runlayer's complaint, and Runlayer — an early-stage company with $42 million raised — benefits from framing a much larger vendor as a copier. Rippling's decision to ship the competing gateway the same night carries obvious promotional value. The publisher's own incentive runs toward a founder-facing cautionary narrative, which shapes the emphasis of the piece.
Confident on outcome, thin elsewhere
Confidence is high for the dismissal terms and the existence of Rippling's gateway, moderate for the litigation chronology, and low for market impact, product equivalence and adoption, all of which rest on a single outlet with no opposing statement and no usage metrics.
build
Relay's last day is September 14th; its founder's next job is Chrome VP2 distinct publishers
invest
Airwallex marks itself up 37% in six months, and tells you why it is not listing1 distinct publisher
build
Vivodyne is spending venture money on wet-lab throughput, not bigger models2 distinct publishers
build
Before you spend quota on an agent skill, make it pass an eval harness1 distinct publisher
Distinct publishers with included, body-backed reporting in this cluster.
1 article · August 20, 2026