@webflorist, you’ll be in for a treat next week 
As for the second question, that might be worked on later, once after we have a dedicated free plan in place that’s robust enough.
First of all many thanks for the update!
But let me get this straight:
You will introduce Horror Bill protection for non-paying customers, while paying customers MIGHT get it sometime later?!
I’m sorry, but i’m pretty flabbergasted by this. I believe your company is still severly underestimating the importance of this feature for your current and potential customers. Having to explain an unexpected bill to a client even in the 100s - not even talking about 1.000s or 100.000s is the stuff of absolute nightmares. You are aready far behind your competition regarding this.
I must say, that this feedback will most definitely make Netlify a non-viable partner for us and our clients.
While not directly addressing this feature request, there’s some good news for anyone seeking to ensure they don’t incur any charges.
Netlify have released a new guaranteed ‘Free’ plan, where instead of being charged overages your site is suspended, (for the remainder of the calendar month), once any monthly limits are exhausted.
It’s effectively a ‘Starter’ plan without the risk of overages.
The forum announcement is here:
The blog announcement is here:
The various monthly limits can be viewed on the pricing page:
Auto kill-switch is now a part of our new plans: Pricing and Plans | Netlify. Quoting the FAQ:
What happens when a project reaches its credit limit?
When a site reaches its monthly usage limits, it enters a paused state until the start of the next billing cycle. We’ll notify you by email and in-app as you approach your limits at 50%, 75%, and 100% of usage. Please note that if one project exceeds its limits, all projects on your account will be paused.
You can re-enable your sites at any time by upgrading your plan. Your projects will automatically resume normal operation after upgrading.
Which sounds good on paper, but feels like “Netlify giveth and Netlify taketh away”, due to being facilitated by the natural behavior of a somewhat complex “Credit Based Pricing” system where every action consumes “an amount of credits”.
I found the best explanation for how it all works in the documentation:
We shipped two other helpful additions to all tiers including free plans:
Rate limiting for your functions and edge functions that you can write directly in the code base:
Helps you protect any expensive action from abuse.
Firewall rules: 2 custom firewall rules per project to block ip ranges, geo ranges, etc…
These together with the simple spend limiting build into the credit based pricing should really help control both cost and abuse.
More to come 