Databricks app image and versioning
Identify the container image used for the Databricks assets app, understand its versioning, and find the exact version assigned to your tenant.
This page identifies the container image used to run the Databricks assets app on Self-Deployed Runtime (SDR). Use it as vendor, product, and version evidence when registering the software with a governance or procurement process.
Databricks assets app
The Databricks assets app is distributed as a container image:
| Field | Value |
|---|---|
| Vendor | Atlan |
| Product name | Databricks assets app |
| Container image | atlanhq/atlan-databricks-app |
| Registry | Docker Hub, under the private atlanhq/* namespace |
| Release identifier (version) | Image tag, for example, 0.4.1 |
The atlanhq/atlan-databricks-app repository is private. Pulling the image requires the Docker Hub Personal Access Token (PAT) that your Atlan representative provides. The PAT is rotated periodically.
How Databricks app versioning works
The image tag is the official release identifier for the Databricks assets app. Each tag is immutable and maps one-to-one to a specific build.
As of September 1, 2026, Databricks release v0.4.1 has an all-channel release record in Atlan's Global Marketplace. Its container image is atlanhq/atlan-databricks-app:0.4.1.
Atlan releases aren't time-boxed, and releases can be assigned to tenants in cohorts. An all-channel release record doesn't mean every tenant is assigned that release at the same time.
Use the tenant-specific image reference in the next section for procurement, deployment, and mirroring. If the assigned version changes, update your governance record to match the new tag.
Find exact version assigned to your tenant
Use the latest-releases endpoint to determine the source image reference that Atlan has assigned to your tenant.
This requires a valid Atlan API token:
curl -sS \
-H "Authorization: Bearer $ATLAN_API_TOKEN" \
"https://<your-tenant>.atlan.com/api/service/marketplace/latest-releases"
Find the release whose app_name identifies Databricks. The image value is a repo:tag reference and is the exact source image assigned to your tenant at that time.
There is no single version that's correct for every tenant. Different tenants can be assigned different active release cohorts. The endpoint response, not the examples on this page, is the source of truth for your deployment.
Verify image
Atlan signs every SDR image with keyless Cosign. Before you deploy or mirror an image, verify its signature using the image reference returned for your tenant. See Verify container images.
For private-registry guidance, see Image procurement approach and Keep private registry in sync.