HOW IT WORKS

How dFlow deploys your app

Install the dflow CLI and point it at a GitHub repo, a local directory, or an image. We build and run the app on Kubernetes. dFlow keeps each release, so you can roll back.

01install02deploy03route + logs04rollbackFIG. 01 DeployFIG. 02 Rollback
01

The quickstart in five steps

$ curl -fsSL https://github.com/dflow-sh/dflow/releases/latest/download/install.sh | sh$ dflow login --email you@company.dev$ dflow projects:create web --environment prod$ dflow apps:create api$ dflow apps:build api --repo https://github.com/you/api$ dflow apps:route:set api$ dflow apps:logs api$ dflow apps:releases:list api$ dflow apps:rollback api --release rel_…

A local directory uses dflow apps:build api --path . instead of --repo. When the server configures a provider, sign-in can be dflow login --google or dflow login --github.

02

What a deploy waits for

A deploy is done when the pod is Ready for 12 seconds with no restarts. Until then, the release is not live.

03

Monorepos and pnpm workspaces

A pnpm workspace:* dependency has no special case in the build. The build clones a GitHub repo or packs a local directory.

04

Custom domains and DNS

Remove old A records for the domain. Add a CNAME to the platform hostname of your app. TLS goes from pending to ready without your help.

05

Deploy together on a call

Want help with your first deploy? Book a call, and we deploy it with you. Book a design-partner call →

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.