Startup Diligence
Diligence report Enterprise data infrastructure, analytics, AI platform, and lakehouse software Late-stage private pre-IPO data and AI platform company

Databricks

Databricks Public-Source Startup Diligence Report

The core thesis is that Databricks is expanding from a lakehouse pioneer into a broader data-and-agent operating layer, using open formats, multi-cloud distribution, and acquisition-led product expansion to widen its moat. The core counter-thesis is that this expansion now depends on ambiguous late-stage financing, hyperscaler coopetition, and legal/IP exposure that could constrain margins, strategic freedom, or valuation durability.

Company profile

Databricks Public-Source Startup Diligence Report

Databricks looks like one of the strongest late-stage private data-and-AI platforms visible from public sources: real product breadth, credible enterprise scale, strong open-source lineage, and a demonstrated ability to raise capital and ship new categories. The counterweight is that core financial quality, partnership economics, and several material IP risks remain unresolved without a data room.

Website
www.databricks.com
Sector
Enterprise data infrastructure, analytics, AI platform, and lakehouse software
Geography
United States headquartered with global enterprise operations across North America, EMEA, and APJ
Stage
Late-stage private pre-IPO data and AI platform company
Known aliases
Databricks Data Intelligence Platform, Databricks Lakehouse Platform, Azure Databricks, Mosaic AI, Lakeflow, Lakebase, Unity Catalog
Report version
1.0
Timezone
UTC

Executive summary

Strengths

  • The Data Intelligence Platform positioning is explicit and current on Databricks’ own platform pages.
  • Databricks clearly operates a multi-product stack spanning engineering, warehousing, AI, governance, and operational database workloads.
  • Open-source lineage through Spark, Delta Lake, MLflow, and Iceberg interoperability is strongly supported.
  • MosaicML, Arcion, Tabular, and Neon visibly extend Databricks into AI, ingestion, interoperability, and operational databases.

Risks

  • The Makkai copyright case could become a strategic legal and valuation issue if public damages theories prove directionally right.
  • Series J headline financing obscures the true amount of fresh operating capital and the economic shape of the cap table.
  • Microsoft and hyperscaler channel dependence is a moat and a major source of strategic vulnerability at the same time.
  • Revenue scale is visible, but audited quality, segment economics, and cash conversion remain opaque.
  • Databricks is integrating many acquisitions and partner-model surfaces at once, increasing execution and product-complexity risk.

Gaps

  • Audited financial statements, AR aging, debt schedules, and cap-table details were not publicly available.
  • Customer concentration, retention, and pipeline quality remain opaque despite strong public logo breadth.
  • Commercial terms with Microsoft, AWS, Anthropic, SAP, and other key partners were not public.
  • Full patent, trademark, and license schedules were not validated in-session.
  • Litigation reserve analysis, insurance coverage, and outside-counsel risk assessment were not reviewed.

Recommended next steps

  • Obtain audited FY2024 and FY2025 financial statements, current cap table, and the full Series J legal package.
  • Review Microsoft, AWS, Anthropic, SAP, and Neon / Tabular / Mosaic transaction documents for economics and control rights.
  • Run customer and partner references across at least one large Azure account, one AWS account, one regulated customer, and one AI-native customer.
  • Review outside-counsel memos, reserves, and insurance schedules for Makkai, Byteweavr, R2, and Databricks v. Weisfield.
  • Benchmark Databricks against Snowflake, Microsoft Fabric, BigQuery, AWS, and Palantir using the buyer’s own workloads and price assumptions.

Risk register

critical high likelihood

R-007: Makkai copyright litigation is potentially bet-the-company

The Makkai case links DBRX and Mosaic model development to allegedly pirated books, and public reporting says the court denied Databricks’ motion to dismiss while damages theories remain very large.

Diligence request: Request outside-counsel assessment, reserve analysis, insurance coverage, and Mosaic acquisition diligence on training-data provenance.

high high likelihood

R-003: Microsoft and hyperscaler channel dependence creates coopetition risk

Azure Databricks is a first-party Microsoft service while Microsoft Fabric is a competitor; Databricks also depends on AWS, GCP, and model providers for distribution and infrastructure.

Diligence request: Review all major cloud and model-partner contracts for revenue sharing, MFN terms, exclusivity, and termination or change-of-control rights.

high high likelihood

R-004: Competition and pricing pressure span the whole data-plus-AI stack

Snowflake, Microsoft Fabric, AWS, BigQuery, and Palantir all market overlapping data, AI, and governance capabilities, which can compress Databricks pricing or force bundling.

Diligence request: Request segment-level win-loss data, pricing concessions, and churn drivers versus named competitors.

high medium likelihood

R-001: Series J structure and cap-table economics remain opaque

The official Series J announcement uses unusual non-dilutive language while also funding employee liquidity and taxes, leaving open questions on primary cash, secondary flow, structured financing, and preference overhang.

Diligence request: Obtain the Series J term sheet, cap table, liquidation preferences, and primary-versus-secondary allocation.

high medium likelihood

R-002: Revenue quality and unit economics are not independently verified

Public revenue and margin signals are management disclosures without audited statements, backlog, deferred revenue, or AR aging detail.

Diligence request: Request audited historical financials, revenue-recognition policies, deferred revenue, ARR definitions, and gross-margin bridges.

high medium likelihood

R-005: Customer concentration and retention quality are hidden

Public materials show impressive logo breadth and $1M-plus customer counts but do not disclose top-account share, concentration, GRR, or NRR.

Diligence request: Request top-10 customer concentration, gross and net revenue retention, and renewal trends by cohort and geography.

high medium likelihood

R-008: Patent and trade-secret disputes add recurring IP friction

Patent suits by R2 Solutions and Byteweavr, plus the Databricks v. Weisfield matter, suggest a recurring IP-defense burden and former-employee dispute risk.

Diligence request: Request the IP litigation schedule, trade-secret inventory, and any settlement or indemnity obligations tied to active disputes.

medium high likelihood

R-006: Product-sprawl and model-dependency execution risk is rising

Databricks is integrating MosaicML, Arcion, Tabular, Neon, Anthropic models, Lakebase, and Agent Bricks at once, increasing roadmap complexity and dependency on external model and infrastructure ecosystems.

Diligence request: Request attach rates, integration milestones, sunset plans, and contingency architecture for major partner-model dependencies.

Chapter 01

01Financial Information

Databricks’ public financial story is unusually rich for a private company on financing and growth markers, but still thin on the documents that matter most for diligence. The public record supports a rapid scaling narrative and a striking capital-raising history, while leaving cap-table mechanics, balance-sheet quality, and earnings quality unresolved.

I.A Annual and quarterly financial information for the past three years

not publicly verifiable confidence: low

Public sources give Databricks unusually good scale markers for a private company — including ARR, revenue, margin, and customer-count disclosures — but not audited statements, backlog schedules, AR aging, or debt detail. The financial picture is therefore directionally informative yet still insufficient for true earnings-quality diligence.

Evidence gaps

  • No audited financial statements, AR aging, backlog, or debt schedule were found in public sources.

Hidden risks

  • Private-company revenue run-rate language can overstate the predictability or quality of actual GAAP revenue.
  • Public gross-margin claims may not capture partner costs, support load, or AI infrastructure spend.

Follow-up questions

  • How do GAAP revenue, deferred revenue, gross margin, and cash collection compare to the public run-rate narrative?
Public revenue, ARR, margin, and scale signals
periodpublic metricsourceverification statusdiligence caveat
2018Exceeded $100M ARRSeries E press releaseverifiedNo audited 2018 statements or revenue-recognition detail were public.
2021-02$425M+ ARR; 75%+ year-over-year growthForbes Series G coverageverifiedThird-party reporting still depends on management access; no audited financial package was available.
2021-08$600M+ ARR; 75% annual growthForbes Series H coverageverifiedNo public cohort, retention, or gross-margin bridge accompanies the ARR number.
2023-07Crossed $1.5B revenue run rate; 85% non-GAAP subscription gross margin; >300 $1M+ ARR customersSeries I press releasepartially_verifiedMetrics are management-stated and non-GAAP; no audited income statement or working-capital view is available.
FY2024 ended 2024-01-31Reached over $1.6B revenue with 50%+ growthNVIDIA June 2024 partnership press releasepartially_verifiedThe statement confirms scale but still does not supply audited statements, segment margin, or tax detail.
Q4 FY2025 guidanceExpected to cross $3B revenue run rate and become free-cash-flow positive for the first timeSeries J press releasepartially_verifiedThis is forward-looking guidance and not a confirmed actual result in the reviewed public set.

