Fly.io to render.yaml converter
Paste your app's fly.toml, and optionally the names of its secrets. You get a draft render.yaml that follows the Fly.io migration guide: process groups become web, worker or private services, `release_command` becomes `preDeployCommand`, HTTP checks become `healthCheckPath`, and a mount becomes a disk. Every gap is listed, and the render.yaml checker gives its verdict on the result.
Reads `app`, `[build]`, `[deploy]`, `[env]`, `[processes]`, `[http_service]`, `[[services]]`, `[checks]`, `[[mounts]]`, `[[vm]]`, `[[statics]]` and `[[restart]]`, plus `fly secrets list` output or `.env` lines. Only secret names are kept; values and digests never reach the draft. Regions, machine sizes and statics are explained, not mapped.
These tools run entirely in your browser. Nothing you paste or drop is uploaded, stored, or sent to analytics.
The app's fly.toml.
Optional. `fly secrets list` output or `.env` lines. Only the names are used: each becomes a secret you enter in the dashboard.
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.