That's.. not the same.

They mean for CNAME'd sites: https://help.github.com/articles/setting-up-a-custom-domain-...

He (probably) means with a custom domain.

Today, I tried out your service with a previously-unused domain and a brand new gh-pages repo.

When I ran into a small issue, I used the instant chat applet inside the Kloudsec control panel, and Steven quickly discovered the problem (I simply needed to remove the two A records pointing to GitHub pages, leaving only the Kloudsec A record).

Everything is working flawlessly so far, in regards to having TLS/SSL for custom domain hosted on GitHub pages. I especially like the option to enable HSTS for the domain's SSL. I wish GitHub Pages' own SSL on username.github.com offered that option.

All in all, painless plus quick, and without the unclean feeling that comes with Cloudflare's free SSL option. Additionally, I'm impressed with Steven's quick and quality assistance via chat and email.

edit: I've now noticed that there are large blocks of Javascript injected into my one-page test website. Ostensibly for the Speed Booster CDN plugin; I'll update after confirming the JS is gone upon disabling all plugins aside from the One-Click Encryption plugin.

edit2: Confirmed. Speed Booster plugin was source of JS injection. I suppose that's the drawback to a CDN who doesn't also host your DNS. Ironically, due to test site being small and static, disabling the Speed Booster plugin to remove all the JavaScript increased page load speeds.

Still, this doesn't detract from Kloudsec's simple deployment of LetsEncrypt SSL certificates for custom domains hosted on GitHub pages.

Google uses https as a signal of quality, and Chrome will start shaming sites that aren't:

http://motherboard.vice.com/read/google-will-soon-shame-all-...

I only have static, unimportant data on my site, but I use HTTPS in case someone's ISP is injecting ads or scripts into their pages. I don't want people to think that's part of my website.

You might be serving something like a PGP public key, which you'd like viewers to be assured hasn't been tampered with in transit.

https is also for authentication, not just encryption.

Some feedback:

The cost is a non-starter. The main reason I go through the hassle of writing compilers for my websites is that I want them to be long-lived.

Presently, I use Nearly Free Speech as my hosting provider. Their pricing scheme for static sites costs me about $2.50/yr and I can maintain an account balance. My $50 account balance will keep my site online for two decades whereas it would buy me only ten months on your service. (Not to mention that Github hosts static sites for free!)

To consider another service, it wouldn't just have to beat the cost but instill a sense of confidence that I could trust the service with my data for the foreseeable future. A few features could tip the scales though: - Open ID auth instead of basic access auth - Easy SSL setup (gethttpsforfree.com was recently a huge help) - Inexpensive hosting for a very low-volume mailing list with HTML archives

Good luck!

Nice. One way you could distinguish your service from all other options (S3, Github Pages), is to support the history API for single page webapps. I'm hosting a static site on EC2 instead of S3 because I need URLs to fallback to index.html. Literally for this one nginx rule:

    location / {
        try_files $uri /index.html =404;
    }

Also, I'd like to try the beta of your service, just signed up. My email is in my profile. Thanks!

Your site doesn't accept connections over SSL.