Public scale visibility is unusually good for a private company, but revenue quality remains a data-room issue.

I.B Financial Projections

partially verified confidence: medium

Databricks does not publicly disclose multi-year projections, but management does provide short-horizon guidance around run-rate revenue, growth, and free cash flow. Those signals support momentum, not forecast reliability.

Evidence gaps

  • No three-year financial model, capex schedule, or scenario analysis was publicly available.

Hidden risks

  • Positive free cash flow in one quarter does not prove durable free cash flow across the cycle.
  • Expansion budgets can mask weaker underlying unit economics if partner or GPU costs rise faster than revenue.

Follow-up questions

  • What are Databricks’ official revenue, gross-margin, and cash-flow projections for the next three fiscal years?

I.C Capital Structure

partially verified confidence: medium

The public record is strong enough to map Databricks’ board and investor mix, but not its actual equity capitalization, option pool, or liquidation preferences. Series J makes the structure more rather than less important.

Evidence gaps

  • No public cap table, option schedule, or share-class rights were verified.

Hidden risks

  • Late-stage private rounds can hide preference, ratchet, or information-rights structures that materially alter common-equity value.

Follow-up questions

  • What does the fully diluted cap table look like after Series J, including employee programs and any structured financing?
Capital structure and governance snapshot
stakeholderpublic positionpublic evidencediligence caveat
Founders and senior managementSeven founders remain publicly listed; Ali Ghodsi is CEOFounder and leadership pages identify founders and current operating roles.No public founder share counts, vesting, or dilution history were verified.
BoardFounder-led board with a16z and NEA investor representation plus independent directorsBoard page lists Ion Stoica, Ali Ghodsi, Matei Zaharia, Ben Horowitz, Pete Sonsini, Elena Donio, Jonathan Chadwick, and Scott Shenker.No public committee structure, observer rights, or reserved-matter schedule was verified.
Strategic investorsMicrosoft, NVIDIA, AWS-linked, and Alphabet-linked participation is publicSeries E, Series I, and Series G/H materials name Microsoft, NVIDIA, AWS, and CapitalG as investors or strategic backers.Investment size, side letters, information rights, and commercial tie-ins remain private.
Employees and former employeesSeries J explicitly funds liquidity and related taxesSeries J press release says the capital is expected to provide liquidity for current and former employees and pay related taxes.No public tender mechanics, strike prices, employee pool size, or preference stack was verified.
Debt and other instrumentsnot_publicly_verifiableReviewed public sources did not confirm any current debt schedule or off-balance-sheet liability inventory.Request debt instruments, venture debt, revolvers, guarantees, and any off-balance-sheet commitments.

The governance picture is public enough for an initial map, but the economic rights remain largely opaque.

I.D Other financial information

partially verified confidence: medium

Public financing history is unusually visible, and Databricks has clearly used capital to fund product expansion and employee liquidity. The public record is much weaker on taxes, accounting policy, debt, and the exact economics of later rounds and acquisitions.

Evidence gaps

  • Tax positions, debt covenants, and actual later-round pricing beyond Series J were not independently verified.

Hidden risks

  • A round that includes significant secondary liquidity may leave less fresh operating cash than its headline size suggests.
  • Undisclosed acquisition prices and integration costs can obscure true capital efficiency.

Follow-up questions

  • How much cash actually entered the company versus selling shareholders in Series J and subsequent liquidity events?
Public funding-round history
dateround or eventpublic amount or termvaluationlead or counterpartiesverification statusdiligence caveat
2019-02-05Series E$250M equity financing$2.75BAndreessen Horowitz; Coatue; Microsoft; NEAverifiedNeed full stock terms and any side letters tied to Microsoft commercial rights.
2021-02Series G$1B equity financing$28B post-moneyFranklin Templeton; AWS; CapitalG; Salesforce Ventures; MicrosoftverifiedHistorical round terms come from archived independent coverage rather than Databricks PRs retrieved in-session.
2021-08Series H$1.6B equity financing$38BMorgan Stanley; Baillie Gifford; ClearBridge; UC Investment OfficeverifiedNeed capitalization, preference, and employee-liquidity mechanics for the round.
2023-09-14Series IOver $500M; $73.50 per share$43BT. Rowe Price; NVIDIA; Ontario Teachers; Capital One VenturesverifiedNeed exact round size, class rights, and strategic-investor restrictions.
2024-12-17Series J$10B expected financing; $8.6B completed at announcement$62BThrive; a16z; DST Global; GIC; Insight; WCMpartially_verifiedNeed primary-versus-secondary split, any debt component, and the legal meaning of non-dilutive.
2025-2026Later private-market pricing referencesPaywalled or indirectly cited later-round references onlynot_publicly_verifiableUndisclosed or paywalled later syndicatesinconclusiveConfirm whether any post-Series J round has actually closed and at what price.

Later valuation references beyond Series J were not independently validated in-session and are intentionally presented as a diligence gap rather than a settled fact.

Selected disclosed acquisitions and capital uses
eventdatedisclosed valuestrategic rationalefinancing implicationverification status
MosaicML acquisition2023-06-26Approx. $1.3B inclusive of retention packagesBring generative AI model training and ownership onto the Databricks platformLargest disclosed acquisition in the reviewed set; likely accelerated later capital needs and now anchors current copyright risk.verified
Arcion acquisition2023-10-23Over $100M inclusive of incentivesAdd real-time replication and CDC into the Lakehouse PlatformSupports ingestion expansion and shows continued tuck-in M&A spending beyond flagship AI deals.verified
Tabular acquisition2024-06-04Price not disclosed in Databricks PRBring Delta Lake and Apache Iceberg interoperability closer togetherStrategically important format-unification move; actual cash outlay remains a diligence gap.partially_verified
Neon acquisition intent2025-05-14Price not disclosed in Databricks PRAdd serverless Postgres built for AI-agent workloadsExpands Databricks into operational databases and agent-native application infrastructure.partially_verified
Series J stated capital uses2024-12-17New AI products, acquisitions, international GTM expansion, and employee liquiditySupport accelerated AI demand and company scalingSignals that not all headline financing converts into balance-sheet cash available for operations.verified

This is a selected disclosed set rather than a complete acquisition register; private side letters, earnouts, and integration budgets remain unreviewed.

Funding and strategic-capital timeline Timeline of the major public financing and strategic-capital events that shaped Databricks from growth-stage analytics company to late-stage AI platform.
Public valuation trajectory Public valuation anchors from Databricks’ major financing events, with a deliberate unknown point for later pricing references that were not independently verified in-session.

A sparse valuation chart is still useful because it frames what later pricing remains unverified.

Chapter 02

02Products

Databricks clearly operates a real multi-product platform rather than a single analytic tool. The challenge for diligence is less about whether the products exist and more about which of them produce durable economics and defensible differentiation.

II.A Description of each product

verified confidence: high

Databricks now publicly presents a broad stack that spans engineering, warehousing, AI agents, governance, and operational databases on top of an open lakehouse foundation. Product existence and current scope are well supported; product economics, attach rates, and relative maturity are not.

Evidence gaps

  • Product-level ARR, gross margin, and retention are not public.

Hidden risks

  • Platform breadth can hide uneven product maturity or low attach rates in newly launched categories.
  • A strong open-format story does not eliminate dependence on partner models and cloud economics.

Follow-up questions

  • Which newer products meaningfully contribute to revenue today, and which remain strategic options rather than durable businesses?
Product and SKU matrix
productaudiencekey featurespublic evidenceverification status
LakeflowData engineering and platform teamsJobs orchestration, declarative pipelines, ingestion connectorsPricing and product pages show Lakeflow Jobs and related engineering SKUs.verified
Databricks SQLAnalytics engineers, BI users, and warehouse buyersClassic, Pro, and Serverless SQL warehousesPricing pages and product descriptions confirm SQL analytics as a major warehouse SKU.verified
Mosaic AI / Agent BricksML, GenAI, and application teamsAgent development, model serving, training, evaluation, vector search, governanceAI page shows Agent Bricks, model serving, training, evaluation, and customer metrics.verified
LakebaseApplication developers and AI-agent buildersServerless Postgres with autoscaling, branching, and Unity Catalog integrationLakebase product and pricing pages describe operational database positioning for AI apps.verified
Unity Catalog and open formatsSecurity, governance, and platform teamsUniversal governance, lineage, and interoperable open lakehouse formatsOpen-source and platform pages position Unity Catalog, Delta Lake, and Apache Iceberg as part of the platform foundation.verified

