IME, letting developers have free reign over service architecture/deployment/CI/observability is a bad idea. Especially when every team comes up with their own option.
You need some sort of Devops (best practices if not a team) to provide guidance and help implement standards for these.
I agree, if we're talking about places big enough to have multiple teams. The thing I was pointing out is that most places that have multiple teams are terrible at setting up best practices. They'd be better off with a centralized "environments" team provisioning the server, network, etc so the dev teams can work on the actually implementation. At least it's easier to maintain standards, or at least consistency, across apps if the low/mid level config is handled by one team.
When I was talking about small places, I mean like tiny mom and pop non-tech companies with an IT department of 1-5 people.
You need some sort of Devops (best practices if not a team) to provide guidance and help implement standards for these.