I don't need my doctor to be thin when he's telling me I need to lose fat, though.
I host my blog with their service, I get thousands of visitors a day and it's always extremely fast. I love the simple deployment and the features they give me, and I evangelize their service to everyone.
Try it out, it's fantastic, despite the large landing page.
To be fair, 14.4MB of that is images (I don't know why some of them are that large, however). Does their offering specifically have something related to image optimization / scaling (I'm unfamiliar with Netlify)?
We do have image optimization built-in but it won't change images' size (in case you link externally - we don't want to move your cheese) or do anything lossy.
So - we have not resized and chosen optimal formats for those images and we are working on doing it right now :)
Netlify as a service doesn't really affect how you do things as a front-end developer, but we do help make sure that all those assets get to your browser as fast as can be.
But yes, we all agree that we should do a better job of making our website leaner and we do have a bunch of changes planned around that (and we're hiring!).
You mentioning this made me go and check it out myself and I got to say the page loads are very quick to the natural eye on my connection, FWIW. I would recommend other people check it out themselves as well.
I compared it to apple.com (since someone mentioned it in a lower comment) and apple.com had noticeable page loads whereas Netlify's blog didn't.
I am abroad on a slow 3G connection while nsurlsessiond is eating my bandwidth and the site was extremely slow (took more than a minute to load), while HN loads in 2~3s.
I'm sure the site is fast on a regular connection though.
Netlify is wonderful. I never thought to check if they dogfood their product, though. Sometimes, resources are allocated to new features and site redesign/restructuring work gets pushed to the back burner.
The model of charging per site was removed in [4], the "low tier" $9 per site was also removed, maybe it was not differentiated enough from the free version to be worth the effort. It also seems they introduced "paying per user" in between [3] and [4], maybe that was a form of substitute for the removal of the site limit.
Disclosure: I am a founder of a cloud hosting startup called Sourcevoid, that's in part why I think looking at pricing and packaging of hosting services is interesting, but thought others might like seeing the links above as well.
Netlify is really good for static sites, but you can also combine their static site resources with Flatmarket or Snipcart and create ecommerce sites as well.
I'd suggest checking out their blog (https://www.netlify.com/blogs/), they have a ton of tutorials on the multiple static site generators they support
Awesome service so far. The Continuous Deployment flow is awesome with deploy previews, CDN, custom routing, Automatic SSL from Let's Encrypt. The SSL can be improved to be true automatic without a provisioning step (first hit issues a cert)
It can be easier. We've used https://github.com/GUI/lua-resty-auto-ssl to provide SSL provisioning on the fly at my previous company for our customers` custom domains. This also means that there is no downtime at all when they change the DNS record from their old servers to the new one
Static sites are becoming more and more popular -- you can host them on CDNs across the globe, they can be cached client-side, pre-loaded, work offline....
Especially important thinking about the billions of people in developing countries accessing the Internet over 2G connections.
If the trend towards static sites continues, Netlify could be the next Heroku.
Personally, I use Netlify to host my Gatsby blog; all I need to do is `git push` and they handle the rest.
For me the biggest appeal of static sites is that I now have significantly less attack surface to think about. The chances of someone finding an RCE in Amazon S3 are way less than than the same occurring on some old Apache 2 server where auto-update broke a couple months ago because of the linux kernel headers eating up all my inodes.
You definitely can, but it's not designed or optimized for static sites. And I think there's plenty you can do to improve performance when an app server isn't needed.
I moved some static sites to Netlify from S3 because it seemed easier than getting HTTPS working on S3. It certainly was, and I haven't looked back. The automatic generation of a static site from the repo is a killer feature I didn't know I needed until I tried it.
Yeah, I loved them too really great service that is forward thinking. They work great for large apps or corporate sites, but for small/personal sites their pricing model doesn't work so well, which I can understand.
For instance I needed simple http auth on some directories in a site, and to get that it's $45/month. I ended up with caddy on a $5 digital ocean droplet which automatically sets up and renews the lets encrypt SSL for you. Caddy really is pretty damn nice.
We've changed pricing models 3 times since I've worked here. Each time we've grandfathered people in at their old pricing level, and the last change also gave away substantially more features for free. Never have we moved someone's cheese from "free" to "not free".
I understand that this is still a risk - I'm not promising it will never happen - but we have a killer track record of giving away more, not less, over time, and never have we changed the pricing for an existing site (except to give away enough features that many folks downgraded from paid to free with the last change - and even that was opt-in in case you for some reason wanted to keep paying us :D )
The features not included in free are not typically things you can't do without for personal projects (ie, password protection, role based access control, role management for team members, etc...)
Password protection is a pretty basic need and need not cost $45/month. Of course the role/team based stuff for $45/month makes perfect sense because those are only applicable on larger projects.
I've never found a need for password protection on any of the small personal projects I've worked on. But I guess I could imagine some use cases where that would be nice to have.
Sure it's "easy" in the sense that the hardest part is editing some JSON, but with Netlify once the site is set up it's literally one click to provision and apply an SSL cert.
Netlify is amazing. It is so easy, a pleasure to use for static sites and react apps, continuous deployment is awesome, and open source projects are (for now and hopefully for the long run!) FREE.
We use netlify for quite sometime with Hugo and we loved it.
Today, we use firebase hosting which is significantly cheaper and comes with its own CDN and free Google SSL. But I don't get CI from my git repo - I have to compile and push. Which I personally prefer.
But kudos to Netlify - I hope they realise that the value is not in CDN or CI or ssl certificates . But rather in building a CMS for static websites.
Awesome! Great to hear.
I've pretty much automated my startup ( https://discoverdev.io ) to work on their infrastructure. And the best part is everything comfortably fits into the free tier.
All the collection and curation happens in the backend (on my laptop), get jinja to generate the data into a html and in a single command goes live! This product has been a life saver. No monitoring, cacheing, or any other headache.
Netlify employee here - this is even funnier when it happens from the inside. There's a moment after working here for a fairly short time when you start typing "net..." into your browser and the autocomplete has turned from netflix into netlify. Somewhat of a rite of passage ;)
Yeh, not a fan of the name, and not just for the obvious reason. I'm honestly not even sure how to say it properly. There's too many syllables for such a short name.
Seems like Netlify is the offspring if CloudFlare and Heroku had a child.
I am using Google Cloud Storage as my origin and CloudFlare for few corporate static sites, and it works fantastic. Get CDN, http/2, free SSL, and cost is literally cents.
I love Netlify and how much they support open source projects (thanks!). Hosting a quick mockup is very easy: drag-and-drop zip, done. It comes with Lets Encrypt SSL, CDN, deploy preview and history.
Love love love Netlify! Moved my blog from Tumblr (lol - but it was free!) to Netlify with Hugo as the static site generator. A wonderful experience. With little effort, my blog now has SSL, auto-deploys after I git check-in, and is a million times faster. I wrote a tiny bit about the migration process: https://www.netkow.com/moving-from-tumblr-to-hugo-netlify/
Awesome! Given the somewhat excessive egress prices charged by AWS/S3 and GCP/Cloud Storage for sites hosted on those services, I've always considered Netlify (and others with similar services) as the companion piece to Lambda/Cloud Functions in the "how to go serverless and save money" playbook. It's great to see them getting some VC love since it will make them an easier sell in corporate environments.
I'm using their open-sourced Netlify-CMS for a static-site, and it's been wonderful. If you also have the site hosted by Netlify, they streamline the github push webhook for you that the CMS depends on, which is really nice when you're starting out.
I really like where Netlify is going and how they embrace open source to achieve their goals. There's just one thing I miss in their mix: strong typing. No Elm, PureScript or ReasonML (just yet).
We do use Elm for a couple of minor projects ourself, and it works great on our platform. We also have plenty of people using Typescript or Flow with Netlify.
I'm a big user of Netlify, and host a number of sites with well over a million views a year and they have been rock solid, quick builds, quick support. I can't wait for them to take off!
Does anyone have details regarding their CDN? Competitors tend to give information on their locations so that you can decide if it works for your audience. Cloudflare even delivers information on the edge node in the header to check where the closest one is.
Is there anything like this for netlify? Or any benchmarks on how they generally perform vs. fastly and cloudflare?
Netlify provides a global cdn and administrative features targeting statically generated pages.
S3 is more generic in its goals so it doesn't provide either.
Heroku on the other hand can host server applications which Netlify cannot so it is really a different service. You could host an API on heroku and the react app on Netlify.
probably the best reason is: we have our CDN spread over 4 different cloud providers. AWS and Digital Ocean could both go down (completely - though we're in several different data centers for each) and it would keep on keepin' on.
Just published my first application on Netlify yesterday. I looked at Surge.sh but their pricing doesn't include the SSL certificate. Netlify SSL with Let's Encrypt was literally a button press. Good stuff!
Gitlab on-prem support coming? That would make me very likely to switch especially because I think it would make it much easier to spin up review apps for our SPA's
We do support GitLab on prem already, but right now it doesn't let you trigger deploy previews and branch deploys. Currently that's something we can help with on the custom plan, but we do hope to bring it to the normal tiers as well.
oh nice! thats a welcome change - seems like last time I looked wasnt even 6 months ago and it was not there yet - branch deploys would be one of my exact use cases for sure
ping us in support and I can talk you through the setup w/the private repo (and branch deploys can be simulated with a few netlify sites attached to the same repo - no additional cost for additional sites on any plan)
If you check out this blog post about one of our biggest customers, you can see that there are some non-static services involved (look for the list of 4 services all called Go<something>):
So - while I wouldn't say we're planning to become a DB host or anything - we are both open to providing some glue needed to bring some missing pieces together for static sites without vendor lock in (all of those are open source and you can run your own instances - they are also all being polished up right now so keep an eye on the one(s) that interest you)...and we are trying to enable other services we don't want to reinvent - things like auth0 and firebase - for interoperability with our service.
oh yeah, and we also open sourced a CMS that uses Git as a backing store so your content editors won't have to learn markdown or git... https://github.com/netlify/netlify-cms
There are a few things you can do from static sites; authorization services, database as a service, backend as a service, etc. I find people find theses things appealing in the abstract yet rarely build anything with them. I built a dbaas that failed myself. For example, what dynamic functionality would you like to add to your dynamic site?
I'm thinking of explicitly non-static sites, enabling SaaS offerings. I'd like to see the ease of use and functionality for static sites extended across the full stack.
They are supposed to be targeted at static high performance blogs.
Yet their own blog is 15MB in size and over 100 different http requests.
See the YSlow report for their blog site below.
https://gtmetrix.com/reports/www.netlify.com/C6fG3uTg
It receives an "F" rating.
Isn't this kind of bloated website the exact problem Netlify is suppose to solve?