I&#x27;m wondering what they&#x27;re doing that they&#x27;re estimating is 1 MB of data uploaded for data in, and 10 MB of data downloaded based off the following:<p>| We guess that such a client uses 1000 API calls per month (that&#x27;s editing only), requires therefore 1GB of data in, and needs about 10 GB of traffic-related data out.<p>I agree with Sgoettschkes regarding Heroku, I&#x27;ve been using it in production for over a year without any issues at all and found it to be the lowest level of entry for scaling apps.<p>For example, I just spun up some new analytics software I wrote last week in golang and it peaks around 50k req&#x2F;min, averages around 23k req&#x2F;min, I&#x27;m using 4 nodes which realistically could probably handle 100k req&#x2F;min without issue since in peak it&#x27;s consuming about 50% of available resources to us as it is right now, but $100&#x2F;mo is well worth it for the piece of mind, then combined with a $20&#x2F;mo percona mysql server on digitalocean that averages around 4% cpu load, we&#x27;re paying $120&#x2F;mo to handle on the low end 927,360,000 http requests&#x2F;month and all I have to do is a git push and the code automatically sets up the DB structure and DB indexes when booting the app up.<p>It&#x27;s cool that they&#x27;re using all these new technologies, but based on their numbers for me to have this software running on their setup it could realistically cost millions of dollars a month, and that&#x27;s still removing the costs of cloudfront and s3 since it&#x27;s not relevant in my case.  Maybe on paper meshing a bunch of AWS technologies that big named companies use sounds great, but it seems like a high price to pay for the ability to say you&#x27;re using these services.