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

Updated November 2026
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
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.
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 secretsRailway detects a potential privilege escalation in its build infrastructure and halts builds.
The attacker pulls encrypted environment variables, obtains internal CI credentials, and decrypts a subset.
Railway notifies upstream providers, publishes a disclosure and asks every customer to rotate every variable.
Railway confirms the attacker is out. Up to about 1.85% of workspaces had variables potentially compromised.
Builders move to single-tenant environments and all keys are rolled twice. No final report as of November 1.
Five steps, almost all of them in your browser.
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.
LiveHQ builds with Railpack, Railway's own open-source builder, or with your Dockerfile, so most Railway projects build unchanged.
Railway asked every customer to rotate everything anyway. Paste the new values into LiveHQ; they're sealed to your server as you save them.
Create a PostgreSQL database, allow your IP to its TLS endpoint, and pg_restore your Railway dump to the connection URL LiveHQ shows you.
Add one CNAME. LiveHQ issues the certificate, and your new app goes live behind the edge, private until you share it.
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.