MCP Startup Runlayer Sues Rippling Over Alleged Idea Theft
Runlayer, a startup building an MCP gateway product, is suing HR and payroll giant Rippling after Rippling evaluated Runlayer's product during a potential partnership and then built a competing version in-house. The case raises sharp questions about the ethics and legality of corporate due diligence processes.
Original sourceRunlayer, a startup building a Model Context Protocol (MCP) gateway — infrastructure that allows AI agents to securely connect to enterprise systems — is taking legal action against Rippling, the workforce management platform valued at over $13 billion. According to Runlayer, Rippling conducted a thorough evaluation of their product under the guise of a potential business relationship, then declined to partner and proceeded to build a nearly identical product internally. The lawsuit centers on whether Rippling's behavior crossed the line from competitive intelligence into trade secret misappropriation.
MCP gateways sit at a critical layer of the emerging agentic infrastructure stack. They manage authentication, permissioning, and routing between AI agents and the enterprise tools those agents need to act on — think Salesforce, Jira, Workday, or in Rippling's case, its own HR and payroll systems. For a company like Rippling, owning that gateway layer in-house would mean tighter control over how AI agents interact with employee data, a strategically valuable position. Runlayer's argument is that Rippling used the evaluation process as a shortcut to skip the R&D work Runlayer had already done.
The legal theory likely hinges on what was shared during the evaluation and under what agreements. If Rippling signed an NDA or received proprietary technical documentation, Runlayer's case is stronger. If the evaluation was arms-length and the product concept itself wasn't patented or formally protected, Rippling's defense will rest on the well-worn 'ideas aren't protectable' doctrine. The outcome may hinge less on who built what and more on what was disclosed, when, and with what contractual protections in place.
The case arrives at an awkward moment for enterprise AI procurement broadly. As large companies evaluate dozens of AI startups for strategic fit, the line between due diligence and competitive intelligence gathering is increasingly blurry. Startups face a structural disadvantage: refusing to share technical details kills the deal, but sharing them may accelerate the enterprise building its own version. Runlayer's lawsuit, regardless of outcome, will likely cause both sides of these conversations to lawyer up earlier.
Panel Takes
The Founder
Business & Market
“This is the nightmare scenario for every infrastructure startup pitching to potential enterprise customers who are also potential competitors — and Rippling is very much both. Runlayer's moat was presumably in the implementation depth and the integrations they'd already built, but if Rippling could replicate the core in-house after a demo cycle, that tells you the defensibility wasn't deep enough. The real lesson here isn't about Rippling's ethics; it's that infrastructure startups selling to platform players need to think carefully about what they reveal during evaluation and get hard contractual protections before showing the actual plumbing.”
The Skeptic
Reality Check
“Let's be precise about what's actually being alleged here: Rippling saw a demo, thought 'we could build that,' and did. That's not obviously illegal — it's how large software companies have operated since forever. The case lives or dies on what was in the NDA and whether Runlayer shared anything beyond a product pitch, because 'MCP gateway for enterprise systems' is not a protectable idea, it's a category. What kills this startup in 12 months isn't the lawsuit outcome — it's that every major enterprise vendor with an MCP story will build this layer themselves, and Runlayer will be squeezed from both ends regardless of how the litigation resolves.”
The Futurist
Big Picture
“The real thesis here is that MCP gateways are about to become the most contested layer in enterprise AI infrastructure — whoever owns the permissioning and routing layer between agents and business data owns the agent economy inside that company. Rippling isn't building an MCP gateway because they think it's a nice feature; they're building it because letting a third party sit between AI agents and employee data is an unacceptable strategic dependency. The second-order effect of this lawsuit is that it accelerates exactly the behavior Runlayer is complaining about: every enterprise platform player will now build this layer in-house before any startup can establish a foothold, because the alternative is a Runlayer with leverage.”
The PM
Product Strategy
“Runlayer's fundamental product strategy error was targeting a buyer — Rippling — who had both the engineering capacity and the strategic motivation to own this layer themselves. The job-to-be-done for an MCP gateway inside a workforce platform isn't 'connect AI to tools,' it's 'control how AI touches sensitive employee data,' and that's a job Rippling will never outsource. The startups that survive in this space will be the ones selling to companies that can't build it themselves, not to platform players running their own AI roadmaps.”