Integrations overview

Git providers, Docker registries, and cloud accounts used by dFlow Services and Worker Nodes.

Written By Zoro

Last updated 9 days ago

dFlow connects to external systems so Services can pull source code, images, and (on dFlow Cloud) provider-managed Worker Nodes.

Git sources

Connect repositories for App Services:

GitHub integration: GitHub App install and repository access.
GitLab integration: OAuth on gitlab.com or self-hosted BYO OAuth applications, plus manual PAT deploys.
Git source integrations: Bitbucket, Gitea, Azure DevOps, and shared token patterns (branches, deploy triggers).

Automatic deploy on push depends on provider and configuration; see each guide.

Container registries

Docker registry integration: pull private images into Docker Services.

Backup storage

Backup storage integration: connect S3-compatible buckets so database Services can store external backups (off-server). Configure credentials under Integrations, then pick a verified provider on each database Backups tab.

Cloud providers

Azure integration is available for linking a subscription with Microsoft sign-in and provisioning Worker Nodes in your Azure account. AWS integration covers access-key linking where supported. Google Cloud Platform and DigitalOcean may show as Coming soon in the UI.

See Azure integration and AWS integration under Integrations in the sidebar. Cloud provider accounts explains how linked accounts relate to Organisations, Environments, and least-privilege habits.

Permissions and troubleshooting

Integration permissions and prerequisites
Integration troubleshooting
Integration issues under Troubleshooting in the sidebar (symptom-led fixes and links to deploy logs)

Security and Organisation access

Integrations authorize dFlow to reach Git hosts, registries, and cloud APIs on behalf of your Organisation. Who may add or rotate those connections is governed by Roles and permissions under Security and Team Management in the sidebar and the Tenant access model under Security and Team Management in the sidebar.

SSH access to Worker Nodes and cloud firewall rules are separate from Git or registry tokens. Use SSH keys under Security and Team Management in the sidebar and Security groups under Security and Team Management in the sidebar when you attach compute.