Updated November 2026

LiveHQ vs Railway

Railway runs your code on its platform and holds the keys to your secrets. LiveHQ runs it on a server you own, and seals your secrets so only that server can read them. Here is the honest difference, sourced from Railway's own documentation.

Your servervsRailway

can decrypt your environment variables, including Railway's sealed ones

Includedvs$5,000/mo

for a sign-in wall in front of private apps (Railway's committed-spend tier)

Your VPSvsRailway's

infrastructure your code is built and run on

Side by side

Railway is a polished platform with a wider feature set. The difference that matters most is who holds the keys: to your secrets, and to the machine your code runs on.

QuestionRailwayLiveHQ
Who can decrypt your variablesRailway manages the encryption keys. Its docs say its systems “can decrypt any unsealed variable”, and that for sealed ones “Railway still decrypts it to run your service.” Unsealed values can be read back in the dashboard, the CLI and the API.Only your server. Your browser seals each value to your server's own key; LiveHQ stores the sealed value, refuses plaintext, and has no key to open it, not even for support.
Where code is built and runsOn Railway's infrastructure. After the October incident, builds moved from multi-tenant to single-tenant environments.On your own VPS, from any provider. No other customer's code is built or run there.
Private apps behind a sign-inRailway Authentication, launched October 2026, needs the $5,000/month committed-spend tier, admits only Railway project members, and doesn't cover TCP proxies.Every app starts private. Invite people by email, grant teams or guests, or set an app password, on every plan.
Databases and backupsPostgreSQL, MySQL, Redis and MongoDB templates. Scheduled volume backups, and point-in-time recovery for PostgreSQL (about 4 weeks) and MySQL (7 days).PostgreSQL 17 on your server with a browser SQL studio, and scheduled, encrypted off-site backups on Pro. No point-in-time recovery, MySQL or Redis yet.
Pricing modelHobby $5 or Pro $20 per workspace per month including that much usage, then $20 per vCPU-month, $10 per GB-month of RAM and $0.05 per GB of egress.You rent a flat-priced VPS from the provider you choose. Nothing on it is metered by the minute.
Scale and regionsFour regions (California, Virginia, Amsterdam, Singapore), replicas you set by hand, and vertical autoscaling.Wherever your VPS lives. Each app runs on one server; there are no replicas or autoscaling.
During a platform incidentIn October, new builds and deploys were paused for roughly a day and a half to two days, while running services stayed up.Your apps keep running on your server. Visitors reach them through LiveHQ's edge, so if the edge is down, they can't load your apps.

What October showed

Railway disclosed its incident within a day and has published updates since. Its own account shows why key ownership matters: the variables were encrypted, and the attacker decrypted them with credentials taken from inside the platform.

On LiveHQ, that last step has nothing to work with. No credential inside LiveHQ opens your variables, because the only key that does lives on your server.

How LiveHQ seals secrets
  1. Oct 20

    Railway detects a potential privilege escalation in its build infrastructure and halts builds.

  2. Oct 21

    The attacker pulls encrypted environment variables, obtains internal CI credentials, and decrypts a subset.

  3. Oct 21

    Railway notifies upstream providers, publishes a disclosure and asks every customer to rotate every variable.

  4. Oct 22

    Railway confirms the attacker is out. Up to about 1.85% of workspaces had variables potentially compromised.

  5. After

    Builders move to single-tenant environments and all keys are rolled twice. No final report as of November 1.

Switching from Railway

Five steps, almost all of them in your browser.

  1. 1

    Connect a server

    Rent a VPS from any provider (2 vCPUs and 4 GB is a comfortable start) and run the one-line installer from your console, in your own SSH session.

  2. 2

    Connect your repository

    LiveHQ builds with Railpack, Railway's own open-source builder, or with your Dockerfile, so most Railway projects build unchanged.

  3. 3

    Re-enter your variables, rotated

    Railway asked every customer to rotate everything anyway. Paste the new values into LiveHQ; they're sealed to your server as you save them.

  4. 4

    Move your database

    Create a PostgreSQL database, allow your IP to its TLS endpoint, and pg_restore your Railway dump to the connection URL LiveHQ shows you.

  5. 5

    Point your domain

    Add one CNAME. LiveHQ issues the certificate, and your new app goes live behind the edge, private until you share it.

Which one is right for you

Choose Railway if

  • You don't want to look after a server at all. On LiveHQ, your VPS's operating system updates are still yours.
  • You need cron jobs, volumes, Redis, MySQL, TCP services or several regions today.
  • You need replicas, point-in-time database recovery or SOC 2 reports today.
  • You want usage-based billing that can put idle services to sleep.

Choose LiveHQ if

  • You want your secrets readable only by your own server, not by your platform.
  • You want private apps with sign-in without an enterprise contract.
  • You want to own the machine your code and data live on, at a flat price.
  • You want a closed server: no inbound web ports, no IP in DNS, no SSH key held by anyone else.
Start free

Sources

Railway facts come from Railway's own blog, documentation and pricing pages, fetched on November 1, 2026. Railway's published timeline is preliminary; we will update this page when its final report appears.