OWN CLUSTER

Attach your own Kubernetes 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.

appsharedyoursdflowkubeconfig · encrypted
01

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.

02

Register your cluster

$ dflow clusters:register --name NAME --region REGION --kubeconfig PATH

03

What dFlow checks

dFlow checks that it can create a namespace on your cluster. We store the kubeconfig encrypted.

04

Deploys after you attach

New environments use your cluster first. You deploy with the same commands as before.

05

Limits today

Cluster registration works from the CLI only. Your agent cannot register a cluster through MCP.

06

Set up a cluster on a VPS

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.

07

FAQ

Can I use my own 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.

Do I need to know Kubernetes?

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.

Get a beta invite.

The beta is invite only. Tell us what you deploy and which agent you use. We reply by email.

Join the beta

Open to the first 100 users.

Book a design-partner call

Invite only. Read the beta terms.