The legal fight between Runlayer and Rippling ended with a whimper on Wednesday night. Both companies dropped their respective lawsuits. No settlement. No cash. Not even lawyers’ fees changed hands, according to court documents seen by TechCrunch. The whole dispute burned hot for weeks, generated plenty of public sniping, and then simply evaporated.
Rippling didn’t waste a second. The company immediately released its MCP gateway, the very product at the center of the dueling lawsuits. Runlayer had claimed Rippling spent more than a year testing its gateway, with engineering teams working closely together, only to bail on becoming a customer. Instead, Runlayer founder Andrew Berman got a text from a Rippling employee saying the company was building its own version and planned to ship it as a product. The employee allegedly described it as a clone. Runlayer sued, alleging contract violations. Rippling countersued over patents, a move Runlayer read as pressure to drop the original suit while legal bills piled up.
For enterprises, an MCP gateway is the security layer between AI agents and company data. When someone asks an agent for the top five job candidates with their email addresses, the gateway fetches that data from the recruitment system without giving the agent direct access. It can also layer on role-based access controls, observability logs, and usage trails. That’s the market Rippling just entered, competing against Stripe, Ramp, Databricks, Docker, and Amazon Bedrock. The company’s pitch ties AI access to employee roles, a natural extension of its payroll and benefits roots.
Runlayer, meanwhile, raised $42 million from Khosla Ventures’ Keith Rabois and Felicis, and its broader bundle includes agent creation and spotting shadow AI agents running inside enterprises without IT’s knowledge. The deeper lesson for founders is uncomfortable: when building software becomes almost trivial, your next competitor might be the very enterprise you spent months courting. The long technical evaluations that enterprise sales cycles depend on are becoming riskier. Between the start of a pilot and its conclusion, the customer’s needs—and their willingness to build instead of buy—can shift dramatically. Runlayer learned that the hard way. The question now is whether Rippling can actually execute on a product category it’s never touched before, or whether this was just a strategic move to make a lawsuit disappear.
