Pretty cool. We were recently discussing how a service like this could exist. Excited to try it out.<p>One suggestion - on the Signup page, you ask for a lot of permissions right away from Github. I think it would be better if you just collected profile/email address and then when I started exploring a little more and working to get my first site deployed, only then ask for the additional permissions.
I think I'm not understanding what it does, but why does it cost $9/mo/site to serve some static content? Isn't that basically free nowadays?<p>I guess my question is "what does Netlify do that GitHub pages doesn't"?
Congrats! And thanks for adding GitLab integration <a href="https://www.netlify.com/blog/2016/07/13/gitlab-integration" rel="nofollow">https://www.netlify.com/blog/2016/07/13/gitlab-integration</a>
At first I didn't understand the difference between Netlify vs. Jekyll / Hugo + s3_website [1] + S3/CloudFront + git. Admittedly, (1) the OP does a terrible job differentiating the two, and (2) there's significant overlap. Netlify is built for "dynamic" static websites, or rather JavaScript applications (whether they be single-page or not, it doesn'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's features, and Jekyll + s3_website + S3/CloudFront + git/GitHub, here's the list of things BOTH support:<p>- Continuous Deployment<p>- Custom Domains / Domain Redirects / Domain Aliases<p>- Domain Redirects<p>- SSL (letsencrypt-s3front helps here [2])<p>- Redirects / Reverse Proxying (s3_website helps here with x-amz-redirect-location header [3])<p>- Headers / Custom Headers / Basic Auth<p>- Versioning and Rollbacks (handled with git)<p>Here's the list of things ONLY Netlify supports:<p>- GeoIP / language-based redirects (on their Enterprise Plan for $1,000/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's wrong.<p>Netlify'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's end, is awesome! However, Netlify strikes me as far too expensive at $9/$49/$399/$1k per month. Especially with developers as their target market. That's too much for what little extra features it does offer.<p>Here's to hoping they can continue to differentiate themselves more.<p>[1]: <a href="https://github.com/laurilehmijoki/s3_website" rel="nofollow">https://github.com/laurilehmijoki/s3_website</a><p>[2]: <a href="https://github.com/dlapiduz/letsencrypt-s3front" rel="nofollow">https://github.com/dlapiduz/letsencrypt-s3front</a><p>[3]: <a href="http://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html" rel="nofollow">http://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-r...</a><p>[4]: <a href="https://www.netlify.com/docs/form-handling" rel="nofollow">https://www.netlify.com/docs/form-handling</a><p>[5]: <a href="https://www.netlify.com/docs/inject-analytics-snippets" rel="nofollow">https://www.netlify.com/docs/inject-analytics-snippets</a><p>[6]: <a href="https://www.netlify.com/docs/versioning-and-rollbacks" rel="nofollow">https://www.netlify.com/docs/versioning-and-rollbacks</a><p>[7]: <a href="https://www.netlify.com/docs/prerendering" rel="nofollow">https://www.netlify.com/docs/prerendering</a><p>EDIT: formatting