[afterwalk]

The value proposition was clear and well written, until I got to this part:

"you want to do it without having to standup layers of infrastructure on AWS or be beholden to the legacy players like Heroku or other providers who don’t get that you want the same Netlify like experience on the backend."

So exactly how is Heroku "legacy"? From past experiences pushing a simple backend service onto Heroku was pretty smooth and "Netlify-esq".

It would be nice to explain or show the shortcomings of using Heroku as the backend for your Netlify app.

[jamil7]

Yeah this bits kinda weird. Heroku is still easiest host I’ve found for throwing up an API + database.

[gscho]

Heroku IS the netlify for backends. This product has good intentions though. Good luck!