Functionality
Find answers to common questions about how Self-Deployed Runtime features compare to Atlan-hosted execution modes.
Some capabilities shown here may require additional enablement or licensing. Contact your Atlan representative for details.
What features work differently with Self-Deployed Runtime?
Self-Deployed Runtime focuses on secure metadata extraction from your infrastructure. Some interactive features available in Atlan-hosted mode require different approaches:
| Feature | Atlan-hosted | Self-Deployed Runtime |
|---|---|---|
| Metadata extraction | ✅ Supported | ✅ Supported |
| Authentication testing | ✅ Test during setup | ⚠️ Configure credentials, test after deployment |
| Preflight checks | ✅ Pre-validate permissions | ⚠️ Validate permissions manually before deployment |
| Filter selection | ✅ Interactive dropdowns | ⚠️ Use regular expressions to specify filters |
| Sample data preview | ✅ Supported | ❌ Not available |
| Insights queries | ✅ Supported | ❌ Not available |
| Tag reverse sync | ✅ Supported | ❌ Not available |
For workflows requiring interactive features, use Atlan-hosted execution mode. For secure metadata extraction from private infrastructure, use Self-Deployed Runtime.
How does job polling work for Self-Deployed Runtime?
Self-Deployed Runtime uses Temporal workers that maintain persistent gRPC connections to Atlan's Temporal service. Workers continuously poll Temporal task queues and pick up tasks as soon as they're available. For more information, see Temporal worker.
How does Self-Deployed Runtime use persistent storage, and who is responsible for cleanup?
SDR writes extracted and transformed metadata to your configured object store (S3, Blob, or GCS), then uploads it to Atlan's tenant storage for processing. The data path is: source systems → SDR application memory → configured object store → Atlan SaaS tenant storage.
Atlan only requires access to files in the object store for the current run. You can clean up files on your persistent storage at regular intervals based on your internal auditing and maintenance policies.
See also
- Deployment and security: Frequently asked questions about supported deployment platforms and security incident handling.
- Architecture: Component interactions and how security controls map to the system design.
- Security: Security architecture, authentication, encryption, and compliance controls for Self-Deployed Runtime.