EDIT To keep the theme going: "10 years in business tells me...+1" lol
@micmc I do agree on adding some/more features geared toward managed Cloudron providers (although I am totally biased here aka on your side lol) but the issue would be effort as @marcusquinn suggests.
The main factors I see between the suggested features are
- Administration /support
- Admin vs Superadmin
The main problem I see is for a fully fledged "White label" platform/user experience one would have to refactor every app to have a similar theme, OR make custom UI's and integrate with every single app...
There is not much of a point of "hiding" Cloudron as a platform but then leaving the branding for RocketChat, NextCloud and the rest of the apps...I get and agree with your end game but as you mentioned users can try and go to the respective project sites/docs or team for support given they know what's "behind the Curtin"
Yes having the "platform" not branded to Cloudron and instead be "XYZ" MSP or the clients company is a good thing but IMO its the "Last" important thing
Pretty much all of what you are suggesting especially the text/link branding is valuable but the issue is more about priority/capacity of the core devs
Taking the slow and steady route and eventually getting to the full feature set seems to be the more logical route given the size of the Cloudron team and the other tasks at hand. Point is there has to be a middle ground for everyone to get "a version" of Cloudron that they want/need, in time...My suggestion would be for us to prioritize the features and advocate for one at a time
Last minute thought before publishing: maybe Cloudron team does not have to change how the admin profile works but could add another profile like "OWNER" for example where the text*/links are more ideal from* an MSP standpoint
Regardless, I am very interested and vested in a similar outcome so if you'd like to talk more here or directly shoot me a message , always down to converse with likeminded ppl