AW3 - Multi-Cloud Hosting Platform
    Migrate · Render → Railway

    Migrate from Render to Railway
    using your render.yaml.

    Railway's import reads Render Blueprints directly, which makes this one of the simpler platform moves. The data is the part that needs care.

    Facts checked against each provider's own pages

    The short answer

    Import the GitHub repository into Railway: it detects render.yaml and provisions the services, databases, cron jobs and workers defined there, including their environment variables[1]. Then move Postgres with pg_dump and psql, copy disk data into Railway volumes, add custom domains with both the CNAME and TXT records Railway shows[2], and shift traffic.

    Mapping

    What maps to what

    On RenderOn RailwayNotes
    render.yaml BlueprintRailway project (imported)Railway auto-detects render.yaml on GitHub import[1].
    Web service / worker / cron jobRailway servicesDeploy from repo, Dockerfile or image[1].
    Render PostgresRailway PostgreSQLMove with pg_dump and psql[1]; Railway also offers MySQL, Redis and MongoDB[3].
    Render Key ValueRailway RedisOne-click Redis[3].
    Persistent diskRailway volume$0.15/GB/month; Hobby up to 5 GB, Pro up to 1 TB[4].
    Environment groups / .envService Variables (RAW Editor)Paste a .env or JSON into the RAW Editor[5].
    Regions: Oregon, Ohio, Virginia, Frankfurt, SingaporeUS West, US East, EU West, Southeast AsiaRender lists 5 regions[6]; Railway lists 4[7].
    Steps

    The migration, step by step

    1. 01

      Import the repository

      Create a Railway project from the GitHub repo. Railway detects render.yaml and sets up services, databases, crons and workers, importing environment variables defined in the file[1]. Variables set only in Render's dashboard need to be added by hand.

    2. 02

      Export the database

      On a paid Render Postgres plan you can create a logical export from the dashboard (kept 7 days) and restore it with pg_restore --format=directory. Render doesn't create logical backups for free databases, so run pg_dump yourself[8].

    3. 03

      Restore into Railway

      Load the dump into Railway PostgreSQL with psql (or pg_restore) and update DATABASE_URL on the services that use it[1].

    4. 04

      Copy disk data

      Render's disks page documents daily snapshots for restoring on Render but no export tool[9], so copy files out from the running service. Attach a Railway volume and upload data with the Railway CLI[4].

    5. 05

      Add custom domains

      In Railway, go to Settings → Public Networking → Custom Domain and add both the CNAME and the TXT verification record it shows[2].

    Gotchas

    Things the docs warn about

    • Render doesn't create logical backups for databases on the Free plan; take your own pg_dump[8].
    • Railway's railway.json / railway.toml is deprecated and stops being read on 1 December 2026; new projects should use .railway/railway.ts[10].
    • Railway volume size depends on plan: Hobby up to 5 GB, Pro up to 1 TB[4].
    • Changing the region of a Railway service with a volume requires a volume migration and causes downtime[7], so choose the region before you load data.
    • Railway bills egress at $0.05/GB with no separate allowance[11]; Render included 5 GB to 1 TB per workspace depending on plan[12].
    Where AW3 Host fits

    Run both during cutover, then switch

    AW3 Host connects both your Render and Railway accounts, so the old and new deployments run side by side from one dashboard and API instead of a big-bang switch.

    Weighted routing sends a small share of traffic to Railway first (for example 5%, then 25%, 50% and 100%) while Render serves the rest. Health checks every 60 seconds watch both; if the Railway side fails, failover moves traffic back automatically, and rollback to the previous release is one step. Daily cost sync shows what each provider costs during the overlap, and budget policies alert you if the double-running period gets expensive. Secrets for both are stored encrypted per environment.

    When Railway has carried all traffic cleanly for long enough that you no longer need the fallback, point DNS at it for good and decommission Render.

    Reference

    Render vs Railway at a glance

    Render vs Railway at a glance
    RenderRailway
    CategoryApp platform (PaaS)App platform (PaaS)
    Pricing modelWorkspace plan plus per-service compute (prorated to the second) and metered bandwidth and build minutes[13]Plan fee that counts toward usage, plus per-resource usage (RAM, CPU, egress, volumes)[11]
    Compute billing granularityCompute prorated to the second[13]Per second: $0.00000386 per GB-second of memory, $0.00000772 per vCPU-second[16]
    Internet egress (first paid tier)$0.15/GB over the included amount[12]$0.05/GB, all regions and plans[11]
    Regions / locations5 regions: Oregon, Ohio, Virginia, Frankfurt, Singapore (counted from list)[6]4 regions: US West, US East, EU West, Southeast Asia (counted from list)[7]
    Deploy modelGit-backed auto-deploys with native runtimes, Dockerfile builds, or a prebuilt image from a registry[14]GitHub repo, Dockerfile, Docker image, or railway up from the CLI[1]
    Persistent volumesYes: persistent disks for paid services at $0.25/GB/mo; a service with a disk can't scale to multiple instances[9]Yes: volumes at $0.15/GB/mo; Hobby up to 5 GB, Pro up to 1 TB[4]
    Config filerender.yaml (Blueprint)[15]railway.json / railway.toml are deprecated (stop being read 2026-12-01); replacement is .railway/railway.ts[10]
    FAQ

    Frequently asked questions

    Can Railway import a render.yaml?
    Yes. Railway's Render migration guide says it detects render.yaml on GitHub import and provisions the services, databases, cron jobs and workers defined in it, importing the environment variables the file defines.
    How do I export a Render Postgres database?
    Paid plans can create a logical export from the dashboard, kept for 7 days, and restore it with pg_restore --format=directory. Free databases have no logical backups, so use pg_dump yourself.
    Which Railway region matches Render's?
    By geography, Render's Oregon, Virginia or Ohio, Frankfurt and Singapore regions are closest to Railway's US West (California), US East (Virginia), EU West (Amsterdam) and Southeast Asia (Singapore) regions.
    Sources

    Sources

    1. Railway Docs: Migrate from Render. https://docs.railway.com/platform/migrate-from-render (checked 2026-11-16)
    2. Railway Docs: Working with domains. https://docs.railway.com/networking/domains/working-with-domains (checked 2026-11-16)
    3. Railway Docs: PostgreSQL. https://docs.railway.com/databases/postgresql (checked 2026-11-16)
    4. Railway Docs: Volumes. https://docs.railway.com/volumes (checked 2026-11-16)
    5. Railway Docs: Variables. https://docs.railway.com/variables (checked 2026-11-16)
    6. Render Docs: Regions. https://render.com/docs/regions (checked 2026-11-16)
    7. Railway Docs: Regions. https://docs.railway.com/deployments/regions (checked 2026-11-16)
    8. Render Docs: Postgres backups. https://render.com/docs/postgresql-backups (checked 2026-11-16)
    9. Render Docs: Persistent disks. https://render.com/docs/disks (checked 2026-11-16)
    10. Railway Docs: Config as code. https://docs.railway.com/config-as-code (checked 2026-11-16)
    11. Railway Docs: Plans. https://docs.railway.com/reference/pricing/plans (checked 2026-11-16)
    12. Render Docs: Outbound bandwidth. https://render.com/docs/outbound-bandwidth (checked 2026-11-16)
    13. Render: Pricing. https://render.com/pricing (checked 2026-11-16)
    14. Render Docs: Deploys. https://render.com/docs/deploys (checked 2026-11-16)
    15. Render Docs: Blueprint spec. https://render.com/docs/blueprint-spec (checked 2026-11-16)
    16. Railway: Pricing. https://railway.com/pricing (checked 2026-11-16)
    Public beta

    Your next deploy
    goes everywhere.

    Connect a provider, point a service at it, and ship. Add the second provider when you're ready.

    No card needed · Free tier · Pay as you go after that