Self-deployed runtime
Atlan Self-Deployed Runtime enables deploying and running Atlan applications on your infrastructure enhancing security and scalability.
SDR requires additional enablement and licensing. Contact your Atlan representative for details.
Atlan's Self-Deployed Runtime crawls metadata entirely inside your own infrastructure, then syncs only metadata to Atlan SaaS—data never leaves your environment.
Why self-deployed runtime
Self-Deployed Runtime keeps your data secure while giving you the flexibility to deploy anywhere and manage everything centrally:
Zero data exposure
- No inbound connectivity (ingress) to the source applications from the Atlan tenant
- Source-system credentials/secrets never leave your infrastructure
- No ingress to the Self-Deployed Runtime application from the Atlan tenant
- Audit trail and system logs for all activities/connections
Deploy anywhere
- Works with any OCI-compatible runtime
- Managed container orchestration (AWS Elastic Container Service, Azure Container Instances, Google Cloud Run)
- Managed Kubernetes clusters (AWS Elastic Kubernetes Service, Azure Kubernetes Service, GKE)
- Docker, Podman, or on-premises Kubernetes deployments
Enterprise-ready
- Built-in monitoring and alerting
- Horizontal/Vertical scaling based on demand
- Professional support and updates
- Connects with external systems for auditing and compliance
Centralized management
- Configure Atlan workflows to run on App deployments
- Monitor execution centrally from the Atlan tenant
- Check status of each Self-Deployed Runtime application
- Manage schedules across workflow execution
Get started
Deploy
Choose your platform — Docker Compose, Kubernetes, or SDR Orchestrator — and deploy the App.
Configure
Configure the Atlan workflow to run on the deployed application.
Run
Manage schedules, run jobs, view status, monitor execution, and download logs.
⚠️ Limitations to evaluate before choosing self-deployed runtime
While the architecture provides flexibility and control, there are a few limitations to be aware of:
- Infrastructure cost and maintenance: You bear infrastructure costs for running the Application Runtime and perform regular maintenance activities.
- Monitoring handled locally: You're responsible for monitoring the runtime environment and take action when the infrastructure goes down
- Certain App functionalities unavailable: Features like Test Authentication, Preflight check, Data Exploration module, sample data preview, and tag reverse sync aren't available in Self-Deployed Runtime.
For details, see What features work differently with Self-Deployed Runtime?