I'm going to be another person to recommend Fly.io. It's phenomenal: The pricing is good, the UX is good, everything just works. The GitHub action is a bit simplistic but it's more than easy enough to just make your own action that runs flyctl. The only real issue I have with it right now is there's no API token system, you need to give CI access to everything you can.
The one reason I'll stay with Railway over Fly is that Fly is not as flexible with diverging CPU/memory requirements. I have a few apps that are memory heavy but don't need a lot of CPU. My Railway bill reflects that, with almost no CPU charge. And I don't have to think about upgrading or downgrading my instance size at all.
If they manage to implement that, they'd be the ideal replacement.
Comments
I'm going to be another person to recommend Fly.io. It's phenomenal: The pricing is good, the UX is good, everything just works. The GitHub action is a bit simplistic but it's more than easy enough to just make your own action that runs flyctl. The only real issue I have with it right now is there's no API token system, you need to give CI access to everything you can.
The one reason I'll stay with Railway over Fly is that Fly is not as flexible with diverging CPU/memory requirements. I have a few apps that are memory heavy but don't need a lot of CPU. My Railway bill reflects that, with almost no CPU charge. And I don't have to think about upgrading or downgrading my instance size at all.
If they manage to implement that, they'd be the ideal replacement.