SDR Orchestrator image and versioning
Identify the container images used for the SDR Orchestrator, understand their versioning, and find the exact version assigned to your tenant.
This page identifies the container images used to run the Self-Deployed Runtime (SDR) Orchestrator. Use it as vendor, product, and version evidence when registering the software with a governance or procurement process.
SDR Orchestrator
The SDR Orchestrator is distributed as a container image. The image repository depends on your deployment platform:
| Platform | Container image repository | Registry |
|---|---|---|
| Docker/Podman | atlanhq/atlan-sdr-orchestrator | Docker Hub, under the private atlanhq/* namespace |
| Kubernetes | atlanhq/atlan-sdr-orchestrator-k8s | Docker Hub, under the private atlanhq/* namespace |
| Field | Value |
|---|---|
| Vendor | Atlan |
| Product name | SDR Orchestrator |
| Release identifier (version) | Image tag |
The image repositories are private. Pulling an image requires the Docker Hub Personal Access Token (PAT) that your Atlan representative provides. The PAT is rotated periodically.
How SDR Orchestrator versioning works
The image tag is the official release identifier for an SDR Orchestrator image. The Docker/Podman and Kubernetes images can use different repository names and tags because they're platform-specific deployment artifacts.
A downloaded SDR package contains an image reference that's pre-filled for the target platform. For example, the public Docker/Podman package published on August 27, 2026 referenced atlanhq/atlan-sdr-orchestrator:main-dc31d17abcd. This package value is a point-in-time bootstrap value and might not be assigned to your tenant.
In orchestrator mode, Atlan manages the lifecycle of the SDR Orchestrator and connector apps independently. The Orchestrator continuously reconciles to the version Atlan publishes for your tenant. Don't replace the tag in an SDR package with an example from this page.
For installation steps, see Install SDR Orchestrator on Docker/Podman or Install SDR Orchestrator on Kubernetes.
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. It returns the image and version for SDR-capable apps, including the SDR Orchestrator.
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 the SDR Orchestrator. 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.