3 ms·
> Inflicting that complexity on you all would help with margin control, but ugh. What we've done instead is set a blended price that fits most apps running on F
by dmw_ng 6y ago
> Inflicting that complexity on you all would help with margin control, but ugh. What we've done instead is set a blended price that fits most apps running on Fly.io, and decided to just eat the extra cost from outliers. If you want to exploit that, run an app in Sydney with a whole bunch of users in India. We'll lose money on your app and you will win one round of capitalism.
https://fly.io/blog/we-cut-bandwidth-prices-go-nuts/ https://fly.io/blog/we-cut-bandwidth-prices-go-nuts/
- everybodyknows 6y agoNice, but still one worry: A bug, or an attacker, sends outbound traffic through the roof, and newbie's fun experiment ends in a huge bill. More than one such story on HN recently (AWS). Skimming the pricing docs just now, I don't see protection against bandwidth overage: https://fly.io/docs/about/ https://fly.io/docs/about/
- ztcfegzgf 6y agohttps://community.fly.io/t/can-i-set-a-billing-limit-per-month/714 https://community.fly.io/t/can-i-set-a-billing-limit-per-mon...
- mrkurt 6y agoWe waive invoices when there's a mistake like this (we racked up a $20k Google bill a few years ago, we get it). We also work hard to keep bandwidth costs down. At $0.02/GB, even 2.5TB of traffic is ~$50. Which is why it's easy to forgive invoices.