
# Databricks classic compute

Data and AI platform with classic compute in your cloud environment.

Canonical page: https://launchinyourcloud.com/directory/databricks/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Databricks classic compute

Data and AI platform with classic compute in your cloud environment.

- Listing: https://launchinyourcloud.com/directory/databricks/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Shared operations · vendor control plane
- Infrastructure IDs: servers
- License: Commercial
- Licensing model: commercial-only
- Installation: Cloud-specific workspace provisioning
- Architecture: Vendor control plane; customer classic compute
- Operations: The vendor manages the control plane. Your team configures classic compute, cloud resources and policies.
- Product website: https://www.databricks.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

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.

This listing covers the commercially provided managed/BYOC service, not a separately licensed open-source engine or library.

Classic compute uses customer-cloud compute resources. Databricks serverless compute is a different vendor-managed deployment and is outside this listing.


### Category fit

- data-analytics: Data and AI platform with classic compute in your cloud environment.

### Deployment boundaries


- aws: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.databricks.com/aws/en/getting-started/high-level-architecture (checked 2026-11-12). 

- azure: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://learn.microsoft.com/en-us/azure/databricks/getting-started/high-level-architecture (checked 2026-11-12). 

- gcp: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.databricks.com/gcp/en/security/network/concepts/architecture (checked 2026-11-12). 

Operating responsibility: 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. Source: https://docs.databricks.com/aws/en/getting-started/high-level-architecture (checked 2026-11-20).


### Cloud deployment evidence

- Databricks classic compute architecture (aws): https://docs.databricks.com/aws/en/getting-started/high-level-architecture
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.

- Databricks classic compute architecture (azure): https://learn.microsoft.com/en-us/azure/databricks/getting-started/high-level-architecture
  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.
  Source type: provider-guide; reviewed: 2026-11-12; vendor support: not-assessed.

- Databricks classic compute architecture (gcp): https://docs.databricks.com/gcp/en/security/network/concepts/architecture
  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.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- AWS architecture: https://docs.databricks.com/aws/en/getting-started/high-level-architecture

- Azure architecture: https://learn.microsoft.com/en-us/azure/databricks/getting-started/high-level-architecture

- Google Cloud architecture: https://docs.databricks.com/gcp/en/security/network/concepts/architecture

- Classic versus serverless compute: https://docs.databricks.com/aws/en/compute/use-compute

- Databricks upcoming behavior changes: https://docs.databricks.com/aws/en/release-notes/whats-coming

### Licensing sources

- https://docs.databricks.com/aws/en/getting-started/high-level-architecture

### Infrastructure sources

- https://docs.databricks.com/aws/en/compute/use-compute


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. 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. Scope: Databricks AWS account/workspace identity; separate vendor-operated control plane. Source: https://docs.databricks.com/aws/en/security/auth/single-sign-on/ (reviewed 2026-11-14).

- SCIM provisioning: Edition-dependent. Account-level SCIM user/group provisioning is documented with Premium or above. Identity federation is required for workspace assignment; workspace-level provisioning is legacy. Scope: Databricks on AWS; Premium or above; not a statement about every cloud edition. Source: https://docs.databricks.com/aws/en/admin/users-groups/scim (reviewed 2026-11-16).

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. 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. Scope: Classic AWS workspace/infrastructure administration; serverless has a different boundary. Source: https://docs.databricks.com/aws/en/dev-tools/terraform/ (reviewed 2026-11-20). Deployment artifact: https://github.com/databricks/terraform-provider-databricks. Artifact reference: Pin Databricks and cloud provider versions.

- Minimum footprint / sizing: Sources checked — unresolved. 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. Scope: Classic AWS compute sizing unresolved without workload and topology. Source: https://docs.databricks.com/aws/en/compute/configure (reviewed 2026-11-20).

- License pricing: Documented. 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. Scope: Databricks commercial usage model; no workload-specific quote or total cost. Source: https://www.databricks.com/product/pricing (reviewed 2026-11-20).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






