The data platform wars were drifting toward maturation: slowing growth, converging architectures, open formats dissolving storage lock-in. Then AI consumption reversed the curve.
Databricks hit a $5.4 billion revenue run-rate at 65% year-over-year growth. Snowflake reaccelerated to 34%. BigQuery reported 30x growth in Gemini-processed data. The numbers are striking, but the question that matters is whether they signal a permanent demand-curve shift or a hype-cycle bump — a question at the centre of the broader data platform market restructure.
How does AI consumption increase data platform revenue?
AI workloads consume compute at orders of magnitude above SQL analytics, and consumption pricing turns every inference call into revenue. A single RAG query can consume 10 to 100 times the credits or DBUs of a dashboard refresh. Agentic workflows compound this: when an agent verifies its own output against a second model call, checks a policy, and retrieves fresh context, that single user prompt becomes five to fifteen billing events.
Databricks’ AI product line reached a $1.4 billion run-rate because every Mosaic AI call consumes DBUs at GPU-attached rates. Your existing SQL workloads growing at 30% now grow total spend at 65%, because AI workloads layer on top of existing data.
Snowflake reaccelerated to 34% product revenue growth as over 9,100 accounts began running Cortex AI. Cortex Code went GA in February 2026 and within the quarter, according to the CFO, became “the largest driver to the increase in our forecast.”
Net Revenue Retention reveals the mechanism. Snowflake’s NRR sits at 125 to 126%, dragged by base maturation. Databricks’ exceeds 140%, reflecting faster AI adoption. The NRR gap is about where each platform sits on the AI adoption S-curve, not platform quality.
How does Snowflake’s Cortex AI differ from Databricks’ Mosaic AI in architecture?
Cortex AI is a model-serving layer on proprietary storage. Data stays in Snowflake, inference runs in virtual warehouses, and the model catalogue is curated for SQL-accessible consumption. It is the simplest path for running AI without leaving Snowflake.
Mosaic AI is a training-and-serving layer integrated with Unity Catalog. Built on MLflow, it covers data prep, training, fine-tuning, deployment, and monitoring with native GPU support. Models sit in Unity Catalog alongside tables and serve through Unity AI Gateway across AWS, Azure, and GCP.
The cost model matters more than model selection. Cortex bills by the virtual warehouse while it runs. Mosaic splits the economics: you pay Databricks DBUs for the GPU compute plus your cloud provider for the underlying instances. Neither is inherently cheaper, but they suit different budgeting styles.
A retailer using Cortex AI to classify product images pays per-warehouse-second with no infrastructure to manage. The same retailer using Mosaic AI to fine-tune a recommendation model on GPU clusters pays DBUs plus cloud compute but can run that model across clouds.
Cortex is model-agnostic: bring the model, Snowflake serves it. Mosaic is model-optimised with an open serving layer. If your team writes SQL, Cortex fits. If notebooks are open all day, Databricks has the advantage.
These architectural differences produce different governance surfaces, and governance is where lock-in now lives — the catalog is becoming the new lock-in surface.
How do Unity AI Gateway, Snowflake Intelligence, and BigQuery Gemini compare as AI governance layers?
The AI governance layer is replacing storage format as the lock-in surface.
Unity AI Gateway governs agents, MCP servers, and frontier models across all three clouds with access controls inherited from Unity Catalog. MCP, adopted widely since Anthropic open-sourced it in 2024, defines how agents discover and access tools and data. Unity AI Gateway makes it a governance boundary where every agent action is mediated by catalogue-level policies and audit trails.
Snowflake Intelligence is model-agnostic but cloud-bound. Governance is only as portable as the Snowflake deployment. Horizon Catalog governs data, and Cortex Agents support MCP connectors for Atlassian, GitHub, and Salesforce, but cross-cloud AI governance portability is still under construction.
BigQuery Gemini collapses governance into SQL IAM. Elegant in its simplicity, but zero cross-platform portability since BigQuery exists only on GCP.
If your agents need consistent governance across clouds, Databricks’ MCP-based architecture is currently the most complete option. If your AI stays within a single Snowflake deployment or a single GCP project, the governance gap is narrower because you are not crossing the boundary where policy portability becomes the constraint.
If governance is the new lock-in surface — a shift traced in how open formats changed the lock-in equation — the question becomes whether the AI consumption growth that makes that lock-in costly is durable or temporary.
What signals indicate that AI-driven consumption growth is durable versus a temporary bump?
Three numbers separate structural demand from a hype-cycle bump: NRR trajectory, GPU-attached consumption growth rate, and agentic versus single-turn inference ratio.
Durable signals: NRR expanding as your existing customers add AI workloads, agentic consumption compounding per-account, GPU-attached DBU growth outrunning SQL DBU growth. Databricks’ 65% YoY growth sustained across multiple quarters is the benchmark. Temporary growth would have decelerated by now.
Temporary signals: one-off training spikes, migration-driven consumption, summit-hype trials that do not convert. Snowflake’s 9,100 AI accounts need to prove sustained Cortex consumption, not trial activity.
Databricks’ most recent private valuation of $134 billion, set during its 2025 funding round, hinges on durability. If AI consumption is structural and NRR stays above 140%, the growth rate justifies the premium. If AI spend proves an air pocket, Snowflake’s public-market discipline looks smarter. A FinOps counterweight exists too: optimisation practices are a permanent drag on consumption growth, and AI is the workload that overcomes it.
For your own budgeting: the consumption model means AI bills can surprise. Snowflake’s account-level and per-agent cost limits exist because customers demanded them. The thing that breaks the thesis is a consumption air pocket. If enterprise AI spending pauses, the consumption meter slows and NRR drifts toward 100%.
How does agentic AI change what an enterprise data platform needs to provide beyond traditional analytics?
Agentic workloads are structurally different from dashboard queries. One user request fans out into dozens of platform operations: vector search, retrieval, inference, validation, action. Database architectures built for human-scale interaction are misaligned with machine-scale workloads. When your agents execute tens of thousands of reads and writes per minute, the platform needs latency budgets that can reach into milliseconds.
The retrieval layer becomes the competitive frontier. RAG accuracy depends on vector search quality. Mosaic AI Vector Search, Cortex Search, and BigQuery’s vector index compete on latency and relevance because the agent is only as good as what it retrieves.
Agent governance is a new category requiring agent-specific identities, action boundaries, and audit trails. Unity AI Gateway treats agents as first-class catalogue identities. Snowflake is building toward this through agent identities and Trust Center. BigQuery collapses it into IAM.
Platforms are racing to build a System of Intelligence: a governed layer above storage that organises business logic, institutional knowledge, and reasoning context that both humans and agents can reason against. Snowflake’s Cortex Sense, its context runtime for this layer, lifts structured-data accuracy from roughly 24% with frontier agents alone to about 86% out of the box, by supplying the business semantics agents lack.
If your organisation is deploying agents in 2026, you are buying the governance and retrieval infrastructure those agents depend on, not just a data platform. The platform that does not provide agent-native governance may become a migration driver.
How do you decide between model-agnostic AI layers and platform-native AI stacks?
Whether your AI workload’s data gravity justifies the lock-in trade is the decision that matters, not which model you use.
Model-agnostic layers (Snowflake Intelligence, BigQuery Gemini) offer flexibility in model choice but bind your data, governance, and agent logic to the platform. You can use any model, but your data must stay on the platform and your governance and agent logic are platform-bound. This works when you are standardised on one platform and AI is additive to existing analytics. It is the lower-friction path.
Platform-native stacks (Databricks Mosaic AI plus Unity AI Gateway) trade model flexibility for cross-cloud portability. You optimise for Databricks’ toolchain but governance is catalogue-portable across clouds. This works when your AI workloads span clouds or you cannot predict compute location two years out.
The partner ecosystem is a variable worth weighing. Snowflake benefits from NVIDIA partnerships and OpenAI’s investment. Databricks benefits from Anthropic’s partnership and the open-source MLflow community. The ecosystem you bet on shapes your roadmap as much as the architecture does.
If your AI is inference on governed data inside Snowflake or GCP, model-agnosticism is lower friction. If it includes training, fine-tuning, and multi-cloud deployment, platform-native is lower risk. If you do not know yet, platform-native preserves more options.
The platform wars have relocated. Storage format is no longer the battleground; governance is. SQL performance is no longer the differentiator; agent infrastructure is. The growth that looked like a hype-cycle bump is the leading edge of a structural demand-curve shift — one front in the full competitive landscape reshaping enterprise data platforms.
The platform decision is no longer about which data warehouse performs best. It is about which AI operating system will govern your agents, retrieval, and model infrastructure across clouds. The wrong choice commits you to a governance surface harder to migrate than storage.
The consumption economics are structural: the GPU multiplier on AI queries and the compounding effect of agentic workflows together confirm a permanent demand-curve reset. The architectural divergence between Cortex AI as a serving layer and Mosaic AI as a training-and-governance pipeline determines which workloads each platform can win. Governance is the new lock-in surface: open table formats solved data portability, but agent governance policies and MCP server configurations are harder to migrate than data. Databricks’ MCP-based cross-cloud architecture gives it a structural lead that competitors cannot match without a fundamental architectural shift.
The decision framework follows from the escalation: if your AI stays within one platform and one cloud, model-agnosticism is the lower-friction path. If your AI spans clouds and includes training, fine-tuning, and agent orchestration, platform-native preserves optionality. If you do not know yet, the governance portability argument tilts toward platform-native. For a structured methodology that integrates these dimensions, see how enterprise architects should evaluate AI workloads across platforms.
Frequently Asked Questions
Do open table formats like Iceberg actually eliminate platform lock-in?
No. Open formats solved storage portability, but lock-in has relocated to the governance and AI layers. Your data in Iceberg can move between platforms, but your agent access policies, model endpoints, MCP server configurations, and continuous learning loops cannot. The Unity AI Gateway, Snowflake Intelligence, and BigQuery IAM policies are where the real switching cost now lives.
Which platform should a mid-market company without a dedicated AI team choose?
Snowflake Cortex AI offers the lowest friction path: SQL-native inference, no infrastructure to manage, and a curated model catalogue accessible through familiar query patterns. You pay only for the warehouse while it runs, and your existing analysts can trigger AI calls without learning new toolchains. Databricks rewards organisations with ML engineering capacity; without it, the depth advantage becomes complexity overhead.
Is BigQuery falling behind because it lacks a standalone AI governance layer?
Not necessarily. BigQuery’s approach collapses AI governance into SQL IAM, which means no separate policy surface to configure. For organisations running AI entirely within GCP, this simplicity is a genuine advantage, not a gap. The trade-off is zero cross-cloud portability, but if your AI workloads are GCP-native and staying that way, BigQuery’s governance model is the most operationally lightweight option available.
Can I use Cortex AI and Mosaic AI together, or do I have to pick one?
You can absolutely run both, and many large enterprises do: Cortex AI for governed inference on Snowflake-managed data and Mosaic AI for training, fine-tuning, and multi-cloud agent orchestration on Databricks. The cost is duplicated governance, because access policies and model registries do not synchronise across platforms. The practical question is whether the duplication cost is justified by each platform’s strengths for different workload types.
How do I budget for AI inference costs when agentic workloads are unpredictable?
Start with a per-query ceiling, not a per-warehouse budget. Agentic workloads fan out unpredictably, and a single user prompt can trigger dozens of metered operations. Databricks and Snowflake both support query-level spend controls and resource governors. Budget against projected NRR expansion rather than static consumption forecasts, and monitor the ratio of agentic to single-turn inference: when agentic share grows, costs compound faster than usage volume suggests.
Are Snowflake’s 9,100 AI accounts a reliable signal of durable demand?
They are directionally positive but not yet proven. The number captures accounts that have run at least one Cortex AI operation, not accounts running production AI workloads. The durability test is conversion: how many of those 9,100 move from trial to sustained consumption, and whether Cortex-attached credit growth outruns SQL credit growth in those accounts. Watch for Snowflake’s NRR trajectory over the next two quarters as the conversion signal.
What makes MCP such a big deal if it is an open standard anyone can implement?
The standard itself is open, but Databricks’ advantage is that Unity AI Gateway operationalises MCP as a live governance boundary with catalogue-inherited policies, column-level masking, and agent identity already in production. Anyone can adopt the MCP specification, but building the governance infrastructure around it takes years and requires a unified catalogue that spans clouds. Databricks has that infrastructure today; competitors would need to build it from scratch.
How do data residency laws complicate cross-cloud AI governance?
They create hard boundaries that cross-cloud governance must navigate. An AI agent governed in Unity AI Gateway can inherit policies that enforce data residency per region (inference stays in Sydney, training data never leaves Frankfurt), and those policies travel with the agent across clouds. Platform-bound governance layers like Snowflake Intelligence and BigQuery Gemini handle residency within a single cloud well but cannot extend enforcement into a second cloud without manual policy duplication.
What actually is a System of Intelligence, and does it matter if I am not deploying agents?
A System of Intelligence is the governed layer above storage and compute that organises business logic, institutional knowledge, and reasoning context for both humans and AI. It matters whether you deploy agents or not because it defines how your organisation’s knowledge becomes queryable. If you are only running SQL analytics today, the System of Intelligence is what will make your data accessible to AI when you do adopt it, and building it takes longer than adopting the AI tools themselves.
How fast are enterprises really moving from AI pilots to production on these platforms?
Faster than the SQL analytics migration curve, but with higher failure rates. Databricks reports that AI-attached customers expand spend within two quarters of initial deployment, and Snowflake’s 34 percent reacceleration suggests Cortex adoption is converting. The bottleneck is not model capability but governance readiness: organisations that have not defined agent access boundaries, audit requirements, and data classification policies stall at pilot stage regardless of which platform they use.
Does choosing a model-agnostic layer mean I can switch platforms easily later?
No. Model-agnostic means you can swap the model, not the platform. Your data, governance policies, agent logic, and query patterns remain locked to the platform you built them on. Model-agnosticism is flexibility within a walled garden: you can change the flowers, but you cannot move the garden. The platform migration cost is governed by data and policy portability, not by how many model endpoints your current platform exposes.
