“What I am claiming – obviously slightly true but slightly self-centered – is that it is the model plus an application layer plus compute.” – Alex Karp – Palantir CEO
Enterprise artificial intelligence has reached a peculiar moment in which the technical breakthrough of large models collides with a far more prosaic problem: who actually captures value, and on what stack of technology and infrastructure that value depends.1 For years, boardrooms were sold the idea that raw model capability was the centre of gravity in AI, with performance benchmarks and parameter counts framed as the decisive differentiator.1 Yet across defence, critical infrastructure, and heavily regulated industries, the practical experience has been very different: organisations are spending on tokens and API usage while struggling to convert that spend into durable advantages, and simultaneously worrying that their proprietary knowledge is being siphoned into someone else’s asset base.1,19 The growing backlash from these enterprises, which Alex Karp channels quite bluntly in his CNBC appearance, reflects a deeper realisation that the true AI stack inside a serious business is not a single model but a tightly coupled combination of model, application layer, and compute footprint, controlled in ways that preserve sovereignty over data, logic, and alpha.1,7
The real enterprise AI stack: beyond the frontier model
The starting point for understanding the statement is the tension between frontier labs that lead model development and enterprises that must operationalise those models inside mission-critical environments.1,7 Frontier labs have understandably emphasised the power of their models: general-purpose reasoning, multimodal capabilities, emerging agentic behaviours.12 This narrative has supported pricing structures based on token consumption and premium tiers that map directly to model access.6,19 But in the contexts Karp emphasises – battlefield systems, manufacturing lines, highly regulated clinical or financial workflows – raw model capability is only one third of the operational challenge.1
First, the model itself must be constrained, contextualised, and integrated into the organisation’s semantics, processes, and control regime.14,17 That is the function of an application layer, which in Palantir’s vocabulary is built around the Ontology: a digital twin of the organisation that encodes entities, relationships, business logic, permissions, and allowable actions.11,14,17 Second, the entire arrangement must sit on compute infrastructure that is not merely performant but strategically owned or governed: GPUs, storage, and orchestration that can be deployed in sovereign environments, air-gapped systems, or hybrid clouds, under the enterprise’s own control of weights and deployment pipelines.1,20,28 The claim that value lies in “model plus application layer plus compute” is thus a direct challenge to the idea that selling remote access to a frontier model is sufficient to win the enterprise market.
In practical terms, this reframing takes aim at the widespread situation where enterprises experiment with powerful models in pilot projects, achieve eye-catching demos, and then stall when asked to move into production at scale.6,21 Analysts tracking enterprise AI adoption repeatedly note a gap between proof-of-concept enthusiasm and sustained operational deployment, driven by unresolved issues around data governance, integration, and security.3,12,21 Karp’s point is not that frontier models lack capability; on the contrary, he calls their builders “world historic” and treats open-weight and closed-weight models as interchangeable components.1 The issue is that, absent a robust application layer and controllable compute, the model becomes an external service whose economics and data behaviour are misaligned with the long-term interests of the enterprise.
Ontology and the application layer: turning models into operational value
The application layer Karp refers to is not a thin user interface or a set of ad hoc scripts sitting between the model and a few databases.1,7 It is a structured operational substrate that captures how the organisation understands itself and how it wants AI systems to interact with its reality.14,17,23 In Palantir’s documentation, the Ontology is described as the central system that enables customers to safely, securely, and effectively leverage AI in their enterprises.14 It represents operational decisions as combinations of data, logic, action, and security, meaning that every AI intervention is grounded in a governed schema of what entities exist, what can be done to them, and under which constraints.14
Independent analyses of Palantir’s Ontology converge on the view that it functions as a digital twin of the organisation rather than a simple semantic layer.8,11,17 It maps business objects, events, and relationships across systems, while also embedding kinetic elements such as actions, workflows, and dynamic security rules.8,17 This design means that when a large language model or agentic system is connected through AIP or Foundry, it does not interact directly with raw tables or arbitrary APIs; it interacts with a curated, governable representation of reality.2,5,20 The application layer thereby constrains what the model can do, routes its outputs into executable workflows, and logs and audits every step.
The strategic claim embedded in Karp’s comment is that without such an application layer, enterprises will either underutilise models or expose themselves to unacceptable risks.1,7,14 Security experts observing frontier AI have already warned that powerful models radically compress the time between vulnerability discovery and exploitation, shifting security from volume measurement to exposure management.9,15,18 In an environment where models can autonomously chain vulnerabilities, craft exploits, and orchestrate complex actions, the absence of an operational control layer becomes a systemic risk.18 An ontology-like layer provides precisely the context, constraint, reversibility, and transparency that emerging AI security frameworks identify as prerequisites for “trusted autonomy”.18 It defines not only what data the model sees, but what consequences its recommendations can trigger and how those consequences are bounded.
Compute, control, and the ownership of alpha
The third element in Karp’s triad – compute – is not simply a reference to cloud capacity or GPU availability.1,7 It is a shorthand for physical infrastructure, deployment topology, and the economic and strategic control of that stack.1,20,28 Palantir’s partnership with NVIDIA, which triggered the CNBC segment, is framed explicitly around giving technical customers control over their compute, their models, their data stack, and their alpha, so that they “own the means of production” rather than having it quietly transferred to others.1,4,28 In manufacturing environments, the company highlights packaged compute and GPU acceleration delivered in form factors that scale from factory floors to distributed edge deployments, all integrated with the Ontology and AI platforms.28
This focus on compute sovereignty responds directly to the unease Karp reports from clients who worry that frontier labs are accumulating de facto control over model weights and training regimes using enterprise data.1,19 If an organisation’s proprietary processes, failure modes, and optimisation strategies are repeatedly fed into external models, and those models are then monetised as general services, the organisation risks subsidising a competitor’s asset base with its own alpha.1,19 By contrast, owning or tightly governing compute that hosts open-weight models – whether in classified defence settings or private industrial contexts – allows enterprises to train, fine-tune, and deploy models while retaining legal and operational control over weights.1,22
Some third-party analyses of enterprise AI stacks have started to codify this intuition into design diagrams that explicitly separate model, orchestration, security, data governance, and infrastructure layers.24 In such architectures, the model is treated as a pluggable component: organisations may use closed frontier models for certain tasks and open-weight models for others, but always through an application layer that enforces local semantics and policies, and on compute they control or at least contract under stringent terms.12,24 This sits squarely with Karp’s insistence that Palantir’s products are agnostic, able to switch between models, but not agnostic about who owns weights and who answers basic questions about data retention, caching, and competitive entry.1
The tokenomics backlash and mis-sold AI
The backstory to Karp’s remark is his broader critique that “something has gone completely wrong” with how AI is sold to enterprises.1 He characterises the prevailing sales motion from frontier labs as one where enterprises are encouraged to “chillax and waste time with tokens”, receiving limited operational value while handing over intellectual property.1,19 Reports of private conversations with CEOs suggest a growing frustration: they feel they are paying for token usage that does not translate into improved margins, resilience, or differentiated capability, and they suspect that their data is being used to improve someone else’s product.1,19
This critique aligns with independent commentary that describes Karp as “demolishing” the economic model of frontier labs on live television, framing it as a wealth tax on enterprises that ultimately fuels calls for broader wealth taxes in politics.7,16,19 The argument runs as follows: if AI has been oversold, enterprises will overpay for capabilities that do not show up in free cash flow or competitive positioning, and the resulting disconnect between tech valuations and real-economy benefits will reinforce populist demands to tax wealth more aggressively.1,7,19 Karp’s counter-position is that AI, properly deployed as model plus application layer plus compute, is already changing the course of history in contexts such as Ukraine, Israel, and American critical infrastructure, without needing to be triply oversold.1,20
The financial subtext here is important. Palantir points to its own financials, where the application layer (ontology) and compute components are described as the only parts of the stack that directly make money and generate free cash flow.1 The implication is that frontier labs optimising for token revenue on shared models may be chasing a less durable business than platforms that own the application and infrastructure layers where enterprises are willing to pay the true cost of operational transformation.7,24 This does not require frontier labs to fail; it simply implies that their long-term profitability in the enterprise segment may depend on embracing architectures that give customers stricter control over data, weights, and compute.
Debates, objections, and competing visions
Karp’s formulation is not uncontroversial. One line of objection argues that application layers can be built by enterprises themselves or by systems integrators and hyperscalers, using more generic orchestration tools, data fabrics, and semantic layers, rather than relying on a single vendor’s ontology.6,9,24 Advocates of this view point to emerging platforms like OpenAI’s Frontier, which position themselves as enterprise AI agent platforms capable of integrating with existing systems, managing identity and permissions, and providing evaluation tooling, effectively offering their own application layer atop multiple models.6 From this perspective, the value may sit in whichever platform best coordinates agents, workflows, and governance, rather than in any one company’s specific ontology implementation.
A second objection concerns lock-in and concentration of power. Critics of Palantir’s Ontology have described it as both a deep moat and a potentially dangerous one, precisely because it embeds a customer’s operational reality so tightly into a proprietary semantic and kinetic model.8 Once business logic, decision flows, and security regimes are encoded into the ontology, switching providers becomes non-trivial.8,11 This raises legitimate questions about long-term dependency, bargaining power, and the ability of states or enterprises to maintain technological sovereignty when their digital twin sits on someone else’s platform.
There is also a broader strategic debate about openness and public access to powerful models.12,15 Some researchers and civil society groups argue that restricting access to frontier models in the name of security may slow innovation and entrench incumbents, while others worry that unrestricted global access gives adversaries tools that outpace defensive capabilities.3,12,15 Karp’s stance, which condemns the idea of denying models to domestic defence departments while providing them to adversaries, sits within this contested space.1,22 The model-plus-application-layer-plus-compute framing tends to favour architectures where governments and critical infrastructure operators host open-weight or tightly governed models on sovereign compute, mediated by robust application layers, rather than relying on public, general-purpose access.
Why the triad matters: trust, sovereignty, and the next phase of AI
Despite these debates, the triadic framing illuminates the shift in what sophisticated customers increasingly demand from AI vendors: trust, deployment realism, security, and ownership of both the application layer and physical infrastructure.4,21,23 Surveys and practitioner accounts point to data quality, retrieval robustness, and governance as primary barriers to moving AI from pilot to production.21,24 The organisations that are actually running AI in critical contexts – defence operations, industrial control systems, pharmacological research – do not treat models as curiosities but as components in carefully governed systems where the margin for error is thin.2,3,14
In that environment, the backstory to Karp’s statement is less about rhetoric and more about architectural necessity. Enterprises must decide whether they are comfortable with a world in which their data, processes, and alpha are repeatedly exposed to external frontier models under token-based economic schemes, or whether they want a world where they own the semantic and operational representation of their business, host or contract compute under stringent sovereign terms, and treat models as interchangeable engines plugged into that stack.1,4,24 The comment that the claim is “slightly true but slightly self-centred” acknowledges Palantir’s commercial interest in such a world, but the direction of travel in independent enterprise AI discussions suggests that many large organisations are converging on similar requirements, whether or not they adopt Palantir’s specific products.3,12,24
The broader implication is that the frontier of value in AI is moving away from raw model performance and towards integrated systems that can be trusted to operate autonomously – or semi-autonomously – in high-stakes environments.18,21,23 Those systems require a substrate where humans and AI collaborate through shared context, governed actions, and transparent reasoning.23 They require compute architectures that can run at the edge, in classified environments, and across multi-cloud topologies without ceding control of weights and data.20,28 And they require economic models that align incentives: enterprises willing to pay the true cost of transformation, vendors willing to respect sovereignty rather than monetise every token, and regulators capable of distinguishing hype from systems that genuinely change outcomes on battlefields, factory floors, and hospital wards.1,3,12
References
1. “Palantir CEO Alex Karp says ‘something has gone completely wrong’ with how AI is sold” – https://www.cnbc.com/video/2026/07/01/palantir-ceo-alex-karp-says-something-has-gone-completely-wrong-with-how-ai-is-sold.html
2. Palantir CEO Alex Karp on what customers actually want, the real … – 2026-07-01 – https://www.linkedin.com/posts/palantir-technologies_palantir-ceo-alex-karp-on-what-customers-activity-7478094653213282304-yAR6
3. AIP architecture overview – Palantir – 2021-12-14 – https://palantir.com/docs/foundry/architecture-center/aip-architecture/
4. How enterprise security needs to plan for frontier AI models – IBM – 2026-06-03 – https://www.ibm.com/think/insights/rethinking-readiness-how-enterprise-security-needs-to-plan-for-frontier-ai-models
5. Alex Karp the CEO of Palantir just said the quiet part out loud about … – 2026-07-01 – https://www.linkedin.com/posts/daniel-arbour_alex-karp-the-ceo-of-palantir-just-said-the-activity-7478184912106381312-6sCa
6. Run Palantir Foundry and Artificial Intelligence Platform on OCI – 2024-11-04 – https://docs.oracle.com/en/solutions/palantir-foundry-ai-platform-on-oci/index.html
7. OpenAI Frontier: Close the Enterprise AI Opportunity Gap-or Widen … – 2026-02-09 – https://futurumgroup.com/insights/openai-frontier-close-the-enterprise-ai-opportunity-gap-or-widen-it/
8. Tokenomics – the worldview according to Palantir as CEO Alex Karp … – 2026-07-03 – https://diginomica.com/tokenomics-worldview-according-palantir-ceo-alex-karp-lays-openai-and-anthropics-effing-insane
9. Why Palantir’s ontologies are its deepest (and dangerous) moat – 2026-02-18 – https://blog.pangeanic.com/why-palantirs-ontologies-are-its-deepest-and-dangerous-moat
10. Securing the enterprise in the frontier AI era – Mantel Group – 2026-06-24 – http://mantelgroup.com.au/enterprise-ai-security-five-steps-to-secure-your-business-in-the-frontier-ai-era/
11. Palantir Technologies – Wikipédia – 2015-01-30 – https://fr.wikipedia.org/wiki/Palantir_Technologies
12. Palantir Ontology Explained: Why It’s the Operating System for … – 2026-05-10 – https://zerofuturetech.substack.com/p/palantir-ontology-explained-why-its
13. Frontier AI Explained: Key Models, Players, and Business Impact – 2026-05-26 – https://www.crowdstrike.com/en-us/cybersecurity-101/artificial-intelligence/frontier-ai/
14. Avec Palantir, le plan «ontologique» d’Alex Karp et Peter Thiel pour … – 2025-08-06 – https://legrandcontinent.eu/fr/2025/08/06/palantir-ontologie/
15. Why create an Ontology? – Palantir – 2021-12-14 – https://palantir.com/docs/foundry/ontology/why-ontology/
16. Advisory on Risks associated with Frontier AI Models – https://www.csa.gov.sg/alerts-and-advisories/advisories/ad-2026-004/
17. Le CEO de PALANTIR, Alex Karp vient de démonter le modèle … – 2026-07-02 – https://fr.linkedin.com/posts/lchevet_le-ceo-de-palantir-alex-karp-vient-de-d%C3%A9monter-activity-7478375997017591808-GhU3
18. Palantir Ontology: Architecture & Benefits – PuppyGraph – 2025-09-21 – https://www.puppygraph.com/blog/palantir-ontology
19. Frontier Models Prompt Need for New AI Security Framework – 2026-06-09 – https://www.forescout.com/blog/frontier-models-prompt-need-for-new-ai-security-framework/
20. Le PDG de Palantir, Alex Karp, critique la tarification des jetons d … – https://fr.qz.com/palantir-karp-openai-anthropic-prix-des-tokens-entreprises-070126
21. AI Infrastructure & Ontology | Palantir & NVIDIA – 2025-10-28 – https://blog.palantir.com/ai-infrastructure-and-ontology-78b86f173ea6
22. The AI Trust Paradox And What Must Change In 2026 – YouTube – 2026-01-26 – https://www.youtube.com/watch?v=YgEPviY4rwo
23. Palantir CEO Alex Karp on frontier AI models – Facebook – 2026-07-01 – https://www.facebook.com/cnbc/videos/palantir-ceo-alex-karp-on-frontier-ai-models/1569245778361592/
24. Palantir Chief Architect on Ontology and AI collaboration – LinkedIn – 2025-08-27 – https://www.linkedin.com/posts/palantir-technologies_the-ontology-is-the-substrate-through-which-activity-7366485022259810304-JLs1
25. From Frontier AI Models to Enterprise Outcomes – LinkedIn – 2026-06-27 – https://www.linkedin.com/pulse/from-frontier-ai-models-enterprise-outcomes-navveen-balani-tcr9f
26. Palantir CEO Alex Karp says open-weight models are a potential … – 2026-07-01 – https://www.instagram.com/reel/DaQ2KPIjI2S/
27. The power of ontology in Palantir Foundry – Cognizant – https://www.cognizant.com/us/en/the-power-of-ontology-in-palantir-foundry
28. Palantir: Home – 2024-03-21 – https://www.palantir.com
29. In the most critical manufacturing environments, operating with AI … – 2026-03-24 – https://x.com/PalantirTech/status/2036474710108651649
