Skip to main content

​
What you get on Square Cloud

  • Predictable flat pricing in BRL: one monthly plan price for the RAM and vCPU your applications use, independent of how much traffic they handle. See Plans and Pricing.
  • Dedicated resources: RAM and vCPU are reserved for your applications.
  • 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 railway.json/Nixpacks detection with a squarecloud.app file at the root of your project:
squarecloud.app
Square Cloud’s Runtimes detect your language automatically from the extension of your MAIN file and check its dependency file, such as package.json or requirements.txt. A web service must listen on host 0.0.0.0 and on the port in PORT (80). 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:
Then restart the application: it reads environment variables when it starts. See Environment variables.
3

Deploy

Upload your project via the CLI or the dashboard, in place of railway up:
See How to Host your Website/API for a full walkthrough of both methods.
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 <subdomain>.squareweb.app, point your domain’s DNS at Square Cloud and attach it from the CLI:
Custom domains require an active Standard plan or higher. For the DNS records, see how to set up your own domain in the help center.

​
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.

​
Next steps

Configuration file

Every field of the file that replaces railway.json.

Environment variables

Move your variables and keep secrets out of your code.

Managed database

Create the database that replaces your Railway plugin.

​
Contact us

If you continue facing technical difficulties, our specialized support team is available to assist you. Contact us and we’ll be happy to help you resolve any issue: support quality is a big part of why developers rate Square Cloud 4.9/5 across 402 reviews on Google and Trustpilot.