Public product breadth is clear; what remains unresolved is product-level monetization and usage mix.

Public pricing comparison across major Databricks workloads
workloaddatabricks public pricepublic competitor anchorcomparability note
Batch and pipeline engineering$0.15 / DBU classic; $0.35 / DBU serverless for Lakeflow JobsAWS markets a purpose-built analytics suite rather than a single unified engineering SKUDatabricks publishes per-DBU list prices; AWS packages multiple services with separate billing.
SQL warehousing$0.22 / DBU classic; $0.55 / DBU pro; $0.70 / DBU serverlessSnowflake describes a serverless managed platform with governance and consumption billingSnowflake public pricing and warehouse sizing were not normalized in-session, so this is a positioning comparison not a TCO model.
AI model serving and agents$0.50 /M input tokens, $1.50 /M output tokens, plus hourly serving rates on reviewed public pricing pagesBigQuery and Microsoft Fabric position AI and agent workflows as integrated into the core analytics platformCross-vendor AI pricing is highly workload-specific and public list prices were not normalized across token, compute, and platform charges.
Operational database$0.092 / capacity unit hour and $0.345 / GB-month for LakebasePalantir Foundry markets an AI-powered operating system rather than a Postgres-native operational databaseLakebase is directly database-oriented; Palantir is a broader operational platform, so overlap is strategic rather than apples-to-apples pricing.
SAP Business Data Cloud shared processingNormal 1.25x DBU consumption uplift; temporary 1.0x promo through 2026-08-31not_publicly_verifiableThe reviewed public evidence confirms SAP-specific Databricks pricing terms, but no directly comparable partner pricing from peers was validated in-session.

All Databricks rates are public list pricing and likely differ materially from committed-use contract economics.

Databricks platform architecture map High-level architecture showing how Databricks layers engineering, warehousing, AI, operations, and governance on top of an open lakehouse foundation.
Chapter 03

03Customer Information

Databricks has strong public customer and partner breadth, but not the concentration and monetization detail that most investors or acquirers would want before underwriting a late-stage platform company. The customer story is credible; the revenue-quality story is still private.

III.A Top customers by application

partially verified confidence: medium

Public customer evidence is strong on breadth and named case studies across industries, but still weak on monetization quality and repeatability. The most credible public examples come from named customers with attributed executives and specific metrics.

Evidence gaps

  • No public customer-by-customer revenue or renewal history was found.

Hidden risks

  • Big logos can conceal low ACV, pilot-stage deployments, or aggressive discounting.

Follow-up questions

  • Which public logo references are large, multi-year, standardized deployments rather than departmental or pilot use cases?
Publicly known customers and case studies
customerindustryuse casepublic outcomeverification status
AT&TTelecommunicationsFraud detection and operational decision supportUp to 80% fraud reduction with 100+ ML models in productionpartially_verified
Virgin AustraliaTravel and aviationReal-time analytics, ML deployment, baggage operations75% increase in near real-time data availability and 44% reduction in mishandled bagspartially_verified
BlockFinancial technologyAI-agent productivity system for seller operations$10M in productivity gains claimed on Databricks AI pagepartially_verified
ComcastMedia and communicationsPersonalized viewer experience and voice commands96% response accuracy and 10x cost reduction claimed on Databricks AI pagepartially_verified
UK and ANZ regional logosCross-industryRegional proof of adoption in regulated and enterprise sectorsPublic releases name Unilever, Rolls Royce, Nationwide, Virgin Atlantic, Airwallex, Atlassian, NAB, Telstra, and Queensland Healthpartially_verified

These cases prove buyer diversity and use-case breadth, but not concentration or renewals.

III.B Strategic relationships

partially verified confidence: medium

Strategic relationships are central to Databricks’ distribution and product strategy. Microsoft, Anthropic, SAP, and the broader partner network are real strengths, but they also concentrate channel and model dependence.

Evidence gaps

  • Public sources do not reveal revenue-share terms, minimum commitments, or partner dependency by ARR.

Hidden risks

  • The most powerful partners are also potential chokepoints for economics, prioritization, or strategic conflict.

Follow-up questions

  • How much of Databricks revenue and pipeline is sourced directly or indirectly through Microsoft, hyperscalers, and key model partners?
Strategic relationships and partnerships
partnerrelationship typepublic evidencerevenue or distribution signalgap
Microsoft / Azure DatabricksFirst-party cloud distribution and strategic investmentAzure Databricks is a first-party Azure service and Microsoft joined Series E.Microsoft-controlled billing makes Azure a major channel rather than just infrastructure.Exact revenue sharing, pricing control, and Fabric-related conflict terms were not public.
AnthropicFive-year model partnershipClaude is offered natively on the Databricks platform across AWS, Azure, and GCP.Adds frontier model breadth and potentially deepens AI-agent adoption.Public economics and any minimum commitments are not disclosed.
SAP Business Data CloudData-sharing and processing integrationDatabricks publishes explicit SAP-related DBU pricing and promotional uplift terms.Suggests SAP-originated data and AI workflows could become a distribution vector.Revenue sharing and exclusivity terms were not public.
Global partner ecosystemCloud, ISV, and consulting ecosystemDatabricks says it has 1,200+ global cloud, ISV, and consulting partners.Large partner ecosystem can multiply implementation and co-sell reach.Public materials do not disclose partner-sourced revenue or the top partner mix.
BrickBuilder / partner-led deliveryPartner program and go-to-market enablementDatabricks public materials describe partner programs and ecosystem routes alongside direct sales.Supports enterprise implementations and global reach beyond direct field sales.Public partner tiers and economics remain limited.

The public record shows a real partner moat, but commercial dependencies may be more important than the headline ecosystem size suggests.

Public customer and partner disclosure ladder Bar chart of the best public customer and partner scale markers, with null bars for the most important concentration metrics that Databricks does not publicly disclose.

The purpose of this chart is to expose the disclosure gap, not to imply a precise concentration model.

III.C Revenue by customer

not publicly verifiable confidence: low

Public sources support broad customer adoption but do not support a reliable concentration analysis. This section is therefore an evidence gap rather than a clean concentration bill of health.

Evidence gaps

  • No public top-customer, cohort-retention, or revenue-by-vertical tables were found.

Hidden risks

  • A small number of hyperscaler-aligned or mega-enterprise accounts could dominate revenue without public visibility.

Follow-up questions

  • What percentage of ARR comes from the top 10, top 20, and top 50 customers?

III.D Significant relationships severed within the last two years

not publicly verifiable confidence: low

No material severed customer, partner, or supplier relationships were directly verified in the reviewed public set. That absence should be treated as a gap, not as proof of clean relationship history.

Evidence gaps

  • No public severance log, customer-loss summary, or partner termination schedule was found.

Hidden risks

  • Important channel conflicts or large customer losses often surface later than product launch or funding news.

Follow-up questions

  • Which material customer, cloud, model, or partner relationships have been terminated or sharply downsized in the last two years?

III.E Top suppliers

partially verified confidence: medium

Databricks’ supplier picture is best understood as multi-cloud and model-platform co-dependency rather than single-supplier concentration. Microsoft, AWS, GCP, NVIDIA, and partner models all matter in different ways.

Evidence gaps

  • No public spend, take-or-pay, or margin-sharing schedules were found for core suppliers and partners.

Hidden risks

  • Platform-level dependencies can alter Databricks economics even if no single cloud accounts for all revenue.

Follow-up questions

  • What share of Databricks workload and revenue runs on Azure, AWS, and GCP, and how are those economics structured?
