N/A

If you didn't have any running deployments then it is possible you had a volume that consumed disk usage over time, which would also explain how it lasted 4 months

Hi Fragly. If by "volume" do you mean large files, I don't think that's the case. But I think the deployments were running until now. I had assumed no credits would be consumed if there were no calls to the APIs, but could it be that simply having them deployed has consumed my credits?

oh yes, if they were running then that is definitely what used up your credits, you're charged for memory consumption as well so even if the service gets no API request, it'll still consume idle memory usage which would drain your credits

and by volume I mean static file storage basically

right, thanks @Fragly

so I guess it's a good idea to stop or pause the deployments when I'm not testing them, right? (also with my new Hobby plan)

Yea, that is a good idea

Although the first 5 dollars of usage is free on hobby plan so if your services stay below 5 dollars total cost then you wouldn't need to bother removing deployments

Another thing that's worth noting is you can use app sleeping which puts your app in a "sleep" state until it receives requests, which would definitely be helpful if you're trying to save costs

Thanks for the tip, that sounds helpful, I'll try the "sleeping" state.

Awesome, you can find it in service settings

awesome!

Would you mind pointing me to the relevant documentation about costs involved by the files stored or the API traffic?

static file storage costs are $0.25 per GB (you can see information about resource pricing on this page )

although that only applies if you have a [Volume]() attached to your service and you are deliberately storing files in that volume

If you don't have a volume attached then everything is stored in ephemeral storage which is free, but does reset when your service restarts or redeploys

Regarding API traffic, Railway charges $0.1 per GB egress, you can see that on the pricing page too

thanks a lot, @Fragly I was checking the right place then, I thought there would be more detailed info. awesome, that helps

Of course, happy I could help 🙂

I've marked the chat as "solved", not sure if that's necessary 🙂

(as if this was a ticket of sorts)

Don't worry we have internal tooling for that

Thanks a lot for your prompt help, enjoy your day!

Thank you, you too 🫡

!s