Integrations · Host

Pagerless for Railway

Woken only when it matters, and one tap undoes a bad deploy: Pagerless rolls back to the previous deployment.

Set up

Node: import "pagerless/auto". Go: pagerless.Middleware. The service name and release are read from Railway's variables.

Store the key with railway variables --set "PAGERLESS_KEY=pl_live_...". Or run npx pagerless connect and it finds your services and places the key for you.

Fixes on Railway

What Pagerless can do on Railway
FixOn Railway
Undo the updateRolls back to the previous deployment
RestartRestarts the deployment
Add capacityAdds replicas
Deploy eventsYes: errors right after a deploy are tied to it
Access it needsa Railway API token

Questions

Can Pagerless roll back Railway automatically?

Yes, if your rules set undo to alone. By default it asks first, and approving an undo needs your passkey (Face ID or Touch ID). It then rolls back to the previous deployment.

Does Pagerless need admin access to Railway?

It needs a Railway API token. It is stored encrypted and used only for the fixes listed above. You can skip it: alerts work without it.

Updated .

Free for you and one backup · 3 apps · no card

Sleep through the small stuff.

Run one command in your repo. Pagerless shows every change before it makes it.

npx pagerless connect