This is a long term feature request. Not a simple thing to implement and is basically a new product feature. I don't know if the team has thought of this or not. Regardless, I would love to at least get you thinking about it.

In insert large company name here, there is a common automatic staging pipeline workflow. Where you have multiple (in your case) environments and rules that allow you to push code and slowly deploy code. Things like dev → test → pre-prod → prod etc.

I envision this looking similar to how the Architecture works. It would be complex to set up, yes. But a really powerful tool. If done right, I see this fitting in really well with Railway.

Very, very simple examples of rules:

• passing a test suite moves it to the next stage

• don't move past this gate without manual approval

Different environments could also have different rules for failure. If a testing environment fails, who cares. But if prod fails - sirens. Notify everyone! (more specifically, let the user define what they want to do on an environment based level.) This also ties into better fine-grained control of what teams can do. For example, I only want to notify the infra people and not the programmers. (so +1 on more control over perms)

Environments, and how they are made, wouldn't require much, if any, change. The biggest thing about this, is some way to connect the various environments together. This could also let you have more fine-grained control of shared variables. Instead of only globally shared stuff, you can pass in a reference variable, very similarly to how it is done for services.

I am sure other members have other features they would request, in this pipeline. If anyone has any specific ideas of features / how it would work; please add them!