💗 💗 💗 💗 💗 💗

So far I really love the platform, as a mid-technical level builder its easy enough for me to grasp and work with, but also provides enough flexibility to customize and optimize my deployments.

One thing i'm a little unsure of is expectations of cost scaling.

I have been building and deploying alot (probably more than an average developer because I'm not building locally right now as I moved my previous local setup to railway. I will likely be setting up a local build in the future, but did not have time yet. So that means i'm deploying (alot).

So far I reached my $5.00 usage credit pretty quickly. I'm just wondering is railway pretty expensive when moving starting to have public traffic inbound?

I have 0 public traffic on my application as we are in development right now, it's just me running deployments right now. Some are more resource intensive and I have since optimized my build system to allow for fast dev deploys and "full" deploys (which take over 15min each). I have not done too many big deploys, and now I will work with dev deployments which I hope will keep costs lower.

So i'm guessing my usage is down to extra processor consumption due to the high amount of deployments. Just wanted to confirm - how this plays out when compared to traffic/usage processing. Obviously you cant know about my application but it's a relatively simple fastapi.