AI model ownership is a fool's errand. Here's what enterprises should do instead.

by Manish Sood, CEO of Reltio, an SAP company

Palantir CEO Alex Karp recently revived a familiar debate: Should enterprises own their AI models rather than rent intelligence from OpenAI, Anthropic, and other frontier labs?

Enterprise tech leaders are split along predictable lines. Sovereignty-minded executives want to own their weights. Pragmatists say renting is fine.

Both sides are arguing about the wrong thing. The better question is: What’s actually worth owning?

An AI model may offer the appearance of sovereignty, but it can quickly become a liability: a depreciating asset with a growing maintenance bill. Businesses would be better off owning the loop — the system around the model. That includes the proprietary data, business context, feedback, governance, workflows, and continuous learning that turn AI outputs into business results. Models can then be rented or replaced while the company retains control over the distinctive capabilities that create lasting value.

What AI model ownership actually requires

Building and maintaining a model is a never-ending project requiring a permanent team of infrastructure engineers and enough GPU capacity to keep them working. Even healthy enterprise budgets will struggle in these scenarios.

And the model starts losing ground the moment a frontier lab releases something better.

Every enterprise that pours budget into a model is buying a countdown clock, not independence. The weights do not appreciate or compound. They fall further behind the frontier until someone must retrain from scratch or admit the project became a liability.

The real asset is the loop

The model isn’t worth owning, but the loop is. That pipeline points a model at specific business problems and improves it against real business outcomes: the reinforcement learning cycle, a reward signal tuned to your workflows, and an evaluation harness that reveals whether the system is getting better or merely different.

That loop compounds in a way a static model file cannot. A model depreciates when a frontier lab ships something better. A well-run loop gains value with every cycle because it learns your business specifically.

That does not make a loop easy or cheap to run. It takes the same kind of standing team and infrastructure investment as trying to maintain a model in-house. The difference is what that investment buys you. Money spent maintaining a model buys you a slower rate of decay. Money spent running a loop buys you something that appreciates and compounds. One is a cost center disguised as sovereignty. The other is a critical asset.

That distinction is also why a loop is not for everyone. Many companies do not have the talent, infrastructure, or patience to run one well. Everyone says they want independence, but almost nobody’s checkbook agrees. It’s a textbook gap between stated preference and revealed preference.

There is a version of this that makes sense. A narrow, high-volume, well-defined workload, where a fine-tuned model can beat a generalist frontier model on that specific task at a fraction of the inference cost, is a legitimate case for building a loop. Done well, that loop becomes a genuine edge, a system that keeps getting sharper at exactly the problems that matter most to the business, in a way no rented model ever will.

The part even the loop-builders skip

There is a twist. Even the companies with the muscle to build a real loop are often skipping the hardest part of the problem.

A loop is only as good as the information feeding it. You can have a world-class fine-tuning pipeline, first-rate infrastructure, and a talented ML team, and still be training that loop on fragmented, duplicated data that can’t tell an agent which customer record, which supplier, or which product listing is correct.

Feed a loop that kind of input, and you do not get sovereignty. You get a model that is confidently wrong, and harder to catch because it sounds plausible.

These are the prerequisites that get skipped in almost every version of this debate, and it comes before “own your weights” or “own your loop.” Do you actually know who your customer is, consistently, across every system that touches them? Do you know which supplier record is current and which one is a duplicate from a merger three years ago?

Many enterprises cannot answer that cleanly, and no amount of RL infrastructure fixes it, because the loop just learns to be wrong more efficiently.

What to do before you build anything

Strip away the sovereignty language and the debate gets simple. A model is not an asset, no matter how much budget goes into building, acquiring, or maintaining one. A loop can be, but only for the narrow set of workloads that justify the investment, and only for companies willing to run it like the standing infrastructure commitment it actually is.

Even then, a loop is only as good as what it learns from. Own your loop if the workload justifies it. But you can’t own a loop built on data you don’t trust.

Learn how Reltio can help you build a trusted data foundation for enterprise AI.

This sponsored post was supplied by Reltio, an SAP company.