The Missing Fourth Option
(Contributed by Tricia Martínez-Saab, Founder & CEO)
For the past year, I've asked every enterprise leader we work with the same question:
What are you actually trying to buy?
Not what's on the invoice. Not GPU-hours, tokens, or reserved capacity. What are you actually buying when you sign an AI infrastructure contract? What's the thing that, if it works, makes the investment transformational—and if it doesn't, turns into a board-level problem?
The answers have been remarkably consistent.
They point to something much bigger than AI infrastructure itself. They point to a pattern that has repeated throughout every major computing transition. Markets begin by selling components. Eventually, they evolve to selling outcomes. I believe we're watching that transition happen again.
Last week, Palantir CEO Alex Karp captured this shift perfectly during an interview on CNBC.
"I want to own the GPUs. I want to own my data. I want to own the model. I want to control the alpha."
He was talking about sovereign AI, but he could just as easily have been speaking for nearly every regulated enterprise we've spent the last year working with.
Because that isn't a request for more compute.
It's a request for control.
And that's a fundamentally different problem.
Enterprises aren't sitting out AI. They're sidelined.
The organizations we work with - banks, pharmaceutical companies, manufacturers, energy providers, defense contractors, and sovereign programs - aren't lacking ambition. Every one of them has an AI strategy. Every one has executive sponsorship. Every one has budget allocated to AI initiatives.
What they don't have is infrastructure that actually matches the way they need to operate.
There's an important distinction between sitting out the AI revolution and being sidelined by it.
Being sidelined means the strategy is real, the urgency is real, and the business case is real-but the infrastructure isn't.
These organizations have launched pilot after pilot, only to see a small fraction reach production. They've been told public cloud capacity will eventually become available, yet many are still waiting. They've evaluated neoclouds and discovered that renting bare-metal GPUs solves only the easiest part of the problem. They've considered building their own infrastructure, only to realize they've committed themselves to a multi-year construction and staffing project before writing a meaningful line of AI code.
These are the enterprises that power our economies, develop our medicines, secure our nations, and manufacture our products.
Today, many of them are effectively locked out of production AI - not because they lack conviction, but because none of the infrastructure options available today actually fit the shape of the problem they're trying to solve.
Every computing era reaches this moment
This isn't the first time enterprise computing has arrived at this crossroads.
During the mainframe era, enterprises weren't really buying hardware. They were buying confidence.
IBM became the trusted operating environment for mission-critical computing because enterprises weren't looking for the cheapest collection of components. They were looking for someone accountable for the outcome.
Hardware, software, services, support, upgrades, and operations were delivered as one operating model, backed by one partner responsible when everything had to work.
"No one ever got fired for buying IBM."
That phrase wasn't really about IBM. It was about reducing operational risk.
The same pattern emerged decades later with cloud computing.
AWS didn't become the dominant cloud platform simply because it owned the most servers. It won because enterprises stopped having to think about servers altogether. Infrastructure became an abstraction. Operational complexity disappeared alongside it.
Every major computing platform follows this same trajectory.
We begin by buying technology.
Eventually, we buy abstraction.
AI is reaching that moment now.
Three options - and one missing
Today, enterprises looking to deploy production AI face three choices.
They can use the public cloud, which remains the fastest way to get started but is increasingly constrained by capacity, multi-tenancy, and priorities that don't always align with enterprise requirements.
They can work with neocloud providers, who do an excellent job renting GPU capacity but typically leave customers responsible for operating secure, compliant, mission-critical AI environments themselves.
Or they can build on-premises infrastructure, gaining maximum control while accepting enormous capital expenditures, years of deployment work, and an ongoing operational burden.
All three options force compromises enterprises increasingly don't want to make.
The reason is simple.
Each of these models is focused on selling infrastructure.
The enterprise isn't trying to buy infrastructure.
It's trying to buy an outcome.
The true cost isn't on the invoice
Alex Karp made another observation during that interview that deserves far more attention.
"The true cost is what you make minus what you lose."
That's a far better definition of total cost of ownership than most procurement models account for.
Because the largest costs in AI rarely appear on an invoice.
The proprietary knowledge that leaves your organization.
The eighteen months spent waiting for infrastructure.
The engineering talent redirected toward operating infrastructure instead of creating competitive advantage.
The compliance programs built from scratch.
The opportunity cost of falling behind competitors while your AI strategy waits for infrastructure to catch up.
None of those costs appear in a pricing calculator.
They're real nonetheless.
Components versus environments
This is where I believe the market is headed.
One layer of the market will continue selling components: GPU-hours, tokens, and raw compute. It will become an enormous market, increasingly competitive, with price becoming the primary differentiator.
Another layer will sell something entirely different.
Operating environments.
Not simply infrastructure, but complete AI platforms designed around how enterprises actually run production workloads.
Compute. Control plane. Operations. Governance. Security. Compliance. Networking. Lifecycle management. Software-defined portability. Physical residency.
One operating layer. One accountable partner. One environment designed around the workload - not around the infrastructure provider.
That's an entirely different business.
Why we built Dapple
This is why we built Dapple.
Not to become another marketplace.
Not to broker GPU capacity.
Not to compete over who owns the largest fleet of hardware.
We built Dapple because we believe enterprises aren't buying infrastructure anymore.
They're buying the ability to successfully operate AI.
The Enterprise OS Cloud is our answer to that challenge.
A new category between the public cloud and the private data center.
Dedicated. Single-tenant. Software-defined. Operated end-to-end. Portable across infrastructure.
Designed around enterprise control instead of provider lock-in.
The software remains with the customer throughout the life of the deployment. The operating model evolves alongside the workload. Infrastructure becomes an implementation detail rather than the customer's responsibility.
That's fundamentally different from renting compute.
It's equally different from asking enterprises to become infrastructure companies themselves.
The missing fourth option
The market spends enormous amounts of time debating public cloud versus private cloud, hyperscalers versus neoclouds, cloud versus on-premises.
I believe that's the wrong debate.
The real distinction isn't between where infrastructure runs.
It's between buying infrastructure and buying an operating environment.
That's the missing fourth option.
Not another way to rent GPUs.
A way to run AI.
History suggests every major computing platform eventually arrives at this point. The technology changes, but enterprise requirements don't.
Organizations running mission-critical systems have always optimized for resilience, accountability, trust, and operational confidence - not for whichever component happened to be cheapest that quarter.
AI is no different.
The enterprises that matter aren't done buying.
They're simply done buying the wrong shape of the solution.
The future of enterprise AI won't be defined by who owns the most GPUs.
It will be defined by who removes the most complexity.
That's the market we're building for at Dapple.
And I believe it's where enterprise AI is headed next.
More posts
Why we built the Enterprise OS Cloud
Most companies raise to build a category. Dapple built it, validated it, then raised. The founding thesis behind the Enterprise OS Cloud.
Build vs. Buy vs. Operate
The traditional build vs. buy debate misses the real question: who operates the AI infrastructure once the decision is made.
Beyond Cost Per GPU: The Metric That Actually Matters
Engineering leaders should not have to choose between looking cost-efficient on a slide and actually delivering for the business. That choice is a symptom of measuring the wrong thing.