{"catalog":"https://launchinyourcloud.com/api/v1/catalog.json","catalogRevision":"170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde","kind":"listing","listing":{"architecture":"Vendor control plane; customer classic compute","categories":["data-analytics"],"category":"Data \u0026 analytics","categoryFit":{"data-analytics":"Data and AI platform with classic compute in your cloud environment."},"cloudEvidence":[{"clouds":["aws"],"notes":"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.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Databricks classic compute architecture","url":"https://docs.databricks.com/aws/en/getting-started/high-level-architecture","vendorSupport":"not-assessed"},{"clouds":["azure"],"notes":"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.","reviewed":"2026-11-12","sourceType":"provider-guide","title":"Databricks classic compute architecture","url":"https://learn.microsoft.com/en-us/azure/databricks/getting-started/high-level-architecture","vendorSupport":"not-assessed"},{"clouds":["gcp"],"notes":"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.","reviewed":"2026-11-12","sourceType":"vendor-documentation","title":"Databricks classic compute architecture","url":"https://docs.databricks.com/gcp/en/security/network/concepts/architecture","vendorSupport":"not-assessed"}],"cloudReviewed":"2026-11-12","clouds":["aws","azure","gcp"],"deploymentPaths":[{"boundary":"cloud-account","cloud":"aws","controlPlane":"vendor-hosted","evidence":[0],"operator":"shared"},{"boundary":"cloud-account","cloud":"azure","controlPlane":"vendor-hosted","evidence":[1],"operator":"shared"},{"boundary":"cloud-account","cloud":"gcp","controlPlane":"vendor-hosted","evidence":[2],"operator":"shared"}],"description":"Data and AI platform with classic compute in your cloud environment.","diligence":{"footprint":{"reviewed":"2026-11-20","scope":"Classic AWS compute sizing unresolved without workload and topology","source":"https://docs.databricks.com/aws/en/compute/configure","status":"inconclusive","summary":"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."},"iac":{"artifactRef":"Pin Databricks and cloud provider versions","artifactUrl":"https://github.com/databricks/terraform-provider-databricks","reviewed":"2026-11-20","scope":"Classic AWS workspace/infrastructure administration; serverless has a different boundary","source":"https://docs.databricks.com/aws/en/dev-tools/terraform/","status":"documented","summary":"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."},"licensePricing":{"reviewed":"2026-11-20","scope":"Databricks commercial usage model; no workload-specific quote or total cost","source":"https://www.databricks.com/product/pricing","status":"documented","summary":"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."},"scim":{"availability":"edition-dependent","reviewed":"2026-11-16","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","status":"documented","summary":"Account-level SCIM user/group provisioning is documented with Premium or above. Identity federation is required for workspace assignment; workspace-level provisioning is legacy."},"sso":{"availability":"available","reviewed":"2026-11-14","scope":"Databricks AWS account/workspace identity; separate vendor-operated control plane","source":"https://docs.databricks.com/aws/en/security/auth/single-sign-on/","status":"documented","summary":"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."}},"id":"databricks","infrastructure":["servers"],"infrastructureNotes":"Classic compute uses customer-cloud compute resources. Databricks serverless compute is a different vendor-managed deployment and is outside this listing.","infrastructureReviewed":"2026-11-10","infrastructureSources":["https://docs.databricks.com/aws/en/compute/use-compute"],"install":"Cloud-specific workspace provisioning","installMethods":["vendor-assisted"],"kind":"platform","license":"Commercial","licenseModel":"commercial-only","licenseModelNotes":"This listing covers the commercially provided managed/BYOC service, not a separately licensed open-source engine or library.","licenseModelSources":["https://docs.databricks.com/aws/en/getting-started/high-level-architecture"],"licenseReviewed":"2026-11-10","model":"BYOC","modelLabel":"Shared operations · vendor control plane","name":"Databricks classic compute","notes":"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.","operationReview":{"controlPlane":"vendor-hosted","modelLabel":"Shared operations · vendor control plane","operator":"shared","reviewed":"2026-11-20","source":"https://docs.databricks.com/aws/en/getting-started/high-level-architecture","summary":"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."},"operations":"The vendor manages the control plane. Your team configures classic compute, cloud resources and policies.","publisher":false,"reviewed":"2026-11-18","sources":[{"title":"AWS architecture","url":"https://docs.databricks.com/aws/en/getting-started/high-level-architecture"},{"title":"Azure architecture","url":"https://learn.microsoft.com/en-us/azure/databricks/getting-started/high-level-architecture"},{"title":"Google Cloud architecture","url":"https://docs.databricks.com/gcp/en/security/network/concepts/architecture"},{"title":"Classic versus serverless compute","url":"https://docs.databricks.com/aws/en/compute/use-compute"},{"title":"Databricks upcoming behavior changes","url":"https://docs.databricks.com/aws/en/release-notes/whats-coming"}],"url":"https://launchinyourcloud.com/directory/databricks/","website":"https://www.databricks.com/"},"schemaVersion":1,"url":"https://launchinyourcloud.com/directory/databricks/"}