We're spending nearly $1000/mo in bandwidth charges on Netlify for serving totally static text files and a few images, which is absurd. I'm considering switching away from them outright. We can use `make` to run our own build, and CDNs are easy enough.
The fact that they charge per contributor when we already pay a lot is insult to injury.
I guess they're either trying to juice harder for a raise or slow losses to avoid other cuts. Whatever the case, I'm not very satisfied. I don't need the platform that badly, and we're definitely not locked in.
How many people you are serving those static files and images to and how much bandwidth does that consume. The fact that they are static sites reveals little about whether the charges are absurd.
Netlify doesn't make it easy to know this. Looking at my historical bills, they're littered with:
1 Extra Bandwidth $55.00
1 Extra Bandwidth $55.00
1 Extra Bandwidth $55.00
1 Extra Bandwidth $55.00
2 Extra Bandwidth $110.00
1 Extra Bandwidth $55.00
1 Extra Bandwidth $55.00
1 Extra Bandwidth $55.00
1 Extra Bandwidth $55.00
2 Extra Bandwidth $110.00
1 Extra Bandwidth $55.00
2 Extra Bandwidth $110.00
...
For a single billing cycle. No cumulative totals.
I can only see the current month's bandwidth expenditures.
Cloudfront and similar CDNs charge peanuts compared to this.
We're spending nearly $1000/mo in bandwidth charges on Netlify for serving totally static text files and a few images, which is absurd. I'm considering switching away from them outright. We can use `make` to run our own build, and CDNs are easy enough.
The fact that they charge per contributor when we already pay a lot is insult to injury.
I guess they're either trying to juice harder for a raise or slow losses to avoid other cuts. Whatever the case, I'm not very satisfied. I don't need the platform that badly, and we're definitely not locked in.
I'm going to file a ticket so I don't forget.