Cloud, model, and infrastructure dependency map
supplierrolepublic evidencedependency riskverification status
Microsoft AzureCloud platform plus first-party Azure Databricks channelAzure Databricks is a first-party service and Microsoft joined Series E.Microsoft controls billing and also competes via Fabric.verified
AWSCloud infrastructure, marketplace route, and analytics/AI competitorAWS invested in Series G and markets a broad analytics plus SageMaker stack.Databricks competes with AWS services while also relying on AWS infrastructure and marketplace reach.verified
Google CloudCloud infrastructure and adjacent data-plus-AI competitorCapitalG invested in Series G and BigQuery markets an autonomous data-to-AI platform with Iceberg support.Open-format interoperability may lower switching friction while keeping Google competitive.verified
NVIDIAGPU, model-serving, and accelerated compute partnerDatabricks publicizes DGX Cloud training, Photon CUDA acceleration, and NVIDIA strategic investment.Supplier pricing power can influence Databricks AI margins.verified
Anthropic and other model providersThird-party model access through Databricks AI workflowsDatabricks markets Anthropic Claude and partner-model availability on its platform.Partner-model concentration can weaken Databricks control over roadmap and pricing.partially_verified

The most material public dependency is not a single supplier but the channel and infrastructure leverage of hyperscalers and model partners.

Chapter 04

04Competition

Databricks no longer competes only with warehouse vendors; it competes across data engineering, governance, AI platforms, agent frameworks, and operational AI systems. That enlarges the opportunity set and intensifies pricing and bundling pressure.

IV.A Competitive landscape by market segment

partially verified confidence: medium

Databricks competes across several overlapping markets at once: warehouse, lakehouse, AI platform, governance, and operational data apps. Public product pages make the overlap obvious even without neutral market-share data.

Evidence gaps

  • No public neutral win-loss, share, or pricing-quality analysis was found.

Hidden risks

  • Broad platform overlap can turn into price pressure and bundling risk long before it shows up in logo churn.

Follow-up questions

  • Where does Databricks consistently win or lose against Snowflake and Fabric by workload, segment, and deal size?
Competitor comparison matrix
competitorsegmentproduct overlapdifferentiatorsource
SnowflakeAI Data Cloud and cloud data platformWarehouse, governance, AI, app development, and multi-cloud data platformServerless managed platform with governance, FinOps, and observabilitySnowflake platform page
Microsoft FabricEnd-to-end analytics SaaS over OneLakeData engineering, data science, warehouse, real-time analytics, databases, and governanceTight Microsoft 365 and OneLake integration plus SaaS packagingMicrosoft Fabric overview
AWS analytics and SageMakerPurpose-built services plus integrated analytics and AI experienceETL, SQL analytics, governance, ML, and lakehouse-style data accessBreadth of native AWS services and deep cloud distributionAnalytics on AWS
Google BigQueryAutonomous data-to-AI platformWarehouse, AI, agents, vector search, and Iceberg interoperabilityAgentic analytics experience with Google-native data and AI integrationsBigQuery page
Palantir FoundryEnterprise operating system and ontology platformOperational decisioning, data governance, and AI-driven applicationsOntology-driven operational workflows rather than warehouse-first analyticsPalantir Foundry page

This matrix intentionally focuses on publicly visible product overlap rather than an unverified market-share ranking.

Basis-of-competition scoring
axisdatabricks positioncompetitor pressurepublic evidence
Open formats and interoperabilityStrong via Spark, Delta Lake, MLflow, Iceberg, and Unity CatalogGoogle BigQuery and AWS now also emphasize Iceberg and open lakehouse interoperabilityDatabricks open-source and Tabular pages versus AWS and BigQuery positioning
Unified end-to-end platform breadthStrong with data engineering, SQL, AI, governance, apps, and operational DBMicrosoft Fabric is closest on explicit end-to-end SaaS scopeDatabricks platform pages and Microsoft Fabric overview
Channel reachStrong but partner-dependent via Azure, AWS, GCP, and 1,200+ partnersMicrosoft and AWS control major native cloud channelsAbout page, Series E, and TechCrunch Azure article
AI and agent depthStrong public product momentum through Mosaic AI, Anthropic, Lakebase, and Agent BricksSnowflake, Fabric, BigQuery, and Palantir all market integrated AI and agent workflowsDatabricks AI page, Anthropic PR, and competitor pages
Pricing transparencyModerate because list prices exist, but enterprise economics are opaqueAll major peers still require workload-specific normalization for true comparisonDatabricks pricing pages and competitor positioning pages

Scoring is qualitative and should be validated with win-loss and pricing data from actual deals.

Data-plus-AI competitive market map Illustrative market map placing Databricks and major rivals on platform breadth and AI-agent depth based on public product positioning.

Entity placement is an analyst judgement grounded in public product scope rather than a formal market-share ranking.

Chapter 05

05Marketing, Sales, and Distribution

Databricks’ public GTM posture is coherent: one-platform messaging, cloud and partner leverage, and visible regional investment. What the public record cannot answer is how efficient those routes are or how much pricing pressure sits underneath the strong growth narrative.

V.A Strategy and implementation

partially verified confidence: medium

Databricks’ public GTM strategy centers on one-platform positioning, open and private data control, partner leverage, and geographic expansion. The story is coherent, but its efficiency is not publicly measurable.

Evidence gaps

  • No public CAC, payback, or budget-efficiency data was found.

Hidden risks

  • Partner-led growth can mask weak direct-sales productivity or dependence on a small number of cloud channels.

Follow-up questions

  • How much of new ARR comes from direct field sales versus cloud or partner-led channels?
Distribution channels and go-to-market motions
channelregion or buyerpublic evidencegap
Direct enterprise sales and committed-use contractsLarge enterprise accountsPricing pages invite customers to contact Databricks for committed-use discounts and custom requirements.No public quota, win rate, or sales-cycle metrics were found.
Azure first-party routeAzure customers and public-sector workloadsAzure Databricks is a first-party Azure service with Microsoft billing and support.No public revenue-share schedule or Azure-versus-direct mix was found.
Cloud marketplace and hyperscaler alignmentAWS, Azure, and GCP-aligned buyersDatabricks markets itself as multi-cloud and highlights cloud-provider compatibility.Marketplace share and CAC are not public.
Partner ecosystem and consulting deliveryLarge enterprise transformation programsDatabricks says it has 1,200+ cloud, ISV, and consulting partners.No public split of partner-sourced revenue, top SIs, or partner dependency.
Self-serve learning, free trial, and platform adoption routesDevelopers, learners, and future enterprise usersPricing and careers materials reference free trial, free edition, and training pathways.No public conversion rates from self-serve users to paying enterprise accounts were found.

The GTM picture is visible at a surface level, but the economics and productivity of each route remain private.

V.B Major Customers

partially verified confidence: medium

Major-customer evidence is persuasive on brand quality and cross-industry relevance, but the public record does not support a reliable view of account health, expansion, or pipeline conversion.

Evidence gaps

  • Pipeline analysis and account health indicators were not public.

Hidden risks

  • A high-profile customer base can still coexist with weak net retention or low platform standardization.

Follow-up questions

  • Which public reference accounts are largest by ARR, and how have they expanded over time?

V.C Principal avenues for generating new business

partially verified confidence: medium

The principal public new-business routes are enterprise sales, Azure/AWS/GCP procurement, partner delivery, training funnels, and increasingly AI-agent and database expansion attached to existing data estates.

Evidence gaps

  • No public conversion funnels or route-by-route bookings data was found.

Hidden risks

  • New-business growth can become increasingly dependent on partner-model hype cycles rather than repeatable platform economics.

Follow-up questions

  • What percentage of new ARR comes from greenfield AI products versus expansion on existing data-platform accounts?
Public GTM funnel from entry to scaled enterprise deployment Qualitative funnel showing how public Databricks materials move a buyer from self-serve awareness to committed enterprise adoption.

This is a narrative funnel rather than a fully comparable cohort funnel because public conversion data is unavailable.

V.D Sales force productivity model

not publicly verifiable confidence: low

Databricks clearly operates a serious enterprise-sales motion, but public materials do not disclose quota, compensation, average cycle length, or new-hire productivity.

Evidence gaps

  • No public sales compensation, quota, or cycle data was found.

Hidden risks

  • Late-stage software companies can preserve headline growth while hiding weakening sales efficiency through discounting or channel subsidies.

Follow-up questions

  • What are Databricks’ sales ramp, quota attainment, and average selling-cycle assumptions by segment?

V.E Ability to implement marketing plan with current and projected budgets

partially verified confidence: medium

Public regional investment commitments strongly suggest Databricks can fund continued marketing and GTM expansion. What remains unclear is whether those budgets are economically efficient and conversion-positive.

Evidence gaps

  • No public CAC, pipeline efficiency, or budget-vs-output analysis was found.

Hidden risks

  • Regional expansion spending can become a vanity metric if partner economics or customer conversion lag.

