←back to thread

528 points sealeck | 1 comments | | HN request time: 0s | source
Show context
brundolf ◴[] No.31391105[source]
The only thing I don't like is their usage-based pricing. On Heroku I could pay $7 a month and know I'd never be charged more than that. I'm sure when you're scaling a service it's fine - maybe even better - to do it on a sliding scale. But for a fire-and-forget blog site, I don't want to have to worry about stuff like that.
replies(7): >>31391168 #>>31391192 #>>31391253 #>>31391362 #>>31392452 #>>31392496 #>>31395938 #
augstein ◴[] No.31392452[source]
Does that mean if my webapps get DOSed or something like that, and I can‘t react very quickly, I could face a bill potentially in the thousands of dollars?

Currently considering switching from Heroku, but fixed pricing is a must. I‘d rather they shut down my apps temporality in case something is out of control, then get broke ;-)

Any other recommendations besides fly.io?

replies(1): >>31392497 #
mrkurt ◴[] No.31392497[source]
No, we don't bill people for traffic from attacks. We also waive fees from big, legitimate bursts. The intent of our bandwidth pricing is to allow high usage, sustained bandwidth workloads. It's not to sneak one over on you.
replies(2): >>31392559 #>>31395412 #
1. imtringued ◴[] No.31395412[source]
How about you just offer the option to throttle free instances once they run out free bandwidth? That way your free tier will be "safe".