Manus ownership affecting enterprise adoption

This is less a product question than a vendor risk question. Large companies can love what Manus does and still hold back if they are not sure which country really controls the company, where task data is processed, and who can keep the service running if regulators force another ownership change. That matters more for enterprise work than for consumer use, because the agent is touching internal documents, external apps, and long running workflows that cannot simply disappear mid process.1 2 3 4

• Manus is legally centered in Singapore through Butterfly Effect Pte. Ltd., but its roots, founders, and prior operations tie back to China, and China blocked Meta's $2B acquisition in April 2026 after reviewing the deal. That makes the control story harder to explain to procurement, security, and legal teams.1 4 5
• Operational continuity is a real issue for agent products because they run multi step tasks across browsers, code, search, and third party tools. Internal research on Manus shows these jobs can take 10 to 15 minutes and sometimes fail or loop, so enterprises will care who owns the stack and who is contractually on the hook if service access changes.2 3
• The comparison point is enterprise AI vendors that sell private deployment and tighter data control. Cohere describes North as running in the customer environment, while Manus has been discussed more as a cloud agent built on outside models and research infrastructure. That gap matters when buyers ask where data lives and what happens if a regulator or model provider cuts access.2 3 6

The likely destination is a more enterprise shaped Manus, with clearer jurisdiction, cleaner governance, and more explicit deployment options. If that happens, the product can move from impressive demo to approved system of record. Until then, the fastest growing part of the agent market will keep tilting toward vendors that can answer data location and continuity questions in one sentence.1 2 4 6