Self-Hosting dFlow
dFlow docs: self-hosting-dflow
- Self-hosting overviewWhy self-host the dFlow control plane, core Compose components, and links to install guides.
- System requirementsCPU, RAM, storage, and software requirements for self-hosting the dFlow control plane.
- Installation optionsdFlow Cloud vs self-hosting the control plane, and how to pick an install path.
- Install with Docker / Docker ComposeRun the dFlow control plane from the official Compose stack: prerequisites, env files, and first boot.
- Environment configurationEnvironment variables and secrets for the self-hosted control plane (Compose, URLs, integrations).
- Tailscale and networkingPrivate networking for the self-hosted control plane, including Tailscale and access patterns.
- Control plane domains and SSLTLS certificates and hostnames for the self-hosted dashboard and Traefik (control plane).
- Email and outgoing servicesOutgoing email and related services for verification, notifications, and self-hosted dFlow.
- Upgrades and maintenanceUpgrading images and Compose stacks and routine maintenance for self-hosted dFlow.
- Backups and recoveryBacking up control-plane data (for example MongoDB) and recovery expectations when self-hosting.
- Self-hosting troubleshootingCommon control-plane failures when self-hosting dFlow and what to check next.
- Self-hosting FAQShort answers to frequent questions about operating self-hosted dFlow.