While discussing fedeproxy with @dachary last week, we mentioned two projects that might be source of inspiration.
Which attempts to unify access to cloud resources which all have different APIs and it often finds a common denominator enabling applications that use this abstraction to be independent of a given cloud implementation, enabling the freedom to change cloud providers without changing the definition of a deployment (salt-cloud can be used as an exemple)
Here the Apache foundation is a warrant of maintenance and longevity of the project.
beeper is a proprietary chat solution for unified chat which is based on the open source components around matrix (https://matrix.org/), it promises to finance and maintain the bridges ecosystem (see the Bridges sections in the blog https://matrix.org/blog/posts ).
For the list of bridges, which by definition are fragile and need to be maintained whenever the API or the chat service it bridges to change (and we know that can be often and unannounced, see the history of the twitter API).
Here we have companies that have a stake in keeping the bridges working because they provide a service based on that.