Follow-up questions

  • How do UK and ANZ investment commitments translate into pipeline, bookings, and regional margin targets?
Public marketing, training, and expansion signals
signaldescriptionpublic evidenceverification status
UK expansionMore than $850M to expand UK presence over three yearsNew 137,000-square-foot EMEA hub, 500+ employees today, and training target of 100,000 people by 2028.partially_verified
ANZ expansion$300M commitment over three yearsNew Sydney headquarters, 85% year-over-year Q1 growth claim, and 100,000 learners target over five years.partially_verified
Large-event brand presenceData + AI Summit and training ecosystem support broad market reachDatabricks public materials repeatedly route users to trials, events, training, and academy resources.verified
Regional GTM prioritiesLakebase, Genie, and Agent Bricks are featured as regional growth productsUK and ANZ releases explicitly call out these products as part of the expansion program.verified

Budget visibility is strongest for regional commitments rather than marketing efficiency or CAC.

Public international expansion commitments Simple bar chart of the two largest region-specific investment commitments Databricks publicly announced in 2026.
Chapter 06

06Research and Development

Databricks still presents itself as a founder-led technical company with substantial research depth, but the current pipeline also reflects a more aggressive commercial expansion into agents, databases, and interoperability. Public sources support the direction of travel, not the eventual economic quality of that pipeline.

VI.A Description of R&D organization

verified confidence: high

Databricks still presents itself as a founder-led technical organization with real research depth, specialized engineering teams, and explicit academic ties. Public materials support technical credibility more strongly than R&D resource allocation.

Evidence gaps

  • No public R&D budget, headcount by function, or research-portfolio ROI was found.

Hidden risks

  • A founder-centric R&D narrative can hide succession or span-of-control issues below the named leaders.

Follow-up questions

  • How is R&D spend allocated across core platform, AI agents, database, open formats, and research science?
Key R&D personnel and technical leadership
nameroletechnical scopesource
Matei ZahariaCo-founder and CTOSpark lineage, MLflow, research leadership, platform strategyFounders and research pages
Ion StoicaCo-founder and Executive ChairDistributed-systems lineage and board-level technical influenceFounders and board pages
Reynold XinCo-founder and Chief ArchitectCore platform architecture and Spark lineageFounders page
Patrick WendellCo-founder and VP of EngineeringPlatform engineering leadershipFounders page
Vinod MarurSVP of EngineeringPublic engineering leadership within current executive teamLeadership team page
Research organization48-publication public research footprintDistributed systems, AI/ML, applications, and specialized engineering teamsResearch page

Public leadership depth is visible, but exact team size and span of control remain private.

R&D and technical leadership org chart Simplified public R&D org chart centered on founders, research, and engineering leadership.

The public org chart is partial by design and should be supplemented by an internal span-of-control map.

VI.B New Product Pipeline

partially verified confidence: medium

Databricks’ public product pipeline is active and acquisition-fed: AI agents, operational databases, interoperability, and partner-model integrations are all moving at once. The missing question is how much of this pipeline becomes high-quality recurring revenue.

Evidence gaps

  • No public product-line P&L or kill-rate data was found; the optional patent/publication trend chart was skipped because no reliable time series beyond a publication snapshot was visible in-session.

Hidden risks

  • Fast-moving AI pipeline expansion can mask low attach rates or higher-than-expected GPU and support costs.

Follow-up questions

  • Which pipeline products are already material to bookings or ARR, and which remain strategic bets?
Public product and research pipeline
projectstatusexpected date or signalsourceverification
Agent Bricks and Mosaic AI agentsPublicly marketed and regionally highlightedFeatured on current AI page and in ANZ releaseAI page and ANZ expansion releaseverified
LakebaseLaunched and priced publiclyPromoted in UK and ANZ expansion materialsLakebase product and pricing pages; UK and ANZ releasesverified
Anthropic Claude integrationFive-year partnership live on AWS, Azure, and GCPClaude 3.7 Sonnet available via DatabricksAnthropic partnership press releaseverified
Delta/Iceberg interoperabilityStrategic integration roadmap after Tabular acquisitionPublic interoperability ambition over multiple yearsTabular acquisition press releasepartially_verified
Neon integration for AI-native operational workloadsAnnounced acquisition intentTransaction still subject to customary closing conditions and regulatory clearancesNeon acquisition press releasepartially_verified

The public roadmap is rich on product launches and partner integrations but thin on product-level economics or kill rates.

Chapter 07

07Management and Personnel

Databricks’ public management picture is strong enough to confirm a mature late-stage leadership bench, but still weak on compensation, equity, and attrition. The company looks operationally serious; what remains unclear is how resilient that seriousness is beneath the visible top layer.

VII.A Organization Chart

verified confidence: high

The public org chart is strongest at the board and top-management level. Founders, investor-linked directors, and late-stage executive hires are all visible, but sub-C-suite operating structure is not.

Evidence gaps

  • No full internal org chart or committee map was public.

Hidden risks

  • A clear public top-level org chart does not prove durable management depth below named executives.

Follow-up questions

  • What does the operating org look like below the named executives, and which functions still rely heavily on founders?
Governance and management org chart Simplified public org chart from the board through the named operating leadership team.

VII.B Historical and projected headcount by function and location

partially verified confidence: medium

Databricks is clearly large enough to be operating like a global public-company candidate in headcount terms, but the public record still provides only a few anchor points rather than a full workforce model.

Evidence gaps

  • No public function-by-function historical headcount or forecast was found.

Hidden risks

  • Large global headcount can hide localized over-hiring, uneven manager quality, or attrition pockets.

Follow-up questions

  • How does headcount break down by function, geography, and planned 12-month growth?
Headcount and hiring signals
signaldetailsourcediligence note
Current workforce size10,000+ employees worldwide across 30+ offices in 20+ countriesCareers pageStrong current scale anchor, but no function-by-function breakdown is public.
2021 hiring planPlan to exceed 3,000 employees by end of 2021Forbes Series H coverageUseful historical anchor, but it is a plan rather than a confirmed year-end actual.
UK / Ireland team500+ employees today with expectation to surpass 1,000 over the next few yearsUK investment releaseShows meaningful regional GTM and engineering build-out.
Research hiringResearch page explicitly recruits PhDs across research and specialized engineering teamsResearch pageSignals continued investment in technical depth rather than only GTM scaling.
ANZ footprint expansionNew 22,000-square-foot Sydney HQ and continuing team growth in ANZANZ investment releaseSupports regional capacity growth but not net global hiring economics.

Public headcount data is sparse, so workforce quality and attrition still require direct diligence.

Public headcount anchor chart Minimal workforce-size chart using the strongest public employee-count anchors visible in-session.

This sparse chart is intentional: it makes the headcount disclosure gap visible instead of hiding it.

VII.C Senior management biographies

verified confidence: high

Publicly named leaders cover finance, legal, field, people, security, information, and engineering — enough to confirm a mature C-suite. Public biographies remain partial and still need diligence support.

Evidence gaps

  • No complete biography pack or tenure history for all senior leaders was public.

Hidden risks

  • Named leaders do not by themselves prove repeatable bench depth or succession readiness.

Follow-up questions

  • Which executives own international operations, product P&L, and AI compliance sign-off?
Senior management roster
namerolepublic signalsource
Ali GhodsiCo-founder and Chief Executive OfficerCore operating leader and public face of financing, platform, and AI strategyLeadership and founders pages
Andy KofoidPresident, Global Field OperationsField-operations scale-up and public-market readiness signalLeadership page and Forbes Series H coverage
David ConteChief Financial OfficerLate-stage private-company finance leadershipLeadership page
Trâm PhiSVP and General CounselElevated legal function while IP and model litigation risks riseLeadership page
Ion Stoica and Matei ZahariaExecutive Chair and CTO; founders on the boardFounders remain inside both technical and governance structuresFounders and board pages

The public roster is credible but still not a substitute for a full internal org chart and biography pack.

VII.D Compensation arrangements

partially verified confidence: low

Public materials show that Databricks promotes benefits and flexible work, but not executive compensation or broad compensation design. This section is therefore mostly a diligence gap.

Evidence gaps

  • No public executive comp summaries, salary bands, or bonus structures were found.

Hidden risks

  • Late-stage private companies can mask retention pressure through opaque equity and tender programs.

