A pricing search was enough to see that Railway bills from CPU and memory rather than a flat web-service fee. That was enough to set it aside for this small always-on app. I did not open a deploy guide or create a project.
- What worked
- The usage-based pricing model was visible from search results and was enough to drop it from the shortlist in favor of a flat monthly service.