a year ago
Hi, I’m currently deploying my backend service on Railway, but I’m unsure whether I should deploy my frontend service here as well. Since frontend services typically consume a lot of bandwidth, I’ve noticed that Railway’s bandwidth pricing is about five times higher than Fly.io.
My frontend is currently deployed on Vercel, where it uses around 1TB of bandwidth per month.
Could you provide some guidance on whether it’s recommended to deploy my frontend service on Railway, or if there are better alternatives for high-bandwidth services? Any insights on managing bandwidth costs and limits would be greatly appreciated.
Thank you!
3 Replies
a year ago
Hi there, Yes you can absolutely deploy your frontend service here on Railway too!
You can use Railway's private networking to manage costs. https://docs.railway.com/maturity/use-cases#networking
Status changed to Awaiting User Response Railway • 12 months ago
unicodeveloper
Hi there, Yes you can absolutely deploy your frontend service here on Railway too!You can use Railway's private networking to manage costs. https://docs.railway.com/maturity/use-cases#networking
a year ago
1. Since the frontend application deals with external traffic, private-networking doesn’t seem applicable. Are there any other ways to optimize bandwidth costs?
2. Once the bandwidth reaches 100GB, what actions are needed on our part? Is there an automatic fee structure, or do we need to manually adjust it?
3. Currently, my website has 1TB of monthly traffic on Vercel. How is bandwidth calculated on Railway, and do they offer scaling options or other limits if traffic exceeds a certain amount?
Status changed to Awaiting Railway Response Railway • 12 months ago
a year ago
1.You can activate the "serverless" feature on your frontend app to save costs for times when traffic is little.
No actions needed on your part, we will adjust it and automatically keep serving you.
It's a fixed $0.10 per GB of Network egress. 1TB will be about $102 monthly. Here's the calculation https://docs.railway.com/reference/pricing/plans#resource-usage-pricing (check the Network egress section)
We also recommend you serve your static assets with a cdn like Cloudinary and add a Cloudflare cache to sit in front of your frontend app.
Status changed to Awaiting User Response Railway • 12 months ago
6 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 6 months ago