Qloaked logo

Painless customer SSL for SaaS businesses

Securing client-owned domains can be a herculean task.

Qloaked provides instant security for third-party domains, provisioned on the fly, with no downtime. Gain all the benefits of SSL (security, speed, SEO improvements), without the pain of transitioning users.

Use it to secure one, one hundred or one thousand customer domains pointed at your service in just minutes, removing the headache of insecure connections once and for all.

Find out more
Homepage hero

Seamlessly managing customer SSL at scale - how does it work?

If your clients send you traffic via non-SSL vanity (custom) domains, here’s how to transition them all in a day.


You forward your existing CNAME target (e.g. clients.yourapp.com) to Qloaked.


Qloaked seamlessly transitions all connection requests via custom domains to SSL on the fly.


Your clients enjoy encrypted domains, with no extra work.


Flawless security

Secure connections when you need them – industry-standard Let's Encrypt SSL/TLS certificates to protect customer data, protect against man-in-the-middle attacks and network packet sniffing.


Branding peace of mind

Your clients know that their visitors feel safe, thanks to valid certificates for fully-encrypted connections.


Automated SSL management via Let's Encrypt

No purchases and no certificate hosting – the Qloaked solution is totally automated. Qloaked deploys and manages Let's Encrypt certificates almost instantly. No more engineering requests on your side or messing customer success interactions to configure CNAME config on their side.


Tremendously secure

Traditional SSL certificates run for up to two years, but Qloaked uses certificates that auto-rotate every 90 days, keeping your customers – and their customers – more secure than ever.


Lowered liability

Keeping valuable private keys secure on behalf of clients is a compliance risk your business can do without. Forget handling certificates – Qloaked stores and keeps all keys encrypted at rest.


Instantaneous deployment

Forget the nightmare of transitioning blocks of users, requesting settings updates or managing config for users. It's all done, in an instant.

Frequently Asked Questions

Why should I care about providing SSL/HTTPS support?

Modern browsers alert the user when they’re on a website that doesn’t have SSL configured. In Chrome they will see a “Not secured” message - this is not good for you, your customer or your customer's users. Search engines penalize non-secure content.

With an SSL/HTTPS connection in place, the data being transferred is encrypted so that other services/servers and bad actors can’t read the data in transit – protecting the communication between your customer's users and your service.

Can any domain be secured by Qloaked?

Yes, as long as the domain owner adds a DNS entry pointing to the service.

Can I ask my users to point the CNAME to one of my domains?

Yes, as part of signing up we will ask you to point a CNAME at our service e.g. secure-hosting.yourdomain.com to a Qloaked domain. The secure-hosting.yourdomain.com is what your clients will use and add to their DNS.

If you are unhappy with the service you can easily transition away from Qloaked by pointing the DNS back towards your own servers.

Will I have to pay for any additional SSL certificates?


What happens when the SSL certificates expire?

Qloaked will automatically renew and manage the SSL certificates.

How long does it take for Qloaked to setup the SSL certificate?

Typically a couple of seconds.

Will all of the data then be secured?

As long as your origin site where we send the traffic to is running on https, Qloaked will have end to end encryption.

What happens while the SSL is being provisioned? Will there be any down time for my customer?

No - While Qloaked is provisioning the service we’ll send the traffic as http and then transition to https once the SSL certificate is in place.

What would my customer have to do to set up SSL for the custom site without Qloaked?

Typically they’d have to generate a SSL certificate request, pay a third party to verify it. Then install the SSL certificate on a server as a reverse proxy or a CDN to run in front of your service. Every year or two they’d have to go through that process again when the SSL certificate expired.

Find Out More