Managed Postgres
Postgres 16, 17 or 18. Back it up on demand, and restore.
db:postgres:create · db:backups:create
Status: BETA · INVITE ONLY
Deploy to Kubernetes from the dflow CLI or your coding agent. We do the cluster work. You can roll back any release.
Open to the first 100 users.
$curl -fsSL https://github.com/dflow-sh/dflow/releases/latest/download/install.sh | shInvite only. We verify your email before your first deploy.
01The problem
You wanted to deploy an app. Now you own YAML, ingress, certs, CI and a pager. The cluster became the product. We think that work is our job, not yours.
02How it works
One script installs the CLI. dflow upgrade gets each new version.
Point dFlow at a container image. dFlow deploys it to the cluster.
Get a hostname with automatic TLS. Then read the pod logs.
dFlow keeps your releases. Roll back to an earlier one.
Every step is in the docs. Read the quickstart →
03Agents deploy too
Connect your agent through hosted MCP or skills. Then ask it to deploy. For a delete or a restore, it must name the target.
A deploy fails at 3 AM. Your agent reads the errors. Should it roll back on its own? First, it must know how to undo the change.
Destructive actions require explicit confirmation.
04EXAMPLE SESSION
Six commands take an app from an image to a rollback.
The agent must type the name before a restore. No name, no restore.
One command teaches your agent how dFlow works.
05What's in the box
Postgres 16, 17 or 18. Back it up on demand, and restore.
db:postgres:create · db:backups:create
Storage for apps that must keep their files.
volumes:create
Create jobs or schedule them. Read their logs.
jobs:schedule
A platform hostname, up to 10 custom domains and automatic TLS.
apps:route:set
You set a secret. Nobody can read it back.
Install umami or hasura. More templates are in development.
templates:install
06Bring your own cluster
Start on our shared cluster. Need more control? Register your own Kubernetes cluster. Your deploy commands stay the same. We store the kubeconfig encrypted.
Cluster registration works from the CLI only, not MCP.
07Trust
07·1Compliance
Status as stated on the dFlow trust center, which covers dFlow Cloud (app.dflow.sh).
Compliance on the trust page →Open the trust center ↗
The published trust center describes dFlow Cloud. This site is the new control plane; its security notes are on /security/ and /trust/.
08Live today vs in development
@dflow-sh/mcp npm packageIN DEVELOPMENTWe record each change in the public changelog. Read the changelog →
09Compare
dFlow sits where three needs meet: CLI deploys, safe agent actions and your own cluster. Each compare page lists its sources.
The beta is invite only. Tell us what you deploy and which agent you use. We reply by email.
Not wired yet. This preview has no backend, so nothing was sent.
Open to the first 100 users.
Invite only. Read the beta terms.
FAQ
No, not yet. dFlow is in an invite-only beta. The product can change, and we offer no SLA. Read the beta terms first.
Pricing isn't set yet. The beta is invite only. The pricing page shows the beta limits for each workspace.
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.
Only with explicit confirmation. A database restore needs confirm_name. A route delete needs confirm_host. Other destructive actions need a confirmation argument too.
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.
dFlow is CLI-first and agent-safe, on Kubernetes. Railway also offers agent tooling. Our focus is safe agent actions, rollback and your own cluster. See the compare pages.