You can fully stop a service by removing its deployment: go to the service's Deployments tab, click the three-dot menu on the active deployment, and select "Remove," which stops it entirely and prevents any further usage. If you want the service to automatically stop when idle and restart when it receives traffic, you can enable Serverless in the service's settings under Deploy. You can also use the CLI command railway down to remove the latest deployment.

No I need it I dont want to remove it, I just want it to stop when idle and the start it again when I need it, what is the easiest way to do that

To enable Serverless, click on your service, go to Settings, scroll to the Deploy section, and toggle Enable Serverless - your service will then automatically sleep after 10 minutes of no outbound traffic and wake up when it receives a new request. Note that if your service maintains active database connections or sends any outbound requests (like telemetry), it may not sleep as expected. More details are in our Serverless docs.

ON Postgres service, clicking the three dots and remove the deployment stop the instance but does not delete it right, and for rapidalert service i can work with serverless

waiting

Yes, that's correct. Removing the Postgres deployment stops it and stops CPU/memory charges, but does not delete the service or its volume data. You can redeploy later and your data will still be there.

So your setup would be:

• rapidalert: Enable serverless — auto-sleeps when idle, wakes on requests
• Postgres: Remove deployment when not in use, redeploy when you need it

One note: volume storage is still billed at $0.15/GB/month even with the deployment removed, but for a small database this is very minimal.