Congratulations on the launch! micro/m3o looks like a lot of work. > AWS is a fairly complex beast which makes it hard for new developers to get started. In th

Congratulations on the launch! micro/m3o looks like a lot of work. > AWS is a fairly complex beast which makes it hard for new developers to get started. In the past we needed VMs and file storage, but today with the Jamstack and other modern development models, the building blocks we’re looking for are changing. Yes! Here's a decent read on how the Big3 cloud providers are being unbundled [0]: https://www.swyx.io/cloud-distros/ https://www.swyx.io/cloud-distros/ Heroku, the blog argues, was ahead of its time, but now PaaS start-ups like replit.com, railway.app, render.com, glitch.com, posthog.com, vercel.com, netlify.com are back on the menu, making a big splash as it were, even if most of them themselves rely on Big3 infrastructure underneath. Curiously, m3o is taking the hard path that fly.io once did before settling on their current "global, auto-scaled ec2 with free vpc and load balancer" offering (which is uber awesome as a fargate / lambda replacement) and focusing on just one or two core use-cases (of late, seems like fly.io is particularly putting its weight behind the elixir ecosystem). supabase.com is another such project that's narrowed itself down to being a firebase alternative (as opposed to, say, an alternative to all of GCP) with their FOSS tech build-out being mostly around Postgres. Risking the ire of Dan Abramov here [1], but I suggest m30 errs towards simplicity (and not just easy). Good luck! [0] https://archive.md/bV9oM https://archive.md/bV9oM, "The Founder's Dilemma: To Compete or Unbundle" (a16z) [1] https://news.ycombinator.com/item?id=19485609 https://news.ycombinator.com/item?id=19485609