ChatGPT began as a consumer sensation, creating the illusion that this cycle would unfold like the web: new entrants would rapidly create new categories and use them to disrupt established players.
Instead, AI has revealed something fundamental about real intelligence. It depends on context: localized, proprietary, and often tribal knowledge.
Most of that knowledge is trapped inside enterprises, fragmented across dozens of systems, buried in operating processes, or held tacitly in the minds of the people who understand how the business actually works.
This is the central paradox of the cycle. The web advanced by democratizing distribution. AI can only continue advancing by unlocking the contextual intelligence held inside the enterprise vault.
But unlocking it is not merely a technical problem. Enterprises must be given a reason to participate without surrendering the core logic, knowledge and identity that make them valuable. They need to co-opt AI without allowing AI to absorb and ultimately replicate the entire business.
That is the essence of the transition: turning enterprise knowledge into machine intelligence without dissolving the enterprise itself.
Companies are not entering Enterprise AI. It is being entered by alliances.
A stack arrives as one motion. Compute underneath, a model in the middle, a governance layer on top, an integrator to wire it in. Each ally opens the floors below its hold and keeps the hold itself. This summer those alliances reordered in public. One player took the lead by naming the buyer’s deepest fear and giving it a single word. The largest model labs conceded the point — then started copying the motion they had just conceded to.
The mistake is to treat the vendor as the unit. Which model won. Which platform leads. Which chip is fastest. That is a category question. It cannot tell you the two things a purchase turns on: where value pools, and where you get locked in.
No enterprise buys a model. It buys a stack that has already decided how its members fit together.
The unit of competition is the alliance, not the firm.
Every player in that alliance is also playing its own book. The coalition is the gift. The book is the price.
A junction, here, is the layer everything routes through and leaving costs a fortune. An end is the layer you rent and swap. Score both from the buyer’s seat, not the pitch deck. You do not need the rest of the map.
Three kinds of alliance
They do different work. Read them together and you have the board.
The vendor-to-vendor stack. Two or more companies at different layers, entering as a single offer. A multi-layer stack, sold as one decision. The buyer is not choosing a model, a cloud, and an integrator in three meetings. The buyer is choosing a coalition that has already decided how those parts fit.
Nvidia and Palantir on a sovereign engine. Microsoft and OpenAI. Amazon and Anthropic. ServiceNow wiring Claude into workflow. Oracle and Palantir on sovereign cloud. Same species. Different books, visible the moment you ask the reading-rule question of each.
Identify which layer each ally opens, and which it holds. The generosity at the open floors is what makes the closed floor defensible. Partner today, rival at renewal.
Work it. Nvidia/Palantir: Nvidia opens the silicon and the open-weight model; Palantir opens the model too; neither opens the Ontology.
Microsoft/OpenAI: Microsoft opens the cloud and the identity plane the model runs through; OpenAI holds the model — and, as of this year, is climbing into the harness above it.
Amazon/Anthropic: Amazon opens the operational substrate; Anthropic holds the model, and now a services firm that puts it in.
ServiceNow/Claude: ServiceNow holds the workflow control plane; Anthropic opens the model into it.
Oracle/Palantir: Oracle opens sovereign cloud; Palantir holds the decision layer that lands on it.
The open floor is why the meeting happens. The held floor is why the renewal is expensive. If you cannot name both, you are reading the press release.
The substrate coalition. A signed industry structure whose membership list is the argument. The open-weights advocacy letter. The security alliance formed around shared agent-auditing tooling. These are not products. They are not stacks. They are declarations of whose economics depend on a given layer staying open or staying closed.
A vendor-to-vendor stack sells you a motion. A substrate coalition tells you which motion is even allowed. Who signed the security alliance told you which firms can live with a cheap, inspectable model layer. Who did not sign told you which firms cannot.
The most informative thing about a substrate coalition is never who signed. It is who didn’t. The absences draw the counter-coalition with more precision than the signatures draw the coalition.
This summer the absences were the closed frontier core. That was not a social fact. It was a map of who still needs the model layer to stay proprietary — and, as the rest of this piece shows, of who then spent the summer trying to occupy the floor above it anyway.
The enterprise-as-co-designer alliance. The customer is not a buyer. It is a member. Kirkland & Ellis, Centrus, McCarthy, a national health service, an integrator like PwC embedding at scale. The asset produced is not a licence. It is the customer’s own codified expertise — the judgment, the objects, the decision rights — written into a system the customer is told it controls.
Told. That word is doing the work. Co-design is the most flattering of the three species, and the easiest to misread. The enterprise arrives with its data and its hardest problem. It leaves having built. The asset has its name on it. Whether the asset can leave is a different question, and it is the only one that decides if membership was sovereignty or a very expensive onboarding.
The Sovereignty Bootcamp is this species, industrialised: a thirty-day cadence in which co-design is the sales motion, and the thing co-designed lives, from that day, in the vendor’s typed graph.
The summer ran through all three at once. Vendor-to-vendor stacks reordered around who holds the floor above the model. Substrate coalitions drew the line between firms that need the model closed and firms that need it cheap. Co-design became a demand engine. The through-line is a word. And a fact: every ally is playing a different book inside the same motion.
Each player is playing its own book
The coalition agreed on the entrance. It does not agree on the furniture.
Palantir holds the typed operating model of the business — the Ontology — and the decision surface that writes back into it. It opens everything beneath that floor: the model, the silicon, even the cloud in a sovereign configuration. It sells the open floors as sovereignty. It grows the held floor until the held floor is the company’s essence. The FDE was its invention. The bootcamp is the industrialised version. The vocabulary is alpha. Palantir does not need to win the model layer. It needs the model layer to become cheap.
OpenAI has rewritten its book in public. For two years the book was: hold the scarce model, let Microsoft open the cloud, let the API be the product. That book is no longer enough, and OpenAI knows it. The new book is two-track. Keep the model. Climb into the floor above it. In February it shipped Frontier — in its own language, “the underlying intelligence layer governing all of a company’s agents,” a “unified operating layer” whose Business Context connects warehouses, CRMs and internal apps and builds “durable institutional memory.” In May it stood up the OpenAI Deployment Company, majority-controlled, seeded with more than four billion dollars, and acquired Tomoro for roughly 150 forward-deployed engineers on day one. In July the same vehicle agreed to acquire Northslope, founded by former Palantir FDEs, adding hundreds more. OpenAI is no longer only selling tokens. It is trying to own the harness those tokens run inside, and the people who wire that harness in.
Anthropic is adjacent, not identical. Hold the model. Differentiate on trust. Let partners open the workflow — ServiceNow, the clouds, the integrators. The new chapter is implementation. In May a joint venture with Blackstone, Hellman & Friedman and a PE consortium acquired Fractional AI. In July it launched as Ode: Claude-first, not Claude-exclusive, a services firm whose job is to put Claude into companies that cannot staff the implementation themselves. Anthropic is not, yet, shipping a named ontology. It is buying the human layer that used to sit between the model and the customer’s operating system. Labour and pattern, not a typed graph. Still a junction.
Nvidia opens the weights and the sovereign engine, convenes the security alliance, and keeps the floor that does not travel: the instruction set. It can sit on every coalition because the silicon is downstream of every one of them. The open-weight letter is substrate politics in service of that book.
Microsoft and Amazon hold the control plane of the cloud they already own. Identity, tenancy, the governance catalog, the bindings that make a “portable” model operationally immovable. Microsoft’s alliance led with OpenAI and now runs Palantir on Azure as well. Amazon’s led with Anthropic. Both have stood up their own forward-deployed motions. They do not need to win the model. They need whichever model you pick to run inside a control plane that does not export.
The alliance is how they enter. The book is what they keep.
Why Palantir took the lead
For two years, the center of gravity was the frontier lab. The model was scarce. The labs held it. Every stack organized itself around whose model sat in the middle. Microsoft led with OpenAI. Amazon led with Anthropic. The lab was the sun.
Palantir refused to organize around a model at all.
The Nvidia partnership is the cleanest expression. A sovereign engine, open-weight Nemotron, on the customer’s own hardware, air-gapped and classified, the customer owning the resulting weights and the training data. Read it through the rule. Nvidia opens the silicon and the model. Palantir opens the model too — swap it freely. What neither opens is the layer that binds the customer’s data into a typed, live operating model of the business, and the decision surface built on top of it.
That layer is Palantir’s. It does not travel.
Everyone else organized the alliance around the layer they wanted to hold. Palantir organized it around the layer the buyer most fears losing, then opened everything else, so the held layer would look like sovereignty rather than lock-in.
The Ontology is a live, typed model of the business — objects, relationships, action types, decision rights — that the rest of the stack writes against. The model underneath is interchangeable. The Ontology is not. Swap OpenAI for Anthropic for an open-weight model on your own iron. Nobody cares. You cannot take the decision graph with you when you walk.
The model is a decoy. Palantir hands you the one freedom that no longer matters, and keeps everything that compounds.
That is a genuine improvement on what the labs were selling two years ago. It is also, still, a lock-in. Both facts have to be held at once.
The improvement that is still a lock-in
Score Palantir against the closed-frontier default, honestly.
The first lab offer was a gravity well. The model was the product. Context, memory, and a meaningful share of enterprise state lived, at least in part, on the lab’s infrastructure. Retention was justified as safety — catching attacks that span many requests — and had the convenient property of keeping the company’s working memory on the vendor’s side of the wall. The switching cost was not a contract. It was judgment, migrating.
Palantir’s offer is better than that, and it is not subtle. The model is portable by design. The sovereign engine can run on the customer’s hardware. The FDE and the bootcamp build on the customer’s own data. Relative to “your alpha lives in our model, on our servers, metered by our tokens,” this is a structural upgrade. Anyone pretending otherwise is arguing from a prior.
Then look at where the company’s essence goes.
The Ontology is not a dashboard. It is the place the business is rewritten as objects, links, action types and write-backs. Once that rewrite is done, the Ontology is no longer a view of the company. It is the company, as far as the operating system is concerned. New decisions execute against it. New agents read it. New employees learn it. The longer it runs, the more the enterprise’s alpha — the codified judgment, the proprietary data model, the operational know-how — lives there, rather than in the heads and systems of record it was extracted from.
Palantir’s proposition is a real improvement over full lab lock-in. The model is no longer the cage. The cage moved one floor up.
So the honest question is not whether Palantir is better than OpenAI. It is whether the Ontology is portable.
Palantir’s own documentation is more precise than the pitch. There is an export. Ontology Manager dumps a working state to JSON and imports it back — to edit in code, or to copy one Ontology to another Ontology. On the same page, Palantir tells you not to depend on the exported schema, because it may change. Conditional formatting cannot be imported to an Ontology other than the one it came from. This is a Foundry-to-Foundry working-state tool. It is not an exit.
What does not travel as a running system: the action-types and validation engine, the write-back path, the decision graph as a live object, the Workshop surfaces, the accumulated operational state that makes leaving cost more every day you stay. You can, with enough engineering, recover a picture of the objects and links. You cannot pick up the company’s essence and set it down on a competitor’s platform on Monday.
There is an export. It is not a portable Ontology.
If the layer that holds your alpha cannot leave, you have not bought sovereignty. You have chosen a better landlord.
Against the original lab offer, Palantir is the less extractive deal. Against the standard the sovereignty pitch itself sets — your alpha stays yours — the Ontology fails the test. The doctrine is correct. The implementation is the junction the doctrine told you not to cede.
The labs understood the enterprise. Then they tried to buy it.
An API is an end. A pilot is a conversation. Production is a person sitting inside the customer’s mess — the identity graph, the legacy systems, the approval chain, the data that is not in the warehouse — and building a system that writes back.
Palantir named that person a forward-deployed engineer more than a decade ago. Until 2016 it had more of them than software engineers. The industry spent two years pretending the model had made that job obsolete. This summer it spent billions admitting it had not.
OpenAI’s Deployment Company launched in May, majority-controlled, seeded with more than four billion dollars, and acquired Tomoro for roughly 150 FDEs from day one. In July it agreed to acquire Northslope, its second such deal, adding hundreds more. Northslope was founded by former Palantir FDEs. OpenAI is not approximating Palantir’s labour model. It is importing it, including the people who used to perform it for Palantir. The official post even leaves the door open to joint commercial engagements with Palantir after close. Copy, hire, and partner, simultaneously. That is not confusion. That is a player paying to hold all three options.
Anthropic made the same admission on a different structure. The May joint venture acquired Fractional AI as its operating core. In July it launched as Ode: standalone, Claude-first, not Claude-exclusive, aimed at companies that cannot staff the implementation. Anthropic’s internal team keeps the strategic deployments. Ode industrialises the rest. The book is still the model. The new chapter is that the model does not enter the enterprise without a human layer Anthropic now owns a piece of.
The hyperscalers followed. The job title Palantir invented is now a standard line item in how the largest software vendors sell.
Enterprise deployment is not an API problem. It is an FDE problem. The closed frontier is not partnering its way into that motion. It is acquiring the companies that already know how to do it.
The labour is the admission. The product is the tell.
OpenAI Frontier is not ChatGPT with a tighter SLA. In OpenAI’s own framing it is the platform that should govern all of a company’s agents: Business Context as a shared semantic layer; Agent Execution against systems of record; evaluation loops so the agents improve with use; agent identity so permissions attach to the coworker, not the chat window. The Enterprise Frontier Program then pairs that platform with FDEs from the Deployment Company. The language is Palantir’s, translated. Durable institutional memory. Unified operating layer. Agents that write back. A human in the building to make it real.
It is not Palantir’s Ontology. Not yet. Frontier’s Business Context is a semantic layer designed to be built by operators and pointed at existing systems. Palantir’s Ontology is a typed, live decision graph with action-types and no meaningful export path, grown over years of FDE labour inside the hardest environments on earth. Depth is not direction. The direction is the same. OpenAI has decided the model is no longer enough of a junction, and is building the floor above it.
It is also not yet a completed lock-in. Frontier is younger. The semantic layer is shallower. The FDE bench is acquired, not native. The Deployment Company is capitalised by a PE and SI consortium whose incentives are not a research lab’s. Scaling a high-touch labour model is Palantir’s unsolved problem, not OpenAI’s solved one. Anyone who tells you Frontier has already replaced Foundry is selling a slide.
The correct reading is more uncomfortable than either pole.
OpenAI is rebuilding a Palantir-like harness from the model side. If it works, the buyer faces two ontology landlords — and the newer one still owns the model underneath. If it fails, Palantir’s lead hardens, because the labs will have spent the year proving the junction really did move above the weights.
Either way the question does not change. Which layer is being opened, and which is being held? Frontier is an escape from a single-model cage only if Business Context and the agent graph can leave. Watch the export, not the brochure. Palantir already answered that question, in its own docs, for its own Ontology. OpenAI has not yet been forced to.
The founding argument
At the second Sovereignty Bootcamp this August, Palantir’s chief executive did not open with product. He opened with the company’s founding.
The founding problem, as he told it, was counter-terrorism under constitutional constraint: how do you find the people trying to attack innocents without destroying the civil liberties of everyone else? Solving it forced the company deep into data integration, and produced an architecture with a specific property — the ability to do very intricate work on very sensitive data while keeping complete control over who sees the insight and who controls the underlying data. Privileged insight, on privileged data, shared inside the organisation, control retained at every step.
Then the pivot, and it is the whole argument in one line. A large language model is a very powerful and very dangerous raw material. The question is how you extract value from it while making sure the value you create stays inside your enterprise. You can use the labs’ models. You make sure the alpha is not migrated out by using an application layer — an ontology — to capture the value, so it never leaves your building to end up in a competitor’s hands, or in the hands of a company that will one day try to kill you.
This is a rhetorical move of real quality. Understand why it works rather than simply be moved by it. It takes a diffuse anxiety about AI and routes it through an architecture the audience already respects: the counter-terror system that balanced surveillance against liberty. The thing that let us find terrorists without shredding the Fourth Amendment is the same thing that lets you use a frontier model without surrendering your edge. Control the insight. Control the data. Keep both inside.
Whether or not the analogy holds all the way down, it converts a technical argument about data boundaries into a story about sovereignty, and attaches that story to a word the audience will remember.
The word is alpha. The threat is that the providers of your key instruments want the alpha of your business inside their model — so you end up powering someone else’s business in return for paying for their tokens.
Hold the sentence up against the Ontology. The alpha is protected from the model. It is not protected from the application layer that captured it. The speech is true about the labs. It is silent about the floor Palantir holds. That silence is not a lie. It is the book.
The demand engine
A vocabulary is not a movement. Palantir built the demand engine to match the argument.
Two Sovereignty Bootcamps in under thirty days. Organisations building on their own data, on infrastructure they control. Nearly two hundred of them, spanning healthcare, construction, media and defence, with speakers from Nvidia, Cisco, Novartis and NATO. Sovereignty over your alpha, offered as something you can attend a workshop to acquire, and leave having built.
A bootcamp is not a sale. It is a co-design session — the third kind of alliance, industrialised. The enterprise arrives with its data and its hardest problem. It leaves having built on infrastructure it controls. The asset belongs to the customer. And lives, from that day, in the Ontology.
Every graduate leaves more deeply bound to the layer that did the binding.
Does value compound in place, so that leaving costs more every day you stay? A price-competed model fails that test. A live decision graph, written against during a workshop on your own data, passes. That is why the bootcamp is a more defensible growth motion than any vendor-to-vendor stack, and why OpenAI’s Deployment Company and Anthropic’s Ode are attempts to buy a version of the same motion rather than invent it.
Palantir took the lead not because it had the best model. It has no model. It took the lead because it was the first to organise an alliance, a sales motion, and a vocabulary around the buyer’s deepest structural fear, at the moment that fear became acute.
The concession — and the climb
The realignment is real because the labs moved their own boundary.
Through the summer they defended a posture in which enterprise data and state lived, at least in part, on the lab’s infrastructure. Palantir spent those same weeks arguing that this was the mechanism by which enterprises lose control of their alpha. Within weeks both of the largest labs restructured. One let enterprise customers keep retained data on their own cloud. The other previewed retaining none of it, piloted with a data platform and a hyperscaler. They will not call these concessions. The boundary moved anyway, in the same window, in the same direction.
That was the response to last year’s fear. The response to this year’s is Frontier, DeployCo, Ode, Northslope, Fractional AI. The labs did not just give the data back. They went upstairs.
The first signature of a realignment is a competitor changing its architecture. The second is the competitor then trying to occupy the floor it just admitted matters.
What the lines now say
The board has redrawn around one axis. Openness below the junction. Ownership at the junction.
The substrate coalitions fell on that line. Nvidia’s open security alliance drew in the data incumbents, the integrators, the chip vendor, the enterprise-facing platforms — Microsoft, IBM, Palantir, ServiceNow, Salesforce, Snowflake, Databricks, Hugging Face, LangChain among some forty founding members. The four names absent were the closed frontier core: OpenAI, Google, Anthropic, Meta. A map of whose economics depend on the model staying proprietary.
If you own the model, you need it closed and valuable. If you own the floor above the model, a cheap model is pure tailwind.
The enterprise-facing coalition wants the model to be a commodity. The labs need it not to be. Palantir sits at the sharpest point of that alignment, which is why it could be the loudest. Every open-weight declaration, every sovereign engine, every bootcamp drives the model toward commodity. Every inch it moves raises the value of the Ontology.
The roster does not show the new instability. The labs are trying to sit on both sides of the line. Keep the model closed. Build or buy the floor above it. You cannot forever charge rents on a layer you are also trying to commoditise from above, and you cannot forever claim the upper floor is the customer’s if your FDE built it on your semantic layer. Something gives. Watch which rent they defend at renewal. That is the book.
The wider frame
The CEO’s closing argument at the bootcamp was not about software. A functioning society cannot have all the value flow to a couple of thousand people in Silicon Valley. The way to head off the fissures pulling societies apart is for a broad base of institutions to be stronger, healthier, more sovereign, rather than dependent. The enterprise keeping its own alpha is, in this telling, a distributive stance about where the gains from AI accumulate.
Discount it for coming from the vendor who profits if you believe it. The structural observation survives the discount.
Value does not spread evenly. It pools where switching costs accumulate, and drains from where substitutes are one API call away. If the deepest junctions concentrate at a handful of frontier labs, the surplus of the transformation concentrates there too. If they concentrate instead at a handful of ontology landlords, the surplus has moved, not distributed. Only if thousands of enterprises hold their own decision layers — on terms they can leave — does the surplus actually distribute.
A portable junction is the only version of that fight the buyer should be willing to fund.
What it means for your alpha
Your alpha is the codified judgment, the proprietary data model, the operational know-how that makes you competitive. It is not protected by choosing the right model. The model is the layer everyone is racing to make cheap. Alpha is protected or surrendered at the floors above it: where data is bound into a business model, where decisions execute, where evaluations and workflow logic accumulate. That is the junction.
Palantir was first to say this out loud, and first to productise it. That is why it led. The refinement is that “above the model” is not automatically “with you.” An Ontology that cannot leave is a move of the company’s essence into a vendor’s typed graph. A Frontier Business Context that becomes the institutional memory of the firm is the same move, attempted from the other side. An Ode engagement that encodes your operating patterns in a services firm you do not own is a softer version of the same move.
Do not ask whose model is in the middle. Ask which layer this coalition is opening, which it is holding — and whether the held layer can leave.
If it cannot, you have not bought sovereignty. You have rented it from a new landlord, however open the floors beneath it. Palantir is a better landlord than the original lab offer. It is still a landlord. OpenAI is spending billions to become one. Anthropic is buying the staff. The doctrine they are all now selling is correct. Each of them is selling it implemented at the layer that happens to be their own.
Read every alliance the same way. The one waving the sovereignty flag. The one rebuilding the harness. The one that just acquired the FDEs. Which layer opens, which layer stays, and whether the staying layer has an exit that is a running system rather than a JSON file. Not the logo in the middle. Not the eloquence of the pitch. That answer is the map of where your alpha will be in three years.
The mental models
Five models carry the piece. They work without the rest of the map.
Alliance, not firm — and book, not alliance. The thing that arrives is a pre-assembled coalition. Score the motion, not the logo. Then score the book inside the motion. Palantir, OpenAI, Anthropic, Nvidia, Microsoft, Amazon can enter together and still be keeping four different floors. If you only read the coalition, you buy the gift.
Open below, hold at the junction. Every alliance opens the layers it can afford to commoditise and keeps the layer where leaving would hurt. Palantir opens the model and holds the Ontology. OpenAI is trying to keep the model and grow Frontier as the floor above it. Anthropic keeps the model and is buying the implementation layer. Nvidia opens the weights and holds the instruction set. Ask it of every coalition, including the one selling you sovereignty.
The lock-in gradient, not the lock-in binary. Palantir is a real improvement on the original lab offer: model-portable, runnable on your iron, data not retained as a matter of architecture. That does not make it portable. The company’s essence migrates into the Ontology. Official export is a Foundry-to-Foundry dump whose schema you are told not to depend on. Better landlord is not sovereignty. Score the gradient or you will be talked from one cage into the next.
Read the absences — then read the copies. Who did not sign the security alliance told you the model layer’s politics. Who then acquired FDE firms told you the next layer’s. The closed frontier sat out the substrate coalitions and spent the summer buying the labour model those coalitions were built around. Absence, then imitation. That sequence is the realignment.
Alpha lives above the model — and above is not automatically yours. The scarce thing is no longer the weights. It is the accumulated judgment, the typed operating model, the decision surface that writes back. Palantir taught the market that vocabulary and holds the junction the vocabulary describes. OpenAI is now building the same junction from the other side, in public, under its own name. Protecting alpha is not a model choice. It is an exit choice. If the layer that holds the essence cannot leave as a running system, the essence has already moved.
Carry those five into the next procurement. The rest of the piece is how they were proven, this summer, in public.
With massive ♥️ Gennaro Cuofano, The Business Engineer