Bring Your Own Cloud

a year ago

This post is part of Railway's 2024 product roadmap kickoff, the Railway team spends the first week every three months sharing our thought process and concepts of what we plan to build.

Project cheerleader: Jon Kingsley/Jake Cooper

Railway is racking and stacking our own servers as we speak and deploying to Railway as a compute target isn't changing anytime soon.

But many companies we have spoken to have existing public cloud (AWS/GCP/Azure/Oracle/Hertzer/homelab Raspberry Pi) footprints that they would like Railway to be aware of to manage. (Or at least bridge via network)

When talking to developers, Own Cloud means a variety of different realities to people and ops teams. This is a catch all feedback post for people to provide what they would like Railway to manage, how integration should work, and general questions.

This is something we have been working towards for years now and it's something we are really excited about- can't wait for your feedback!

2 Replies

a year ago

It would be amazing if we could use railway as the orchestration layer for the other cloud providers. Logging, networking, environment variables, dns etc. Having a platform that allows multi cloud is desperately missing in the market (having a frontend app in aws and having a backend service in digitalocean).

I know the above is blue sky but thinking how Railway could become the defacto platform for running all and any applications.


a year ago

Blue sky is exactly our goal, if you don't mind me asking, what is your current footprint on those platforms? What would you like to become managed first?


Bring Your Own Cloud - Railway Help Station