This hits close to home. I have something similar, except it's not as featureful and it's ridiculously purpose-built for me. E.g. I have one page in this app fo

This hits close to home. I have something similar, except it's not as featureful and it's ridiculously purpose-built for me. E.g. I have one page in this app for generating PDFs of a very specific type that I need. I have another page that parses CSVs from my bank. These aren't tools I use regularly, I just need them occasionally, but they're all in one repo in one project. There are of course apps that do each of these, but when you start integrating them together, with their different ways of doing auth, different kinds of APIs, etc. things get so complicated. I worked in a company that integrated with some third parties and those integrations were easily 50% of the workload for the dev team and maybe 90% of the workload for support. There is so much effort being wasted on having different systems for different things. I feel like there's an idea out there that will solve all this for open source--maybe involving stitched GraphQL APIs, OIDC+JWT for auth, etc. Something kind of like Sandstorm[1] except with Sandstorm the different apps weren't necessarily built with Sandstorm in mind. In this system there would be a centralized identity management system like Keycloak that manages concepts like users, roles and apps, and everything else delegates auth to that centralized system. [1] https://sandstorm.io/ https://sandstorm.io/