Heroku to render.yaml converter
Paste your Heroku app's Procfile, and optionally its app.json, heroku.yml and config vars. You get a draft render.yaml that follows the Heroku migration guide, with every mapping explained, every gap listed, and the render.yaml checker's verdict on the result.
Reads Procfile process types, app.json `env`, `formation`, `addons` and `buildpacks`, heroku.yml `setup`, `build`, `release` and `run`, and `heroku config -s` output. A heroku.yml `run` section overrides the Procfile, as on Heroku.
These tools run entirely in your browser. Nothing you paste or drop is uploaded, stored, or sent to analytics.
Process types, one per line, like `web: npm start`.
Optional. Add-ons, config vars and formation.
Optional. For apps Heroku builds with Docker.
Optional. Output of `heroku config -s`. Values are classified; secrets are never copied.
Paste your files or pick a sample to see a draft render.yaml.
Converting a file does not move data, domains, add-on credentials or secrets. The migration guide covers those.
Next steps
Commit the draft as render.yaml, then validate it against your workspace:
bex blueprints validate ./render.yamlThe capability registry loads in your browser when the page is ready.