Databricks classic compute
Data and AI platform with classic compute in your cloud environment.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Cloud-specific workspace provisioning
External vendor control plane
Runs in
Documented customer environment
Vendor control plane; customer classic compute
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Customer and vendor
The vendor manages the control plane. Your team configures classic compute, cloud resources and policies.
Deployment boundaries by provider
- AWS: Customer cloud account · Shared operations
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Databricks classic compute architecture ↗ · Source checked 2026-11-12
- Azure: Customer cloud account · Shared operations
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Databricks classic compute architecture ↗ · Source checked 2026-11-12
- Google Cloud: Customer cloud account · Shared operations
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Databricks classic compute architecture ↗ · Source checked 2026-11-12
Classic compute and workspace storage are in the customer cloud account. Databricks operates the separate management plane; the customer configures compute, networking and policy. Serverless compute is outside this listing.
Operating responsibility source ↗ · Checked 2026-11-20
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Cloud-specific workspace provisioning |
|---|---|
| Infrastructure | Servers / containers Classic compute uses customer-cloud compute resources. Databricks serverless compute is a different vendor-managed deployment and is outside this listing. |
| Licensing model | Commercial Only This listing covers the commercially provided managed/BYOC service, not a separately licensed open-source engine or library. |
| License | Commercial |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
5 of 12 fields researched (42%) · 4 documented · 1 unresolved. Evidence coverage is not a feature score.
- Single sign-on
AvailableEvidence and scope for Single sign-on
The AWS account/workspace login configuration supports SAML 2.0 or OpenID Connect. Unified-login and emergency-access settings must be planned for the account.
Databricks AWS account/workspace identity; separate vendor-operated control plane · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- SCIM provisioning
Edition-dependentEvidence and scope for SCIM provisioning
Account-level SCIM user/group provisioning is documented with Premium or above. Identity federation is required for workspace assignment; workspace-level provisioning is legacy.
Databricks on AWS; Premium or above; not a statement about every cloud edition · Source ↗ · Reviewed 2026-11-16
Edition-dependent · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
The vendor-supported Terraform provider manages workspaces and administrative resources; AWS infrastructure is provisioned with the AWS provider. Databricks recommends Terraform for cloud/external resources and administrative actions, and Automation Bundles for jobs and pipelines. Select compatible provider versions and least-privilege credentials.
Classic AWS workspace/infrastructure administration; serverless has a different boundary · Source ↗ · Deployment artifact ↗ (Pin Databricks and cloud provider versions) · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The classic-compute guide requires selecting runtime, worker types, driver, autoscaling and policies for the workload. It does not establish one platform-wide CPU/RAM floor. Size the customer-account compute separately from Databricks-hosted control-plane and optional serverless services.
Classic AWS compute sizing unresolved without workload and topology · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
Databricks publishes usage-based product pricing in DBUs with optional committed-use contracts. Rates depend on cloud, region, workload and product. Customer-account classic infrastructure can incur a separate cloud bill; obtain the selected product rate and contract rather than treating a starting DBU price as the whole deployment cost.
Databricks commercial usage model; no workload-specific quote or total cost · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
Show all fields (7 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
This entry covers classic compute only. Serverless compute runs in a Databricks-managed environment and is outside this entry. Confirm the responsibility split and metadata flows for your cloud. Beginning November 18, 2026, new VARIANT tables created on Databricks Runtime 17.3 or later automatically use variantShredding. Databricks Runtime 15.4 cannot read or write those tables, so upgrade affected classic clusters to 16.4 or later before creating or accessing them.
Category fit
- Data & analytics
- Data and AI platform with classic compute in your cloud environment.
Compare within Data & analytics
- ActivityInfo (Self-Managed Server)Commercial self-managed data collection, relational records and program-reporting platform.
- Azure
- Airbyte Self-ManagedSelf-managed data movement and ELT platform with customer-operated connectors and job execution.
- AWS
- Azure
- Google Cloud
- DigitalOcean
- Apache Doris Self-HostedApache-licensed analytical database with upstream AWS EKS/Alibaba ACK/ACS guides and a separately packaged cloudimg Azure VM path.
- AWS
- Azure
- Alibaba Cloud
- Apache DruidColumn-oriented analytics database for interactive queries over streaming and historical event data.
- AWS
- Azure
- Google Cloud
- Apache SupersetBusiness intelligence and data exploration platform for SQL analysis, visualizations and shared dashboards.
- AWS
- AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
- AWS
- Azure Trusted Research EnvironmentOpen-source reference platform for isolated research workspaces and controlled data movement.
- Azure
- Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
- Google Cloud
Showing 8 of 43 other listings in Data & analytics. These products address related workflows; read their category-fit notes before comparing scope. See all of Data & analytics →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- AWS architecture ↗docs.databricks.com
- Azure architecture ↗learn.microsoft.com
- Google Cloud architecture ↗docs.databricks.com
- Classic versus serverless compute ↗docs.databricks.com
- Databricks upcoming behavior changes ↗docs.databricks.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Databricks classic compute architecture ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The classic compute plane runs in the customer cloud account, subscription or project; Databricks operates its separate control plane. This badge describes classic compute, not serverless compute in a Databricks-managed account. Review the selected workspace networking, region and service terms.
- Databricks classic compute architecture ↗ · Azure
Provider guide · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The classic compute plane runs in the customer cloud account, subscription or project; Databricks operates its separate control plane. This badge describes classic compute, not serverless compute in a Databricks-managed account. Review the selected workspace networking, region and service terms.
- Databricks classic compute architecture ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The classic compute plane runs in the customer cloud account, subscription or project; Databricks operates its separate control plane. This badge describes classic compute, not serverless compute in a Databricks-managed account. Review the selected workspace networking, region and service terms.
- Databricks classic compute architecture ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked