Claude or Open Source: The Five-Variable Framework

You sat in a meeting last month. Someone argued for Claude Managed Agents. Someone else argued for OpenClaw or a self-hosted setup. Both had bullet points. Neither had a decision. Six weeks later you still have not shipped an agent.

The fragmentation you are navigating is not in the AI ecosystem. It is in your decision framework.

Here is a different question to start with: which single variable would you be willing to sacrifice the other four for?

01Why Is This Decision So Confusing?

Because the options are not comparable on one axis. Claude Managed Agents, OpenClaw, LangGraph, vendor-native runtimes, and custom builds on MCP all call themselves agent platforms. They solve different problems.

Claude is managed infrastructure plus model access. OpenClaw is a runtime you host yourself. LangGraph is an orchestration library. Vendor-native agents lock to one application's workflows. Calling all of these "the agent choice" is like asking whether you should use AWS or Python.

The fragmentation feels overwhelming because the question is under-defined. Sharpen the question and the options collapse.

02What Are the Five Variables That Actually Matter?

Time to first ship. Cost at volume. Maintenance burden. Data sovereignty. Portability. Nothing else matters at the decision stage.

1. Time to first ship. Claude Managed Agents runs your first production agent in days. Self-hosted OpenClaw takes weeks to months depending on your team. If you have not shipped an agent before, you are buying velocity, not architecture.

2. Cost at volume. Under roughly 500,000 agent runs per month, Claude is cheaper when you price in engineering time. Past that threshold, self-hosted economics flip. Most SMBs are three zeros below that threshold.

3. Maintenance burden. Claude requires zero dedicated infrastructure engineers. OpenClaw or a custom build needs at least one. If you do not have that person, you will hire them or ship a broken agent.

4. Data sovereignty. Healthcare, finance, defense, and some EU-regulated verticals need self-hosted or private-cloud deployment. Everyone else is overthinking this. Anthropic's enterprise data terms are not weaker than your current CRM vendor's.

5. Portability. The variable most operators anchor to. MCP has largely solved agent-layer portability. Your prompts, tool definitions, and agent logic port between Claude, GPT, Gemini, and OpenClaw in days. Hosting ports in weeks. Vendor lock-in at the agent layer is not zero, but it is not what you think it is.

03Which Variable Should You Optimize For?

The one that is actually blocking you. Not the one that sounds most strategic at the board meeting.

For the 10-150 employee range, variables one through three dominate. Time to first ship, cost at volume, and maintenance burden decide this for 90% of companies. You are not losing this decision on portability. You are losing it because nothing is live.

For larger companies with existing ML infrastructure teams, variables two, four, and five carry more weight. Vendor lock-in becomes a real line item at that scale and the engineering capacity exists to run self-hosted.

For regulated verticals, variable four vetoes everything. If patient data or customer financial records route through the agent, self-hosted or private-cloud is the only option and the other variables fall in line behind that constraint.

This is the same pattern we saw in what 97 million MCP installs actually mean. The architecture decision looks ideological. It is operational.

04When Does the Answer Flip?

When your agent volume crosses the cost threshold, when you hire the infrastructure engineer, or when compliance constraints change. Not before.

A company shipping 50,000 agent runs today on Claude and targeting 5 million next year should architect portable. A company shipping zero runs and debating OpenClaw because "what if Anthropic raises prices" is architecture theater.

Pick the platform that optimizes the variable blocking you now. Revisit when a variable upstream changes.