HN Explorer

Tell HN: Netlify changing Starter plan

25 points by HarveyKandola ↗ HN
In a nutshell..

In 30 days, our Starter plan will require that GitHub repositories connected to your Netlify account are either linked to Personal GitHub accounts or set for public visibility. If you have repositories using an Organization-owned GitHub account set to private visibility, you will need to move to the Netlify Pro plan or above.

11 comments

[ 2.9 ms ] story [ 38.7 ms ] thread
datene
It's not unreasonable, however 30 days seems a bit on the short side. I have 15+ repos that I'll need to review. Another thing that would be nice is if the affected sites would be tagged in the Netlify dashboard or mentioned in the email. That would make the review process a bit easier
fabian_shipamax
I don't think 30 days are reasonable and our costs would go up 150x! On top of having regular outages over the last six months. Not going to happen. I'm out.
hoofhearted
I'm guessing this is why my question about Netlify got downvoted the other day on another post. I was intrigued by the CMS feature, but I am rethinking that now.
mtmail
Pro plan is $19/month (https://www.netlify.com/pricing/). As a business we have 5 static websites with them. It's reasonable and we will upgrade without looking around. The feature that brought us to Netlify was being able to set additional HTTP headers (via a configuration file). We don't use or need any of the other pro features (extra build minutes, more bandwidth). To us it was clear the free plan we used wouldn't last.
ValentineC
I just wish there was an option for smaller businesses/non-profits that wasn't charged per-seat.

I'm moving quite a few websites for the various non-profits I'm involved in to Cloudflare — mainly because it's free to add team members there.

mr_cyborg
I host several sites on Netlify and will likely move the one that doesn’t qualify for free tier over to another provider.

I like their service but I paid for analytics for a while through them and didn’t find it worthwhile, so I will probably not want to pay for the one site that needs it when I can host elsewhere for cheaper now.

Sytten
I always found the pricing per seat to be weird for a CDN, we will move our stuff to render.com as it offers the same basic features for much cheaper.
thetwopct
I’ll be moving my admittedly small projects to CloudFlare Pages. I find it slightly disingenuous that Netlify still promote the free plan on their website without mentioning the public git requirement.
clouder
Its 100% fair wanting companies to pay however the notice isn't enough. I just use Netlify for a basic landing page to link to my linkedin / github etc on my personal domain...

Its kinda annoying having to have this repo public, so i'm most likely moving this to s3/CloudFront since AWS offers 1TB free.