I get that SSL for custom hostnames is ****** to support - but security shouldn't be something users have to pay extra for.

While it's great that you provide custom domains for free, making us pay to have our users interact securely really feels gross.

Without it, I'm not really sure what the point of the custom domain. As it is, it's worthless to me (my entire site is on SSL, and browsers don't like switching protocols for subdomains).

So, I propose that SSL support for hostnames is included for all plans. Most of your customers aren't likely to implement it (so no extra cost hit there), and for smaller organizations like mine that need it (but don't need any of the other advanced features), it'd be a huge help.

Thanks for listening!