Self-hosting FAQ
Short answers to frequent questions about operating self-hosted dFlow.
Written By Zoro
Last updated 3 days ago
Do we self-host Worker Nodes too?
Often yes, but it is a separate decision. The control plane can run on Compose while Worker Nodes are other Linux servers or cloud instances. Teams still use Applications under Applications in the sidebar and Environments under Environments in the sidebar the same way as dFlow Cloud.
Is Compose the only supported install?
It is the reference path in this repository (docker-compose.yml, DOCKER.md). SELF_HOSTING.md documents a Dokku-oriented bootstrap for VM-focused teams. Kubernetes or other orchestrators are your port of the same containers and env vars.
Can we skip Tailscale?
If you do not use tailnet features, you may leave Tailscale variables unset only when your build and runtime validation allow it. Do not remove NET_ADMIN and /dev/net/tun unless you have tested the product without them.
Who patches MongoDB and Redis?
Operators do. Follow upstream security advisories and test upgrades against a staging Compose stack.
Where do custom app domains get configured?
In the dashboard for each Service, not on this host's Traefik alone. See Domains and SSL under Deployments and Operations in the sidebar.
How do upgrades roll out?
You pull new container images (or rebuild from git), run Compose, and validate the UI. See Upgrades and maintenance.
What is the fastest onboarding doc for mixed teams?
Quick start for Self-Hosted dFlow under Getting Started in the sidebar plus How dFlow is structured under Core Concepts in the sidebar.