Why developers migrate
Railway bills by metered usage (CPU, RAM and network consumed per second), so the monthly invoice moves with traffic and can be hard to forecast. Square Cloud takes a different approach:- Predictable flat pricing in BRL — one plan price for RAM, vCPU and Blob storage, independent of how much traffic your app handles. See Plans and Pricing.
- Dedicated resources — RAM and vCPU are reserved for your application, not shared best-effort capacity.
- Deploy in seconds — upload a zip or push via CLI and your application is running.
Concept mapping
Migration steps
1
Create your configuration file
Replace Square Cloud’s Runtimes detect your language automatically from files like
railway.json/Nixpacks detection with a squarecloud.app file at the root of your project:squarecloud.app
package.json or requirements.txt, the same signals Nixpacks relies on. See the configuration file reference for every field.2
Set your environment variables
Recreate the variables from your Railway project’s Variables tab, either from the dashboard’s environment variables panel or by uploading a
.env file:3
Deploy
Upload your project via the CLI or the dashboard, in place of See How to Host your Website/API for a full walkthrough of both methods.
railway up:4
Migrate plugins to managed databases
If your project used a Railway Postgres, MySQL or Redis plugin, provision the equivalent Square Cloud managed database and point your app’s connection string at it.
5
Point your DNS
Once the app is live at Custom domains require an active Standard plan or higher.
<subdomain>.squareweb.app, point your domain’s DNS at Square Cloud and attach it from the CLI:Key differences to plan for
- Billing model. There is no per-second usage meter to watch — cost is fixed per plan regardless of traffic. Size your plan by RAM/vCPU need rather than projected usage. See Plans and Pricing.
- Region and latency. Square Cloud’s data center is located in New York — see the Platform Overview for infrastructure details. Measure latency from your user base before cutting over if you were running in a different Railway region.
- Databases move separately. Migrating a Railway Postgres/Redis plugin’s data means exporting it and restoring it into a new Square Cloud managed database — plan a maintenance window for the cutover.