Two Companies Sued Each Other Over an AI Tool, Then Just... Stopped
August 21, 2026
Based on reporting by TechCrunch → — simplified & explained by VAIIYA.
What the fight was about
Picture a company that wants its AI assistants to be able to pull information from other software — say, checking a candidate's resume in a hiring system — without just handing the AI full, unrestricted access to that system. A tool that manages this safely, checking who's allowed to see what and keeping a log of activity, is sometimes called an "MCP gateway." (MCP is a technical standard that lets AI tools talk to other software safely.)
A startup called Runlayer built one of these gateways and spent over a year working closely with the workplace-software company Rippling, which was testing Runlayer's product. But Rippling never actually became a paying customer. Instead, an employee at Rippling texted Runlayer's founder to say Rippling was building its own competing version — internally describing it as basically a copy of Runlayer's product.
The lawsuits, and how they ended
Runlayer sued, arguing Rippling had broken the rules of their testing agreement. Rippling counter-sued, claiming Runlayer had copied ideas that Rippling had patented — a move some observers saw as a pressure tactic meant to make the legal fight too expensive for the smaller startup to continue.
In the end, both sides just walked away. Runlayer dropped its case first, and Rippling followed shortly after. No settlement money changed hands in either direction, and even the lawyers' bills weren't reimbursed by either side.
The lesson for founders
The real takeaway isn't really about who "won." It's a warning about how a company you're closely partnering with — even one testing your product for over a year — can turn into a direct competitor almost overnight in an industry that's moving as fast as AI is right now. Rippling has since launched its own AI-model-routing product and its own MCP gateway, putting it in competition with several companies at once, including the very startup it had just been testing.