Follow-up questions

  • How are executive and key technical employees paid across cash, bonus, equity, and liquidity programs?

VII.E Incentive stock plans

not publicly verifiable confidence: low

No meaningful public stock-plan detail was verified. Given the late-stage financing profile and explicit employee-liquidity references, this is a core private-data-room issue.

Evidence gaps

  • No option-pool, strike-price, vesting, or tender-history schedule was public.

Hidden risks

  • Opaque stock-plan refresh and tender mechanics can distort incentives and common-equity expectations.

Follow-up questions

  • What are the current option pool, refresh policy, and employee tender history by level and cohort?

VII.F Significant employee relations problems, past or present

inconclusive confidence: low

No significant employee-relations problems were directly verified in the reviewed public set. That should be read as inconclusive, not as evidence that no issues exist.

Evidence gaps

  • No public employee-relations log, WARN history, or whistleblower summary was found.

Hidden risks

  • High-growth companies often show employee-relations strain before it reaches public litigation or press.

Follow-up questions

  • Have there been material HR investigations, settlements, or labor disputes in the last two years?

VII.G Personnel Turnover

inconclusive confidence: low

Public turnover evidence is thin, but founder-role distinctions and former-employee litigation suggest that people-related diligence should go deeper than the positive culture narrative.

Evidence gaps

  • No two-year attrition, regretted attrition, or founder employment-agreement data was public.

Hidden risks

  • Formal executive hires and growth messaging can coexist with meaningful attrition below the named leadership layer.

Follow-up questions

  • Which founders and key leaders remain operational, and what has voluntary attrition looked like by function?
Departures, role changes, and turnover signals
signaldate or periodpublic evidenceimplicationverification status
Ion Stoica moved from founding CEO to Executive Chair years ago2015 onward, public history summarized in ForbesForbes recounts the governance transition and Ali Ghodsi’s rise to CEO.Shows the company has already navigated one founder-governance reset.verified
Andy Konwinski remains a founder but is not on the current executive-team pageCurrent as of 2026-05-14Founders page lists Konwinski, while leadership page does not.Suggests a founder-role transition or reduced operational involvement that warrants direct clarification.partially_verified
Andy Kofoid joined to run global field operations2021Forbes Series H coverage frames Kofoid as a late-stage field-scale hire.Supports the view that Databricks has been professionalizing GTM for public-market readiness.verified
Former employee James Weisfield is now a litigation counterparty2024 onwardDatabricks sued Weisfield and related entities in 2024.Raises former-employee IP and retention-governance questions.verified
Comprehensive attrition metricsPast two yearsnot_publicly_verifiableNo public voluntary, regretted, or function-level turnover data was found.not_publicly_verifiable

This table should be read as a sparse public signal set, not a true turnover ledger.

Chapter 08

08Legal and Related Matters

Databricks’ legal and regulatory diligence picture is materially more active than a casual reading of its trust center would imply. The combination of AI copyright exposure, recurring patent disputes, and private contract economics makes legal diligence a central workstream, not a check-the-box exercise.

VIII.A Pending lawsuits against the Company

partially verified confidence: medium

Databricks has material public litigation exposure, led by the Makkai copyright case and supported by a broader set of patent disputes. This is not peripheral diligence — it is a central risk area.

Evidence gaps

  • No reserve analysis, direct PACER exhibit review, or outside-counsel assessment was available.

Hidden risks

  • Public docket activity may understate reserve needs, settlement pressure, or discovery risk.

Follow-up questions

  • What is management’s downside-case reserve view for Makkai and the active patent docket?
Pending lawsuits against the company
casecourtfiled datematterstatussource
Makkai v. Databricks, Inc., et al.N.D. California, 3:24-cv-026532024-05-02Copyright and model-training-data dispute tied to Mosaic/DBRXComplaint filed; public reporting says motion to dismiss was denied in 2026CourtListener and The Register
Byteweavr, LLC v. Databricks, Inc.E.D. Texas, 2:24-cv-001622024-03-08Patent infringementPublic docket remains active with later filings visible through 2025-06CourtListener
R2 Solutions LLC v. Databricks, Inc.E.D. Texas, 4:23-cv-011472023-12-28Patent infringementPublic docket shows the case remained active through 2026-05CourtListener

This table reflects only the matters directly verified in-session; it is not a complete litigation schedule.

Legal and IP timeline Timeline of the most material publicly verified disputes and related transactions affecting Databricks’ IP risk profile.

VIII.B Pending lawsuits initiated by Company

partially verified confidence: medium

The clearest publicly verified company-initiated dispute is Databricks v. Weisfield. Beyond that, the offensive or threatened-litigation picture remains largely private.

Evidence gaps

  • No public counsel schedule of company-initiated and threatened disputes was available.

Hidden risks

  • Confidential threatened disputes or settlements can sit outside the visible docket set.

Follow-up questions

  • What offensive IP, contract, or employment claims is Databricks currently pursuing or threatening outside public dockets?
Pending lawsuits initiated by the company
defendant or counterpartycourtfiled datematterstatussource or gap
James Weisfield and related entitiesW.D. Washington, 2:24-cv-014172024-09-06Databricks complaint involving former employee and affiliated IP entitiesFiled and publicly docketed; multiple defendants servedCourtListener docket
Other offensive disputesnot_publicly_verifiablenot_publicly_verifiableNo broader offensive litigation schedule was validated in-sessionnot_publicly_verifiableNeed company counsel schedule of active and threatened matters

The absence of more cases in this table should not be read as proof that Databricks has no additional offensive or confidential disputes.

VIII.C Environmental and employee safety issues and liabilities

partially verified confidence: medium

For a software platform like Databricks, the most relevant public safety and exposure signals are security, privacy, and regulated-workload obligations rather than classic environmental liabilities. The public record is strongest on certifications, weakest on operating evidence and regulator interaction.

Evidence gaps

  • No direct regulator correspondence, penetration-test exceptions, or audit findings were reviewed.

Hidden risks

  • Operating a platform for sensitive enterprise and public-sector data creates privacy and safety exposure even when enforcement is not yet public.

Follow-up questions

  • What privacy, security, or AI-governance remediation items are open today across major regulated programs?
Databricks diligence risk heatmap Heatmap of the report’s major risks by severity and likelihood.

VIII.D Material patents, copyrights, licenses, and trademarks

partially verified confidence: medium

Databricks’ public IP story is strongest on open-source lineage and current litigation, and weakest on the proprietary patent and trademark portfolio itself. That asymmetry is common for private software companies but still important in diligence.

Evidence gaps

  • No full patent, trademark, or outbound-license schedule was reviewed.

Hidden risks

  • A thin public proprietary-IP record can hide either a strong private portfolio or a surprisingly weak one.

Follow-up questions

  • What patents, trademarks, copyright registrations, and key licenses does Databricks actually own or depend on today?
Material IP, licenses, and trademarks
asset or rightjurisdiction or ownerpublic statussourcediligence note
Apache Spark lineage and trademark contextApache Software Foundation ecosystemDatabricks states its engineers are the original creators of Apache Spark.Open-source pageDatabricks influence is substantial but not equivalent to sole control of community governance.
Delta Lake and Apache Iceberg interoperabilityLinux Foundation Delta Lake and Apache Iceberg communitiesDatabricks publicly positions itself as bringing the two leading open lakehouse formats closer together.Open-source page and Tabular acquisition releaseNeed the actual interoperability roadmap, governance rights, and any contributor concentration analysis.
MLflow and Unity CatalogOpen-source / Databricks-led ecosystemPublic pages identify MLflow and Unity Catalog as part of Databricks’ open-source-led governance stack.Open-source pageNeed license, trademark, and contribution agreements for all materially used open projects.
Mosaic/DBRX model-training rights and copyright exposureDisputed in U.S. litigationMakkai alleges Mosaic-related training data use that now affects DBRX-related IP risk.CourtListener and The RegisterNeed training-data provenance records, outside-counsel analysis, and any indemnities from the Mosaic transaction.
Databricks patent and trademark portfolioDatabricks proprietary rightsnot_publicly_verifiableNo patent or TTAB docket sweep was completed beyond the public lawsuit setRequest a full patent, trademark, and license schedule from counsel before any transaction decision.

The strongest public IP evidence is around open-source positioning and current litigation, not the full Databricks proprietary portfolio.

VIII.E Insurance coverage and material exposures

not publicly verifiable confidence: low

