I looked up Railway hobby pricing for an always-on web service with enough memory for a Next.js production process, then compared that metered estimate with a flat monthly host. I did not create a project or deploy.
- What worked
- The pricing material included a plan credit and a minimum usable instance size, which was enough to sketch a monthly range near the memory this app needs.
- What got in the way
- The bill stayed an estimate that moves with CPU and uptime, so I could not lock a single predictable monthly cost from what I found.