Runlayer and Rippling End Legal Fight

🔑 Enhanced Key Takeaways

•Runlayer accused Rippling of trade secret misappropriation, unfair competition, and breach of contract, specifically claiming Rippling used confidential information shared during a nearly year-long product evaluation to build a competing Model Context Protocol (MCP) gateway.
•The lawsuit was prompted by an alleged message from a Rippling insider to Runlayer's CEO, Andrew Berman, describing an internal Rippling project as 'essentially a clone' and 'almost a 1 to 1 copy' of Runlayer's product.
•Rippling denied the allegations, asserting its competing MCP gateway was developed using only its proprietary information and that Runlayer's claims were fabricated to restrict competition.
•Runlayer, founded in 2025, is an AI infrastructure provider specializing in security and governance software for AI agents and has raised $42 million in funding, including a $30 million Series A in 2026.
•Rippling, a workforce management platform valued at $16.8 billion in May 2025, has been expanding its offerings to include AI governance and previously faced corporate espionage accusations from competitor Deel in 2025.

🛠️ Technical Deep Dive

Runlayer provides an enterprise gateway for Model Context Protocol (MCP), which enables AI applications to connect securely with external tools and business data.
The gateway enforces permissions, inspects tool calls, records activity, and limits which systems an AI agent can reach.
Runlayer's platform includes features for AI enablement and control, offering a catalog of MCPs, enabling teams to convert internal APIs and workflows into reusable agent capabilities, and allowing employees to create governed AI coworkers with scoped permissions.
Key control features involve surfacing 'shadow AI' from unmanaged agents, governing user and agent access, real-time scanning of tool calls and outputs for risk, and tracking AI spend and adoption.
The platform enforces AARM (AI Agent Risk Management) requirements through a primary gateway pattern that proxies tool calls through a control plane for policy and ML security model evaluation, and a secondary 'shadow pattern' for endpoint visibility and enforcement.
Specific capabilities include: real-time policy enforcement, shadow detection/enforcement via MDM/EDR, purpose-built ML threat detection models for MCP-specific attacks, deep identity integration (Okta, Entra, SSO, SCIM), tamper-evident audit logs, Slack-based human-in-the-loop approval workflows, semantic distance tracking, telemetry export (Splunk, Datadog, Honeycomb, S3), and least-privilege credential/tool scoping.
Model Context Protocol (MCP) was initially introduced by Anthropic in November 2024, functioning as a standardized interface for AI systems to connect to enterprise infrastructure.
Rippling AI focuses on automating tasks and analyzing data using natural language, generating precise SQL queries or formulas to provide auditable and deterministic answers.
Rippling's AI Spend Console helps identify AI spend drivers, categorize costs by teams or departments, map AI spend to business metrics, and control AI access by enforcing model access policies.

🔮 Future ImplicationsAI analysis grounded in cited sources

The legal dispute highlights a growing challenge for AI infrastructure startups in protecting intellectual property during product evaluations.

The case involves allegations of a prospective customer using shared confidential information to build a competing product, which could deter startups from engaging in deep technical trials.

Increased scrutiny and more stringent contractual protections will become standard for enterprise software trials involving AI infrastructure.

The Runlayer-Rippling case serves as a cautionary tale, prompting both vendors and customers to re-evaluate NDAs and trial agreements to explicitly address IP protection and derivative work prohibitions.

Rippling's move to release a competing MCP gateway product signifies its strategic expansion into the AI governance and security market.

Despite the lawsuit, Rippling's decision to launch its own MCP gateway indicates a commitment to integrating AI governance into its broader HR, IT, and finance platform, potentially positioning it as a comprehensive AI workforce management solution.

⏳ Timeline

2024-11

Model Context Protocol (MCP) originally introduced by Anthropic.

2025

Runlayer founded, focusing on AI agent security and MCP gateways.

2025

Rippling began a nearly year-long evaluation of Runlayer's MCP gateway product under mutual non-disclosure agreements.

2026-06-12

Runlayer terminated the product evaluation with Rippling, followed by an alleged insider tip about Rippling building a 'clone'.

2026-07-28

Runlayer filed a lawsuit against Rippling for trade secret misappropriation, unfair competition, and breach of contract.

2026-08-10

Rippling filed a countersuit against Runlayer.

Runlayer and Rippling End Legal Fight

⚡ 30-Second TL;DR

Key Points

🧠 Deep Insight

🔑 Enhanced Key Takeaways

🛠️ Technical Deep Dive

🔮 Future ImplicationsAI analysis grounded in cited sources

⏳ Timeline

📎 Sources (25)

👉Related Updates

Could Urine Really Cool AI Data Centers?

Google Lets Readers Favor Trusted Publishers

Linkdaze Turns Calendars Into Household Hubs

Grok Lite Users Report Gibberish Replies