No public insurance coverage schedule was verified. This matters because Databricks’ current legal and compliance posture could create material D&O, E&O, cyber, and IP exposure.

Evidence gaps

  • No public D&O, E&O, cyber, or IP coverage details were found.

Hidden risks

  • Large private-company legal exposure can outstrip older insurance programs if limits were set before current scale and AI risk profile.

Follow-up questions

  • What insurance limits, exclusions, and notice positions apply to the current litigation set and regulated-workload exposure?

VIII.F Material contracts

partially verified confidence: medium

Publicly visible contracts and transactions show Databricks is strategically intertwined with Microsoft, Anthropic, SAP, and recent acquisition targets. These relationships are central to the diligence case, but their economics remain private.

Evidence gaps

  • No operative contract text, side letters, or acquisition schedules were reviewed.

Hidden risks

  • Strategic contracts can carry unpublicized exclusivity, take-or-pay, or change-of-control terms that materially alter value.

Follow-up questions

  • Which strategic contracts include exclusivity, minimum commitments, or restrictions that would matter in a financing or M&A context?
Material contracts and strategic transactions visible from public sources
counterpartycontract or transactionpublic termsstrategic importancediligence gap
MicrosoftAzure Databricks first-party service and strategic investmentAzure billing and support flow through Microsoft; Microsoft joined Series E.Major distribution and infrastructure dependency with direct competitive overlap from Fabric.Need revenue sharing, termination rights, and change-of-control protections.
AnthropicFive-year strategic partnershipClaude models offered natively through Databricks on AWS, Azure, and GCP.Expands AI-agent offering and deepens third-party model dependence.No public committed spend, minimums, or exclusivity terms were found.
SAPSAP BDC delta-sharing pricing relationshipNormal 1.25x DBU uplift; temporary 1.0x promotional rate through 2026-08-31.Signals a real commercial integration path into large SAP data estates.Need the full OEM, resale, or referral economics and renewal structure.
MosaicMLAcquisitionApprox. $1.3B inclusive of retention packagesDefines Databricks’ GenAI positioning and current litigation exposure.Need reps and warranties, indemnities, and post-close integration economics.
Tabular / Neon / ArcionAcquisitions and acquisition intentDatabricks disclosed strategic rationale but not all prices or post-close economics.Extends interoperability, ingestion, and operational database scope.Need actual purchase prices, earnouts, retention packages, and synergy tracking.

This table captures only contracts and transactions visible in public sources; the operative legal documents remain private.

VIII.G Regulatory agency problems

inconclusive confidence: low

Databricks’ public regulatory profile is dominated by certifications and compliance signals rather than a directly verified adverse-action record. That is directionally positive, but not the same as a clean regulatory bill of health.

Evidence gaps

  • No enforcement log, regulator correspondence file, or privacy-impact assessment pack was available.

Hidden risks

  • Regulatory exposure can remain hidden until a customer incident, regulator inquiry, or cross-border transfer issue forces disclosure.

Follow-up questions

  • What regulator inquiries, privacy assessments, or government-customer audit findings has Databricks received in the last 24 months?
Regulatory certifications and public agency-action signal
regime or actionpublic statussourcediligence note
FedRAMP and DoD IL5Visible in Databricks Trust & Compliance as supported programsTrust & Compliance pageRequest actual authorization packages, scope boundaries, and current ATO status by deployment.
ISO, SOC, HIPAA, HITRUST, PCI-DSS, GDPR, CCPA, IRAP, ISMAP, K-FSI, and related programsVisible in Databricks Trust & ComplianceTrust & Compliance pageRequest latest reports, exceptions, and remediation trackers rather than relying on logo-level certification references.
Due-diligence package and SOC 2 availabilityDatabricks says customers can download a due-diligence package and request SOC 2 Type II reportsTrust & Compliance pageNeed the actual package contents and report dates.
Public adverse agency actions or sanctionsinconclusiveReviewed public evidence emphasized certifications rather than agency actionsAbsence of a found public action is not proof of absence; request regulator correspondence and enforcement logs.

This table should not be read as clearance from regulators; it only reflects what was visible in the reviewed source set.

Evidence

