I have a number of Lemmy instances meant for discussion groups around specific topics. They are not being as used as I expected/hoped. I would like to set them up in a way that they can be owned by a consortium of different admins so that they are collectively owned. My only requirement: these instances should remain closed for registrations and used only to create communities.
On the other hand, for some communities moderation of the communities and the members are specific and should not be generalized.
Beehaw is an example that comes to mind, lemmy.ml as well
Even though the community is contained the cloud resources should still be split in two between identity and operations to be in alignment with all the industry best practices and potential for scalability. Remember the unix philosophy is do one thing well.
Beehaw should operate their own Beehaw fediverse IDP (Identity provider) for the users to sign in with, that would manage their tos agreements, privacy policies and user based security. Separately they should operate their Lemmy server which hosts pictures and links organized by communities. They could just use a single IDP for their instance and have the same experience as now only better with better architecture.
Source: I am a cloud services architect.