Hm. This is a lot of "isn't" and not a lot of "is", limiting the usefulness. For example, something we as a platform team contribute to our products success is

Hm. This is a lot of "isn't" and not a lot of "is", limiting the usefulness. For example, something we as a platform team contribute to our products success is data safety, backups and archiving. Our dev-teams are just using our postgres clusters with little effort. That way they can say they are using a highly available storage layer, with perodic backups, backups being periodically restore-tested, backups being archived long-term and archived to multiple different locations and providers. We check many non-functional boxes overall. And if a B2B customer wants to be a jerk about it, we can be invited to such meetings. And suddenly they aren't talking to a regular Dev or PO anymore, but someone who has been doing this for 10 - 15 years across different companies and industries. This kind of backup tends to be very, very valuable to our smaller and more agile teams.