3 months ago
Hello Railway Team,
My estimations this month look inconsistent.
In previous months, my database estimate was around $13, and this month it dropped to $5.
Meanwhile, my Next.js SSR landing page suddenly jumped to around $9, which is much higher than expected.
Yet the total estimated cost still ends up around $30, very close to previous months.
Is there an algorithm that adjusts or balances estimations to always match around $30/month?
My main issue: why is the Next.js SSR landing page costing this much?
It’s only a simple landing page with SSR and very low usage, so this increase doesn’t make sense.
I always have issues understanding how the project usage system calculates these numbers, and why there is this imbalance.
Please clarify why the landing page cost is so high.
4 Replies
3 months ago
Estimated costs look correct. 1 GB of memory 24/7 = 10$ every month
3 months ago
also, math looks correct based off what youre using, https://docs.railway.com/reference/pricing/plans#resource-usage-pricing and total estimate
Yes, I understand the calculation itself is correct — 1 GB 24/7 = $10.
But on your side, it seems that a simple Next.js SSR project consumes a lot more resources than expected. Even with very low traffic, the landing page is using enough resources to push the estimate close to $9.
So my issue isn’t the pricing formula — it’s why such a small SSR landing page is using that much memory on Railway, and why these usage numbers fluctuate so much from month to month even though nothing changed in my setup.
3 months ago
its all really based off your usage, if one month your website has higher traffic, youll incurr higher costs, higher memory, higher egress fees. if another month you have no traffic, itll cost next to nothing. there are ways to optimize your SSR project if youre concerned about costs, or setting a hard limit so you prevent it from happening