Squandered is a bit harsh. I don't have skin in the game either way, but I wouldn't be surprised if there is a profitable business to be built once the dust settles. It can be hard to know in advance just how big that market would be, and how defensible.
We tried cognito (bizarrely hard to use), Auth0 (mildly hard to use), and Userfront (easy to use) for authentication + rbac + multi-tenancy. We also looked at Warrant and Oso, and my takeaway was that they shine for more complex use cases, which wasn't our particular need.
Thank you for building it! I haven't kicked the tires yet, but as a node developer, this feels like the future: we can move fast with node when it makes sense, and get rust level performance when we need to. Best of both worlds!
Yes, it is our fault for believing Netlify had contingency plans as hosting is their core business. We're fixing this mistake now so that our customers don't have the same experience.
We use(d) Netlify for the frontend. I agree, our mistake was believing Netlify could be used for more than toy websites and took care of backup plans for us. Clearly they do not.
Honestly, "not taking advantage of our DNS management" is a garbage response. We use AWS for our DNS management. If you offer a configuration, you should support it fully.
Our sites have been down for 3 hours now, and you're blaming someone else? We have 5 properties on Netlify now and will have 0 this time next week.
Amazon (and all the others you've mentioned) have the ability to choose their suppliers. There isn't piss in the Gatorade nor nails in the M&Ms because this is a solved problem: make companies liable for their supply chains.
If you're considering a really low price point like $5/mo, you might be better suited charging businesses more and then having a free tier that's restricted to personal use in some way (e.g. license or no collaboration)