Skip to main content

Deployment options

Self-Deployed Runtime uses containerization to run across any OCI-compliant environment. Each connector or application is packaged as a container image, so you can deploy on your existing infrastructure without changing your operational practices.

Did you know?

SDR requires additional enablement and licensing. Contact your Atlan representative for details.

Deployment models​

Atlan provides three deployment models. Each targets a different operational context—from quick evaluation to production scale to fully automated management.

Docker Compose is the simplest path. Atlan generates a docker-compose.yaml and environment configuration for each connector. You run the compose file on any Docker host. This is the right choice for evaluating a connector, running a single app, or environments where you want full manual control over every deployment step.

Kubernetes is for production workloads. Atlan provides Helm charts compatible with both managed clusters (EKS, AKS, GKE) and self-hosted Kubernetes. You get horizontal scaling, high availability, and the full Kubernetes operational model. This is the right choice if you already operate Kubernetes and need enterprise-grade reliability and orchestration.

SDR Orchestrator Private Preview is for managing multiple connector apps on a Linux VM without repeating manual setup steps for every app. You run one container—the orchestrator—and it manages the full lifecycle of all your connector apps: install, upgrade, and autoupdate. After the one-time bootstrap, every app is installed and managed from the Atlan UI with no per-app terminal work. This is the right choice if you're deploying several connectors and want automated lifecycle management. See Install App via SDR Orchestrator and SDR Orchestrator.

For Docker Compose and Kubernetes, the generated deployment artifacts include sections where you can modify infrastructure-specific attributes like security context, resource constraints, labels and annotations, and environment variables.

Container image​

Each connector app container image includes four key components that work in collaboration:

  • Dapr sidecar process for service interaction
  • Temporal Python SDK for connecting to Atlan's orchestrator
  • FastAPI server for handling requests
  • Core application logic implemented as Temporal workers

For more details about how these components interact, see the Architecture - Core components reference.

See also​