> Infrastructure, and usually code powering them is very hard to open source imo. In a way that is useful. > or any large infrastructure as application specific. Your servers and your network is not my servers nor my network. Your control plane and service discovery (if you have one) might be meant for colo, full cloud, kubs as a service, physical hardware, theres' no point releasing it. I think many don't admit there is some security through obscurity as well. Knowing long-term topology could allow an attacker to cripple systems more easily My block storage might be cheaper than yours, my object storage might be cheaper. There are so many differences. For example, - my new infra relies on a low latency control plane now, that can't really happen in the cloud - I have shared storage on a trusted network just heavily depends on the application and costs involved.