Branding Limitations

[A Former User]

Branding is too limited and the following are a few things I have noticed:

• Page Titles still contain Cloudron e.g. User account creation
• Emails sent to user with "Cloudron" in the subject, "powered by Cloudron" in footer
• In user's dashboard, hovering over fa-user icon user is prompted to "Login with Cloudron credentials"
• "Cloudron account" in a user's profile under App Passwords
• DKIM cloudron._domainkey prefix should be changed, not only for branding but other reasons (obscurity). Why needlessly announce an organization is using Cloudron?

Branding should extend to the above. and anything I have yet to see, especially in an Enterprise setting. It should reflect the name of the organization. Ultimately, the user is creating an account with the organization, and not with Cloudron.

[girish]

I like the ideas in general. We had a separate email conversation with @micmc who pointed out similar shortcoming of our white labeling aspect.

[micmc]

@girish And I'm about to come with more, though I like also the ideas mentioned here by @nothing .
White labeling could also be desirable for enterprises providing managed services using Cloudron technology who would prefer to hide their secret weapon from competitors. Especially as Cloudron has very unique features making the whole process so easy to manage compare to anything I've seen yet.

[A Former User]

@girish @micmc Thank you for your input.

I might consider an enterprise subscription if this is something Cloudron implements.

In addition to my original post, I think it is confusing to users, who aren't familiar with Cloudron, it is foreign to them, so questions arise during account setup, emails etc. When Cloudron is branded, the user should see the organization name in each of the instances stated above and anything I have missed.

@girish Agreed, it is unnecessary to make it so blatantly obvious, not only to competitors, but security concerns arise. A DKIM record/email header lets everyone know you're using Cloudron and therefore likely running a host of other services. I don't see any need to do this. It is attached to every email.