The Runlayer-Rippling Incident: A Signal, Not a Scandal
Recently, Runlayer accused Rippling of product theft in the Model Context Protocol (MCP) space. The specifics matter less than the pattern they reveal.
An incumbent evaluates a startup's technology through the lens of a vendor integration—a deep technical exploration of an MCP gateway. The startup, eager for distribution, opens its architecture, explains its differentiation, and demonstrates value. The incumbent absorbs that knowledge, iterates, and releases a near-identical feature as a native offering. The startup is left with legal threats, porous NDAs, and a market that no longer needs it.
This is not an isolated incident. This is the Integration Paradox: the more effectively you integrate with a platform, the more you expose the blueprint for your own commoditization.
The Anatomy of the Trap
1. The 'Death by NDA' Mechanism
NDAs are paper shields against deliberate theft. They offer no protection against iterative imitation. An incumbent does not need to copy your code—it needs only to understand your approach, your bottlenecks, and your unique value proposition. Once internalized, the incumbent can build a functionally equivalent feature, refactor it into its own architecture, and claim ownership of the innovation.
In the MCP ecosystem, where interoperability is the core selling point, the line between integration and imitation blurs. The NDA becomes a litigation tool after the fact, not a preventative safeguard. By the time lawyers are engaged, the market has already shifted.
2. Collaborative Discovery as Market Intelligence
History shows a recurring pattern: in early-stage ecosystem development, platforms use collaborative discovery as a mechanism for market intelligence. When an incumbent requests deep technical integration—an MCP gateway, a custom adapter, a shared protocol—it is framed as partnership. But the information flow is asymmetric.
You provide the how-to. They provide distribution. Yet distribution controlled by the platform is revocable. The knowledge you share is not. Your technical roadmap becomes their product backlog. Your deepest differentiation becomes their next feature launch.
3. The Build vs. Clone Shift
For decades, the strategic choice was Build vs. Buy. Today, for startups operating within a dominant platform's ecosystem, it has become Build vs. Clone.
Incumbents now run vendor evaluation processes not to select the best tool, but to identify the most threatening niche innovations. The evaluation is reconnaissance. Once a startup is flagged as high-potential, the incumbent's calculus is straightforward: licensing costs are avoided through internal replication, and the startup's user base is absorbed through platform lock-in.
Runlayer is not alone. This pattern repeats across SaaS, AI tooling, and infrastructure layers. The MCP space is particularly susceptible because openness invites scrutiny, and scrutiny enables cloning.
The Sociological Roots of Platform Power
Platform power is not merely economic—it is sociological. Market leaders leverage integration in two ways:
- Legitimacy signaling: A startup that lands a major platform integration gains credibility, but that credibility is fleeting. The platform controls the narrative of what is 'native' versus 'third-party.'
- Attention absorption: The startup's marketing, sales, and engineering resources are consumed by integration work. Meanwhile, the incumbent's parallel team builds the clone using insights from the collaboration.
The asymmetry is structural and cannot be solved by better contracts or more detailed NDAs. It requires a fundamentally different strategic approach.
The Contrarian Move: Platform-Agnostic Utility
The only durable defense is to build platform-agnostic utility—value that exists independently of any single ecosystem. If your product is a feature within a larger platform's infrastructure, you are not building a company; you are building a roadmap item for the incumbent. The moment your differentiation is fully expressed within that platform, you become replaceable.
The contrarian alternative:
- Atomic composability: Design your product as a standalone tool that integrates with any MCP-compatible environment. Do not optimize for a single platform's API at the expense of portability.
- Protocol ownership: Contribute to and leverage open standards where possible, but retain control over proprietary implementations that cannot be easily reverse-engineered through integration patterns.
- Parallel distribution: Never rely solely on a platform's marketplace or app store. Cultivate direct relationships with end users through channels outside the incumbent's control.
The Real Lesson for AI Builders
The Runlayer-Rippling incident illustrates the Integration Paradox clearly. For AI founders, the warning is straightforward: integration is not partnership. The incumbent's goal is to capture value, not share it. Your deepest technical differentiation becomes your greatest liability when dealing with a platform that can treat your innovation as discovery research.
At Mynd Labs, we advocate for building atomic, composable tools that resist total platform dependency. The most resilient startups create value outside the incumbent's immediate control—making your product a necessary layer rather than a replicable feature.
Architect for autonomy. Build for independence. The market rewards those who own their own roadmap.
Visit https://myndlabs.io to learn more about architecting for autonomy.