@williampietri @kfitz Oh and you'll need to provide object storage, of course.
A PaaS is also not great for heavy ETL/machine-learning due to limited local disk.
My feeling after looking at the Supabase stack a lot lately is that "just use postgres" is a boring but also winning architecture strategy for most of what people want to make, but as the service provider you might not get much say over what they are working with.
@williampietri @kfitz So, depending on who you want to serve, I'd probably just start with hardware and OpenStack (IaaS), then work up to OpenShift+Korifi or BOSH+Cloud Foundry (PaaS).
After that, listen to what people want and start providing those as brokered services that they don't have to operate themselves. I'm not crazy about k8s, but if you start with OpenShift you're in a good position both to provide a k8s service, and to use it yourself to operate specialized brokered services.