At first glance this looks very much like Firebase, minus the real-time datastore. What's different/better about Netlify, and how are you supposed to use it for sites that need to persist data (i.e., pretty much anything non-trivial)?
Features off the top of my head:
* SSL support (through Let's Encrypt), even with custom domains
* A global CDN
* Instant cache invalidation
* Redeploy with one click
* Roll back support
* Custom build commands (whereas with GitHub Pages, you either have to use Jekyll or commit generated files)
* An API
* Preview websites for GitHub pull requests, so you can easily view changes in browser before merging
For sites that persist data, you could still use Netlify to deliver the frontend and then use Ajax to talk to the backend.
Sounds like Netlify is competing either on simplicity or on price, with a (likely temporary) advantage in developer tooling integration.