Skip to main content

Deployment options

Deployment in Self-Deployed Runtime leverages containerization to run across any OCI-compliant runtime environment. Since each connector or application is containerized, you can deploy them on your existing container infrastructure without changing your operational practices. Understanding the deployment model helps you choose the right approach for your infrastructure and security requirements.

Deployment artifacts​

Atlan provides deployment artifacts for popular runtimes:

  • Docker Runtime: Docker Compose files for direct container deployment
  • Kubernetes: Helm charts compatible with both managed and self-hosted clusters

The deployment chart includes sections where you can modify infrastructure-specific attributes like security context, resource constraints, labels and annotations, and environment variables.

Container image​

Each 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.

Once built, images are distributed through Atlan's Harbor open-source registry with vulnerability scanning, image signing for integrity verification, and secure distribution capabilities. Access to the Harbor registry requires authentication so only authorized personnel can pull or push images.

See also​