#

Key takeaways

• Product trials can create legal and commercial risk if access is not tightly controlled.

• NDAs and source-code rules need clear limits before any enterprise demo.

• Moroccan AI vendors should document who sees what, and why.

• Secure AI infrastructure needs governance as much as engineering.

• Language mix, procurement, and compliance can complicate enterprise sales in Morocco.

What happened

TechCrunch reported that Runlayer filed a lawsuit against Rippling over an alleged MCP gateway product copy. Runlayer says Rippling used information from a product trial to build a competing gateway. The claims include trade-secret misappropriation, unfair competition, and breach of contract.

Rippling denied misusing Runlayer IP. It said it is launching its own product with proprietary information. The report does not add Morocco-specific details, so the relevance for Moroccan readers is practical rather than local.

Why this matters for AI infrastructure vendors

The dispute is about more than one product. It is about how enterprise trials are run, what information is shared, and how teams document access. For Moroccan software vendors selling AI infrastructure, that is a direct business issue.

A secure Model Context Protocol gateway sits close to sensitive systems. That means trial access can expose architecture, prompts, integration patterns, and product direction. If controls are weak, a trial can become a governance problem.

Morocco context: why the lesson travels well

Moroccan vendors often sell into mixed environments. Buyers may want Arabic and French support, integration with existing systems, and careful handling of internal data. That can make trials longer and more complex.

In that setting, the basics matter. Teams need clear procurement steps, defined trial scopes, and written rules for source-code access. They also need to think about privacy, cybersecurity, and compliance from the start.

For Moroccan policymakers and enterprise buyers, the case is a reminder that AI infrastructure is not only about performance. It is also about trust, documentation, and control over sensitive information.

Practical use cases in Morocco

A Moroccan vendor offering an AI gateway, agent platform, or enterprise integration layer may face similar trial conditions. A bank, telecom operator, or large enterprise may ask for a proof of concept before purchase. That is normal, but it should be structured.

A practical approach would include limited demo data, named reviewers, and a written list of approved users. If source code must be shown, the vendor should define what can be viewed, copied, or tested. If the buyer needs deeper access, the contract should say so clearly.

For Moroccan readers, the same logic applies to internal AI projects. If a company tests a third-party gateway, it should track access, logs, and data flows. That helps reduce disputes later.

Risks and governance

The biggest risk in this story is not only copying. It is ambiguity. When trial terms are vague, both sides may later disagree about what was allowed.

That is why governance should cover several areas:

• *Data availability:

• only share the minimum data needed for the trial.

• *Procurement:

• define who approves access and who signs the trial terms.

• *Language mix:

• make sure Arabic, French, and English documents say the same thing.

• *Skills:

• assign someone who understands both legal and technical controls.

• *Infrastructure:

• separate trial systems from production systems.

• *Privacy:

• avoid exposing personal or confidential data without a clear basis.

• *Cybersecurity:

• log access, restrict downloads, and review permissions often.

• *Compliance:

• keep records that show what was shared and when.

These controls are useful in Morocco because enterprise buying often involves multiple stakeholders. Sales, engineering, legal, and procurement may all review the same trial. Without a single process, the risk grows.

What Moroccan vendors should do next

Start with the trial agreement. It should say what the buyer can test, how long the trial lasts, and what happens to shared materials after it ends. If the vendor uses source code, the agreement should be even more specific.

Next, limit access by default. Give the smallest practical set of permissions. Use separate environments for demos and pilots. Keep records of every file, build, and configuration shared during the trial.

Then review internal policy. Moroccan vendors should check whether their sales teams know when to involve legal or security staff. They should also confirm that customer-facing documents are consistent across languages.

Buyers should do the same. Before accepting a trial, they should ask what data will be used, who can see it, and whether the vendor will retain copies. That is especially important when the product touches sensitive enterprise workflows.

Bottom line

The Runlayer lawsuit is a reminder that AI infrastructure deals can carry legal risk long before a contract is signed. For Moroccan software vendors, the lesson is simple. Treat trials as controlled business processes, not informal demos.

That approach may not prevent every dispute. But it can reduce confusion, protect intellectual property, and support safer enterprise AI adoption in Morocco.