This is what it cost us for @vercel @typesense @supabase from launch to 50k users in 10 days. I've debated running my own server route, but a voice in my head always told me, is that the best use of your time? It would be fun and I hate paying for low value services. Instead decided to wait post launch and see actual costs first. Here's the cost breakdown: ・Vercel: ~$177. The great news is that our traffic took a huge spike for a few hours and there is no way I could have sized that properly and Vercel just scaled up for us. The cost was a lot higher than I had modelled, our spending limit got hit as we busted through out function duration limit by a lot more than I'd predicted. Turns out it was a bug in our code and now that it's fixed the estimate for next month is $18. Two coffees. ・Typesense: $50. We have a 3-node fully HA setup and Typesense runs the most important screen in our app fully with 30-50ms response times through all the traffic spikes. As expected no surprises. I should pay them more for just being awesome. ・Supabase: ~$3k. This one is interesting. It's our db and stood up fine with no sweat... postgres is proven and the supabase team has nice socks! But it cost us a lot relatively. First, I oversized the instance too much to be safe for ~$1100 of spend, and downsized since. Lastly, our app is very media centric and that just completely killed our costs. We served up over 6T of total egress and 1.8% of that was app data, the rest media. We cache on device and downsample video on device to lower bitrate. While we can cutdown more, the egress and CDN transforms (resizing) was 90% of our supabase costs. Egress is always the hidden cloud killer cost, and pricing varies a lot per provider. I'll be looking to move our CDN and media streaming. In the end, our hosting costs are peanuts of what the 2 dev and 1 designer salaries. All providers stayed up and had our backs. We should always strive to have resource lean apps, but happy with the decision to not host my own for now. Happy building all.