Evidence claims
IDClaimStatusSources
EC-001 Databricks says more than 15,000 organizations worldwide, including 70% of the Fortune 500, rely on the platform, and that it has 1,200+ global partners. partially verified medium SRC-001
EC-002 Databricks’ customer page says more than 20,000 customers across the globe and more than 60% of the Fortune 500 use Databricks. partially verified medium SRC-002
EC-003 Databricks describes its Data Intelligence Platform as a private, open, unified foundation for data and AI built on a lakehouse architecture. verified high SRC-003
EC-004 Databricks publicly ties itself to Apache Spark, Delta Lake, Apache Iceberg, Unity Catalog, MLflow, Delta Sharing, and Redash as core open-source technologies. verified high SRC-004
EC-005 Databricks markets Mosaic AI and Agent Bricks as a governed AI-agent system that can connect enterprise data with any AI model. verified high SRC-005
EC-006 AT&T’s Databricks case study says the company reduced fraud by up to 80% and now runs over 100 fraud-detection ML models in production. partially verified medium SRC-006
EC-007 Virgin Australia’s case study says Databricks drove a 75% increase in near real-time data availability and a 44% reduction in mishandled bags. partially verified medium SRC-007
EC-008 Databricks’ careers page says the company has 10,000+ employees, 30+ offices in 20+ countries, and is still growing aggressively. verified high SRC-008
EC-009 Databricks’ research page shows 48 public publications and explicitly ties the company to specialized teams across distributed systems, AI/ML, and applications. verified high SRC-009
EC-010 The current executive roster publicly includes Ali Ghodsi, Andy Kofoid, David Conte, Amy Reichanadter, Trâm Phi, Ron Gabrisko, Rick Schultz, Hatim Shafique, Fermín Serna, Naveen Zutshi, Vinod Marur, David Meyer, and Adam Conway. verified high SRC-010
EC-011 Databricks’ founders page still lists seven founders: Ali Ghodsi, Ion Stoica, Matei Zaharia, Patrick Wendell, Reynold Xin, Andy Konwinski, and Arsalan Tavakoli-Shiraji. verified high SRC-011
EC-012 Databricks’ board page shows founder control plus investor representation from a16z and NEA alongside independent directors. verified high SRC-012
EC-013 Databricks raised $250M in Series E at a $2.75B valuation. verified high SRC-013
EC-014 Series E also confirmed Databricks exceeded $100M ARR in 2018 and that Microsoft joined the round after Azure Databricks traction. verified high SRC-013
EC-015 Databricks raised over $500M in Series I at a $43B valuation and added NVIDIA as a strategic investor. verified high SRC-014
EC-016 Series I also said Databricks crossed a $1.5B revenue run rate, had over 10,000 global customers, more than 300 $1M-plus customers, and achieved 85% non-GAAP subscription gross margins. partially verified medium SRC-014
EC-017 Databricks’ Series J announcement says the company is raising $10B of expected non-dilutive financing at a $62B valuation and had completed $8.6B to date. partially verified high SRC-015
EC-018 Series J also says Databricks grew over 60% year-over-year in Q3 FY2025, expects to cross a $3B revenue run rate, expects positive free cash flow in Q4 FY2025, has 500+ customers above $1M annual run rate, and sees Databricks SQL at a $600M run rate. partially verified medium SRC-015
EC-019 Forbes reported Databricks raised $1B in Series G at a $28B valuation, had $425M+ ARR growing 75%+, and added AWS, CapitalG, Salesforce Ventures, and Microsoft to the investor base. verified high SRC-016
EC-020 Forbes reported Databricks raised $1.6B in Series H at a $38B valuation, exceeded $600M ARR, aimed for 3,000+ employees by year-end 2021, and hired Andy Kofoid from Salesforce. verified high SRC-017
EC-021 Databricks’ June 2024 NVIDIA partnership release says Databricks reached over $1.6B in revenue for its fiscal year ending January 31, 2024, representing over 50% year-over-year growth. partially verified medium SRC-018
EC-022 Databricks and Anthropic publicly announced a five-year partnership that brings Claude models natively to the Databricks platform across AWS, Azure, and GCP. verified high SRC-019
EC-023 TechCrunch reported Azure Databricks is a first-party Azure service, with Microsoft handling billing and support. verified high SRC-020
EC-024 Databricks said the MosaicML acquisition was valued at approximately $1.3B, inclusive of retention packages. verified high SRC-021
EC-025 Databricks said the Arcion acquisition was valued at over $100M, inclusive of incentives. verified high SRC-022
EC-026 Databricks’ Tabular acquisition release says the company wants to bring Delta Lake and Apache Iceberg closer together over time to reduce lakehouse format fragmentation. verified medium SRC-023
EC-027 Databricks’ Neon acquisition release says over 80 percent of databases provisioned on Neon were created automatically by AI agents. partially verified medium SRC-024
EC-028 Databricks announced more than $850M of UK investment, 500+ UK employees, a new 137,000-square-foot London hub, and over 50% of the FTSE 100 as regional customers. partially verified medium SRC-025
EC-029 Databricks announced a $300M ANZ investment, said Q1 regional growth exceeded 85% year over year, and highlighted Lakebase, Genie, and Agent Bricks as regionally available priorities. partially verified medium SRC-026
EC-030 Databricks publishes Lakeflow Jobs pricing at $0.15 / DBU for classic jobs and $0.35 / DBU for serverless jobs. verified high SRC-027
EC-031 Databricks SQL pricing is publicly listed at $0.22 / DBU for SQL Classic, $0.55 / DBU for SQL Pro, and $0.70 / DBU for SQL Serverless. verified high SRC-028
EC-032 Databricks publicly prices Lakebase at $0.092 per capacity unit hour and $0.345 per GB-month of storage. verified high SRC-029
EC-033 Databricks’ SAP Business Data Cloud pricing page says normal DBU processing runs at a 1.25x uplift but is temporarily promoted at 1.0x through 2026-08-31. verified high SRC-030
EC-034 Databricks’ trust center publicly offers a due-diligence package and lists a broad certification set including FedRAMP, DoD IL5, SOC, ISO, HIPAA, HITRUST, PCI-DSS, GDPR, and CCPA. verified medium SRC-031
EC-035 The Makkai complaint shows authors sued Databricks and Mosaic ML in May 2024 over alleged copyright infringement tied to model training. verified high SRC-032
EC-036 Independent public reporting says Databricks’ motion to dismiss in the Makkai case was denied and frames the case as carrying extraordinary damages risk tied to roughly 196,000 titles and statutory damages up to $150,000 per work. partially verified medium SRC-033
EC-037 Databricks filed suit against former employee James Weisfield and related entities in September 2024. verified high SRC-034
EC-038 Byteweavr sued Databricks for patent infringement in March 2024 in the Eastern District of Texas. verified high SRC-035
EC-039 R2 Solutions sued Databricks for patent infringement in December 2023 and the public docket remained active through May 2026. verified high SRC-036
EC-040 Snowflake publicly describes its platform as serverless, managed, multi-cloud, and governance-heavy, confirming direct overlap with Databricks’ warehouse-plus-AI positioning. verified medium SRC-037
EC-041 Microsoft Fabric publicly describes itself as an end-to-end analytics SaaS platform spanning data engineering, data science, warehousing, databases, and governance over OneLake. verified high SRC-038
EC-042 AWS publicly markets a comprehensive analytics stack plus an integrated SageMaker experience with Iceberg-compatible lakehouse access, confirming meaningful functional overlap with Databricks. verified medium SRC-039
EC-043 Google BigQuery publicly positions itself as an autonomous data-to-AI platform with built-in AI, agents, and Apache Iceberg interoperability. verified medium SRC-040
EC-044 Palantir Foundry publicly markets itself as an Ontology/AI-powered operating system for the modern enterprise. verified medium SRC-041
EC-045 Reviewed public customer materials disclose broad logo breadth and high-value customer counts, but do not disclose top-customer revenue share, top-10 concentration, churn, or retention. not publicly verifiable medium SRC-002SRC-015
EC-046 Reviewed public financial materials do not provide audited financial statements, AR aging, backlog schedules, or a public debt inventory. not publicly verifiable medium SRC-013SRC-014SRC-015
EC-047 Reviewed public GTM materials do not disclose sales compensation, average quota, sales-cycle duration, or marketing-budget productivity. not publicly verifiable medium SRC-027SRC-028SRC-025SRC-026
EC-048 Reviewed public people materials do not disclose executive compensation schedules, stock-plan mechanics, or two-year attrition data. not publicly verifiable medium SRC-008SRC-010SRC-011
EC-049 The public founders and leadership pages show Andy Konwinski remains listed as a founder but is absent from the current executive-team page. partially verified medium SRC-010SRC-011
EC-050 The regulatory evidence reviewed in-session primarily shows certifications, standards, and due-diligence materials rather than a public record of adverse agency actions or sanctions against Databricks. inconclusive low SRC-031
Sources
IDPublisherTitleAccessed
SRC-001 Databricks Databricks About Us 2026-05-14
SRC-002 Databricks Customer Success Stories | Databricks 2026-05-14
SRC-003 Databricks The Databricks Data Intelligence Platform 2026-05-14
SRC-004 Databricks Built on Open Source | Databricks 2026-05-14
SRC-005 Databricks Artificial Intelligence | Databricks 2026-05-14
SRC-006 Databricks AT&T Customer Story | Databricks 2026-05-14
SRC-007 Databricks Virgin Australia Customer Story | Databricks 2026-05-14
SRC-008 Databricks Databricks Careers 2026-05-14
SRC-009 Databricks Databricks Research 2026-05-14
SRC-010 Databricks Leadership Team | Databricks 2026-05-14
SRC-011 Databricks Founders | Databricks 2026-05-14
SRC-012 Databricks Board of Directors | Databricks 2026-05-14
SRC-013 Databricks Databricks Secures $250M Series E, Valuation at $2.75B 2026-05-14
SRC-014 Databricks Databricks Raises Series I at $43B Valuation 2026-05-14
SRC-015 Databricks Databricks Raising $10B Series J at $62B Valuation 2026-05-14
SRC-016 Forbes Databricks at $28B Valuation From AWS, Google, Microsoft, Salesforce 2026-05-14
SRC-017 Forbes Databricks Series H at $38B Valuation 2026-05-14
SRC-018 Databricks Databricks and NVIDIA Strengthen Partnership 2026-05-14
SRC-019 Databricks Databricks and Anthropic Sign Landmark Deal to Bring Claude Models 2026-05-14
SRC-020 TechCrunch Microsoft Makes Databricks a First-Party Service on Azure 2026-05-14
SRC-021 Databricks Databricks Signs Definitive Agreement to Acquire MosaicML 2026-05-14
SRC-022 Databricks Databricks Agrees to Acquire Arcion 2026-05-14
SRC-023 Databricks Databricks Agrees to Acquire Tabular 2026-05-14
SRC-024 Databricks Databricks Agrees to Acquire Neon 2026-05-14
SRC-025 Databricks Databricks Announces $850M UK Investment 2026-05-14
SRC-026 Databricks Databricks Invests $300M in ANZ Over Next Three Years 2026-05-14
SRC-027 Databricks Lakeflow Jobs Pricing 2026-05-14
SRC-028 Databricks Databricks SQL Pricing 2026-05-14
SRC-029 Databricks Lakebase Pricing 2026-05-14
SRC-030 Databricks Delta Share from SAP Business Data Cloud Pricing 2026-05-14
SRC-031 Databricks Databricks Trust & Compliance 2026-05-14
SRC-032 CourtListener Makkai v. Databricks, Inc. | CourtListener docket 2026-05-14
SRC-033 The Register Databricks can't seem to shake authors' copyright claim 2026-05-14
SRC-034 CourtListener Databricks Inc. v. Weisfield | CourtListener docket 2026-05-14
SRC-035 CourtListener Byteweavr, LLC v. Databricks, Inc. | CourtListener docket 2026-05-14
SRC-036 CourtListener R2 Solutions LLC v. Databricks, Inc. | CourtListener docket 2026-05-14
SRC-037 Snowflake The Snowflake Platform 2026-05-14
SRC-038 Microsoft Learn Microsoft Fabric Overview 2026-05-14
SRC-039 Amazon Web Services Analytics on AWS 2026-05-14
SRC-040 Google Cloud BigQuery 2026-05-14
SRC-041 Palantir Palantir Foundry 2026-05-14

Disclaimer

This report is a public-evidence diligence snapshot, not investment advice. Important financial, legal, technical, and contractual facts remain non-public and should be verified directly with management and primary documents before any investment decision.