Railway at least for me changed to an hourly limit of 750 hours I think per container about a month ago could be different for different users. I never really used it so correct me if I'm wrong.
Actually! Funny thing, I did! The article was getting long so I ended up making some cuts. Originally, I had it listed as an honorable mention because while they did have a free tier, it required a credit card:
"Fly's free tier requires a credit card but does include 2,340 hours of computing each month, up to 3 shared CPUs, and no inactivity timeouts.
Though an evidently powerful platform, with the need to install their CLI and use Docker to access its features, Fly wasn't ideally suited for this specific test case. While sadly this meant that I was unable to successfully measure deployment performance from a Github template, it has left me very interested in exploring other testing scenarios and projects where it might be a better fit."
