I imagine it would scale about as well as the git* API backing it up, given that the content list etc. are all pulled from the git host's API (Github in this case).

I like the way it uses pull requests to handle drafts. A couple of clever build scripts in the repo would make for a pretty sweet deployment workflow.

I'm not super keen on the way it stores uploaded assets though. I understand the benefit of simplicity in only targeting a single API, but it would be nice to target a cloud hosting service (like GCE/AWS storage) for asset uploads.

That one is really meant for small things.

Alas, for massive sites with lots of content, Netlify's other services plays nicely with other tools. E.g. his AT&T dev proposes GatsbyJS, Contentful, and Netlify in combination [0].

[0]: https://hackernoon.com/contentful-and-netlify-the-dynamic-du...