Netlify, a sevice for quickly rolling out static websites, raises $2.1M
At first I didn&#x27;t understand the difference between Netlify vs. Jekyll &#x2F; Hugo + s3_website [1] + S3&#x2F;CloudFront + git. Admittedly, (1) the OP does a terrible job differentiating the two, and (2) there&#x27;s significant overlap. Netlify is built for &quot;dynamic&quot; static websites, or rather JavaScript applications (whether they be single-page or not, it doesn&#x27;t matter). It serves up a static page, and the JS and APIs do the rest.<p>So, for anyone who wants a basic breakdown between Netlify&#x27;s features, and Jekyll + s3_website + S3&#x2F;CloudFront + git&#x2F;GitHub, here&#x27;s the list of things BOTH support:<p>- Continuous Deployment<p>- Custom Domains &#x2F; Domain Redirects &#x2F; Domain Aliases<p>- Domain Redirects<p>- SSL (letsencrypt-s3front helps here [2])<p>- Redirects &#x2F; Reverse Proxying (s3_website helps here with x-amz-redirect-location header [3])<p>- Headers &#x2F; Custom Headers &#x2F; Basic Auth<p>- Versioning and Rollbacks (handled with git)<p>Here&#x27;s the list of things ONLY Netlify supports:<p>- GeoIP &#x2F; language-based redirects (on their Enterprise Plan for $1,000&#x2F;month)<p>- Form submissions [4]<p>- Analytics snippet injection [5] (albeit a little unnecessary for most developers)<p>- Atomic deploys [6]<p>- Prerending [7] (one of the most important and useful features)<p>Please, correct anything that&#x27;s wrong.<p>Netlify&#x27;s killer feature, for me, looks like prerending: rendering JS pages with a headless browser to help with SEO, with no work on the developer&#x27;s end, is awesome! However, Netlify strikes me as far too expensive at $9&#x2F;$49&#x2F;$399&#x2F;$1k per month. Especially with developers as their target market. That&#x27;s too much for what little extra features it does offer.<p>Here&#x27;s to hoping they can continue to differentiate themselves more.<p>[1]: <a href="https:&#x2F;&#x2F;github.com&#x2F;laurilehmijoki&#x2F;s3_website" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;laurilehmijoki&#x2F;s3_website</a><p>[2]: <a href="https:&#x2F;&#x2F;github.com&#x2F;dlapiduz&#x2F;letsencrypt-s3front" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;dlapiduz&#x2F;letsencrypt-s3front</a><p>[3]: <a href="http:&#x2F;&#x2F;docs.aws.amazon.com&#x2F;AmazonS3&#x2F;latest&#x2F;dev&#x2F;how-to-page-redirect.html" rel="nofollow">http:&#x2F;&#x2F;docs.aws.amazon.com&#x2F;AmazonS3&#x2F;latest&#x2F;dev&#x2F;how-to-page-r...</a><p>[4]: <a href="https:&#x2F;&#x2F;www.netlify.com&#x2F;docs&#x2F;form-handling" rel="nofollow">https:&#x2F;&#x2F;www.netlify.com&#x2F;docs&#x2F;form-handling</a><p>[5]: <a href="https:&#x2F;&#x2F;www.netlify.com&#x2F;docs&#x2F;inject-analytics-snippets" rel="nofollow">https:&#x2F;&#x2F;www.netlify.com&#x2F;docs&#x2F;inject-analytics-snippets</a><p>[6]: <a href="https:&#x2F;&#x2F;www.netlify.com&#x2F;docs&#x2F;versioning-and-rollbacks" rel="nofollow">https:&#x2F;&#x2F;www.netlify.com&#x2F;docs&#x2F;versioning-and-rollbacks</a><p>[7]: <a href="https:&#x2F;&#x2F;www.netlify.com&#x2F;docs&#x2F;prerendering" rel="nofollow">https:&#x2F;&#x2F;www.netlify.com&#x2F;docs&#x2F;prerendering</a><p>EDIT: formatting