When to attach your own cluster
Start on the shared cluster. Attach a cluster you already run when those deploys should land there. dflow clusters:register stores the kubeconfig encrypted. MCP cannot register a cluster.
OWN CLUSTER
Start on our shared cluster. When you need your own, register it with one CLI command. Your deploy commands stay the same after that.
Start on the shared cluster. Attach a cluster you already run when those deploys should land there. dflow clusters:register stores the kubeconfig encrypted. MCP cannot register a cluster.
dFlow checks that it can create a namespace on your cluster. We store the kubeconfig encrypted.
New environments use your cluster first. You deploy with the same commands as before.
Cluster registration works from the CLI only. Your agent cannot register a cluster through MCP.
No cluster yet? An operator runs dflow-server cluster:create on a Linux machine. It installs k3s or kubeadm. The developer CLI does not install the cluster.
Yes. Register it with dflow clusters:register. We store the kubeconfig encrypted. This works from the CLI only. An operator installs k3s or kubeadm with dflow-server cluster:create.
No. You deploy with the dflow CLI or your coding agent. dFlow creates the Kubernetes parts. You need a kubeconfig only for your own cluster.
The beta is invite only. Tell us what you deploy and which agent you use. We reply by email.
Open to the first 100 users.
Invite only. Read the beta terms.