Migrate from Railway to Layerbase
Move your Railway Postgres, MySQL, or Redis to a managed Layerbase database in one guided pass. Paste a token, pick a service, and we provision a matching database and copy the data. Read-once, your Railway service is never modified.
Why switch
Why teams leave Railway
Postgres, MySQL, or Redis: all three migrate
Paste one Railway token and we list every database service you run. Pick one and Layerbase provisions the matching engine, then copies the data across.
Databases as the product
Daily backups, a web console for every engine, database branching, TLS by default, and wake-on-connect. Purpose-built database hosting instead of a generic container.
Flat, predictable pricing
Postgres and Redis start on the Free tier, then $5/mo Solo or $15/mo Pro. No per-minute compute billing to reverse-engineer at the end of the month.
How it works
Four steps, one pass
- 1
Create a free account or sign in
Sign in with Google or GitHub. No credit card is needed to start, and the migration wizard opens with this platform already selected.
- 2
Connect your account
Paste a Railway account or team token (Account Settings, then Tokens). We list your Postgres, MySQL, and Redis services so you can pick one, and provision a matching Layerbase database. The source needs public networking enabled.
- 3
Pick what to migrate and name it
Choose what to bring over, give the new Layerbase database a name, and start the migration. Progress streams live in the dashboard.
- 4
We copy it in one pass
The migration reads from Railway once and never writes to it. Credentials are used for the copy and never stored. When it finishes, you land in your new database with a live TLS connection string.
Questions
Common Railway migration questions
Will my Railway service be modified?+
No. The migration is read-once: we connect, copy the schema and data, and disconnect. Your Railway service keeps running throughout.
What credentials do I need?+
A Railway account or team token (Account Settings, then Tokens). We use it once to list your Postgres, MySQL, and Redis services so you can pick one, and it is never stored.
Does my Railway database need to be reachable?+
Yes. The source service needs public networking enabled so the migration can connect to it. You can turn it back off after the copy finishes.
Which engine will my data land on?+
The matching one: Railway Postgres becomes Layerbase Postgres, MySQL becomes MySQL, and Redis becomes Redis (or Valkey if you prefer, since the two are wire-compatible).
Ready to leave Railway?
Sign in, and the migration wizard opens with Railway already selected. Your source is read once and never modified, so there is nothing to undo if you change your mind.