Migrate from Railway, Render, or Heroku

Move Postgres databases and container services to Scalix Cloud

Why teams move

Predictable pricing with a published calculator — per-unit rates are public; the pricing page computes your stack live. No surprise bills: overage is opt-in with a hard cap you set.
EU data residency by default, on hardware we operate.
Scale-to-zero on databases and services — side projects cost near-nothing at idle.

Railway/Render have polished multi-region options today; Scalix regions are expanding (EU live, India next). If you need us-west p99s right now, we're not there yet.
Heroku-style buildpacks: Scalix Builder auto-detects Node/Python/Go/Rust with nixpacks — most Procfile apps port with zero config, but exotic buildpacks may need a Dockerfile.

All three expose a Postgres URL:

bash

scalix-cloud migrate db import --source "$DATABASE_URL"

Deploy from source (runtime auto-detected) or bring the image:

bash

scalix-cloud deploy ./my-app                 # build + deploy from source
# or
scalix-cloud run deploy --name api --image registry/img:v1 --port 8080

Revisions, rollback, health checks, and concurrency autoscaling are built in — scalix-cloud run rollback api works on day one.

bash

scalix-cloud cron create job "0 * * * *" --action-type function --config '{"function_id":"<fn-id>"}'

Long-running workers deploy as Run services with --min-instances 1.

Questions mid-move? migrate@scalix.world — a founder answers.