8 months ago
I wanted to host a website with backend, frontend, and few other things.
I tried really hard to make everything work and this triggered a lot of cpu, memory and so the billing went up.
Then i let the finished working project "rest" with normal/zero usage from users for something like 15 days,
and now i don't really know how much it's going to cost to keep deployed, because I can only see monthly ranges of billing usage.
I'd like to exclude the setup part from the billing part, so i can understand, how much it really costs to keep it up.
How can i do that?
(in project i set N/A because it didn't show projects, just project parts, and this is not about a specific component, rather a whole project.)
8 Replies
8 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
8 months ago
Hey, the best way to estimate a cost is to perhaps run your services for a few days and check how much usage they are consuming each day, you can do this by checking how much each service is consuming in the usage dashboard. This will give you an idea of how much each service could potentially cost for an entire month, as opposed to the entire project's cost to the next billing cycle (this is what is shown in the UI). However, keep in mind that this can be influenced by many factors such as using serverless, spikes in traffic, etc. Furthermore, can you explain what you mean with the setup part?
uxuz
Hey, the best way to estimate a cost is to perhaps run your services for a few days and check how much usage they are consuming each day, you can do this by checking how much each service is consuming in the usage dashboard. This will give you an idea of how much each service could potentially cost for an entire month, as opposed to the entire project's cost to the next billing cycle (this is what is shown in the UI). However, keep in mind that this can be influenced by many factors such as using serverless, spikes in traffic, etc. Furthermore, can you explain what you mean with the setup part?
8 months ago
yes, that's what i also thought, i let the services run for like 20 days, but i don't remember the starting point anymore.
by the 'setup' part i mean all the time spent trying to make things work, i did a ton of deploys and that really used a lot of resources. i used like 2€ only on the first day if i don't remember incorrectly.
so, if i knew that the bill when i got a working build was x and now my bill is y, i'd do y - x and i'd know how much does it cost to keep it running for ~20 days
but i don't have x, and apparently there's no way to retrieve it.
8 months ago
The cost of running the service is low but the memory usage cost must be driving your price up
8 months ago
hi, you can pick a custom date range in the usage dashboard (top right) to see daily costs per service and even export the CSV. find the total on the day you finished setup (that’s your “x”), then subtract it from today’s total (“y”) to get the precise cost of keeping it running.
turborx
hi, you can pick a custom date range in the usage dashboard (top right) to see daily costs per service and even export the CSV. find the total on the day you finished setup (that’s your “x”), then subtract it from today’s total (“y”) to get the precise cost of keeping it running.
8 months ago
i can't really find what you are talking about. in the usage dashboard i can't see daily costs nor export a csv. would you help me find it?
8 months ago
hmm...
aleeeee1
i can't really find what you are talking about. in the usage dashboard i can't see daily costs nor export a csv. would you help me find it?
8 months ago
railway’s usage tab only shows cumulative totals and doesn’t offer daily breakdowns or a csv export. to get per‑day costs you can call the public graphql api’s estimatedUsage query, e.g.:
curl -X POST https://backboard.railway.app/graphql/v2 \
-H 'Authorization: Bearer <YOUR_TOKEN>' \
-H 'Content-Type: application/json' \
-d '{"query":"query { project(id: \"<PROJECT_ID>\") { estimatedUsage { edges { node { date totalCost } } } } }"}'
this will return date and totalCost for each day, so you can subtract x from y to find your exact usage cost.