03
What is the same
Both deploy from Git or an image, keep releases you can roll back, run managed Postgres and schedule jobs. Both have a CLI and an MCP server.
04
Heroku concepts in dFlow
| On Heroku | On dFlow |
|---|
| Deploy from Git | dflow apps:build APP --repo URL |
|---|
| Deploy a container image | dflow apps:deploy APP --image IMAGE |
|---|
| Releases and rollback | dflow apps:releases:list APP · dflow apps:rollback APP --release ID |
|---|
| Heroku Postgres | dflow db:postgres:create · dflow db:link |
|---|
| Config vars | Env vars, plus write-only secrets for keys |
|---|
| Scheduler | dflow jobs:schedule |
|---|
| Logs | dflow apps:logs APP |
|---|
| Custom domains | dflow apps:route:set APP |
|---|
05
Move from Heroku to dFlow
- Request beta access and install the CLI.
- Build from your repo, or deploy your image.
- Create a Postgres database and link it to the app.
- Copy your data with standard Postgres tools. Get the connection details with
dflow db:credentials. - Set your env vars and secrets.
- Set the route, check the logs, then point your DNS to dFlow.