If you remove the latest deployment you should be able to replicate this behavior, though it's more of a workaround

Why do you need this? Could you perhaps interface diretly with the Railway API?

"Remove" seems like the wrong word to use here.

I wish you could "Inactivate" or something like that

That is essentially removing

Lets agree to disagree

What's the difference in your eyes?

thanks though

remove = physically remove and never come back, inactivate = stop it but its still there and can be re-activated at another point

That is what remove means in context of Railway

You remove the latest deployment and then redeploy whenever you like

No data as lost as long as you properly use volumes

i understand but i'm expressing my opinion that a better word could be used. nothing more.

!s