<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Feature descriptions]]></title><description><![CDATA[<p dir="auto">Sorry for asking, We are testing cloudron now for a couple of days and i want to use it for our managed hosting offerings, while i am very pleased by the support (it is superb !!!) i am a little stuck on pricing and features.</p>
<p dir="auto">These features are not clear to me:</p>
<ul>
<li>Extended Branding ?</li>
<li>Advanced user ACL (does this mean that i can give users acces to mail settings?)</li>
</ul>
<p dir="auto">Is Cloudron suitable for multiple users who can creat their own users website and apps:</p>
<ul>
<li>Do they have to enter everytime their Cloudflare APi key when adding a domain or do i have to do that everytime?</li>
<li>is the pricing per Cloudron server, for example if i have 5 Resellers who want to use this do i need 5 Cloudron license of 60€ each?</li>
</ul>
<p dir="auto">Best regards,</p>
<p dir="auto">Peter Kuipers<br />
Kyzoe Hosting</p>
<p dir="auto">E: <a href="mailto:hallo@kyzoe.be" target="_blank" rel="noopener noreferrer nofollow ugc">hallo@kyzoe.be</a> W: <a href="https://kyzoe.be" target="_blank" rel="noopener noreferrer nofollow ugc">https://kyzoe.be</a></p>
]]></description><link>https://forum.cloudron.io/topic/4174/feature-descriptions</link><generator>RSS for Node</generator><lastBuildDate>Sun, 13 Sep 2026 20:04:04 GMT</lastBuildDate><atom:link href="https://forum.cloudron.io/topic/4174.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 11 Jan 2021 22:37:49 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Feature descriptions on Tue, 12 Jan 2021 11:41:54 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/girish" aria-label="Profile: girish">@<bdi>girish</bdi></a> Thanks,</p>
<p dir="auto">Love to see your email coming!</p>
]]></description><link>https://forum.cloudron.io/post/23250</link><guid isPermaLink="true">https://forum.cloudron.io/post/23250</guid><dc:creator><![CDATA[kyzoe.be]]></dc:creator><pubDate>Tue, 12 Jan 2021 11:41:54 GMT</pubDate></item><item><title><![CDATA[Reply to Feature descriptions on Tue, 12 Jan 2021 01:52:21 GMT]]></title><description><![CDATA[<p dir="auto">@kyzoe-be Nothing to be sorry about <img src="https://forum.cloudron.io/assets/plugins/nodebb-plugin-emoji/emoji/android/1f642.png?v=f0ef0373a83" class="not-responsive emoji emoji-android emoji--slightly_smiling_face" style="height:23px;width:auto;vertical-align:middle" title=":)" alt="🙂" /> There is a bit of a disconnect between the pricing page and what is actually implemented in the product. This is simply because we want to first find out what feature appears to which audience before actually implementing restrictions of features based on the plans.</p>
<p dir="auto">With that out of the way.. Extended branding refers to having email branded (like if you add a user on Cloudron, the invitation email still says 'cloudron' in the footer). This feature is not implemented yet. For advanced user ACL, currently, this is available in the Premium plan (where there is different user roles like superadmin/admin/user manager etc). These features will likely move to the higher plan. (Before someone mis-reads this, don't worry, existing users are never affected by all these changes, we always grandfather to the features that you had when you started using Cloudron).</p>
<p dir="auto">Finally, for the pricing, the one we have on website is not meant for resellers. We treat resellers more or less like partners and can offer good discounts. I will contact you from our support email address, so we can discuss further. Thanks!</p>
]]></description><link>https://forum.cloudron.io/post/23224</link><guid isPermaLink="true">https://forum.cloudron.io/post/23224</guid><dc:creator><![CDATA[girish]]></dc:creator><pubDate>Tue, 12 Jan 2021 01:52:21 GMT</pubDate></item></channel></rss>