Railway to render.yaml converter
Paste a service's railway.json or railway.toml, and optionally its variables. You get a draft render.yaml that follows the Railway migration guide: the service becomes a web service, or a cron job when it has `cronSchedule`; `preDeployCommand` and `healthcheckPath` carry over; and references to Railway Postgres and Redis become new Bex datastores. Every gap is listed, and the render.yaml checker gives its verdict on the result.
Reads the documented `build` and `deploy` keys, including `builder`, `buildCommand`, `dockerfilePath`, `startCommand`, `preDeployCommand`, `cronSchedule`, `healthcheckPath`, `numReplicas` and `requiredMountPath`. `environments` overrides are listed, not merged. One file configures one service, so convert each service's file separately.
These tools run entirely in your browser. Nothing you paste or drop is uploaded, stored, or sent to analytics.
The service's railway.json or railway.toml. The format is detected.
Optional. `railway variables --kv` output. References such as `${{Postgres.DATABASE_URL}}` are wired to new datastores; secret values 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.