I don't think this is true at all. Red Hat needed a web toolkit for their products and presumably decided that the available options weren't suitable for their

I don't think this is true at all. Red Hat needed a web toolkit for their products and presumably decided that the available options weren't suitable for their purposes. These are more common now because a few years ago a lot of folks drew the same conclusions at around the same time. For example, PivotalUI[0] was developed in-house to provide a uniform toolkit and look-n-feel for Pivotal's various web interfaces (Pivotal Network, OpsMan, AppsMan, Healthcheck, Metrics etc). Other examples include JetBrains's RingUI[1] or Microsoft's ReactXP[2]. But by no means is PivotalUI intended to lock anyone into anything. To my knowledge our consulting division, Pivotal Labs, has undertaken approximately zero projects using Pivotal UI. Disclosure: I work for Pivotal. We compete with Red Hat. [0] https://styleguide.pivotal.io/ https://styleguide.pivotal.io/ [1] https://www.jetbrains.org/ring-ui/index.html https://www.jetbrains.org/ring-ui/index.html [2] https://microsoft.github.io/reactxp/ https://microsoft.github.io/reactxp/