At what point did building a tiny SaaS require accounts with half the internet?

I'm sketching out another small SaaS and trying to be more disciplined about the stack this time because my last project somehow ended up with a separate service for nearly everything. Hosting here, database there, auth somewhere else, email somewhere else, payments somewhere else and then another dashboard to figure out which one broke. Some of that separation obviously makes sense once you need specialized tools, but for an MVP with no users yet it feels like I'm designing infrastructure for a company that doesn't exist. If you were starting something small today, which parts would you consolidate and which would you absolutely keep separate? I'm particularly curious about hosting + database because that seems like one of the easier places to remove a vendor without giving up much. Payments and email I can understand keeping specialized. Trying to build the boring version this time and add complexity only after the product earns it.