Configuring Cloudflare for SaaS

​​ Before you begin

Before you start creating custom hostnames:

1. Add your zone to Cloudflare on a Free plan.
2. Enable Cloudflare for SaaS for your zone.
3. (optional) Review the following documentation:

• API documentation (if you have not worked with the Cloudflare API before).
• Hostname prioritization.
• Certificate validation.

​​ Initial setup

When you first enable Cloudflare for SaaS, you need to perform a few steps prior to creating any custom hostnames.

​​ Step 1 — Create fallback origin

The fallback origin is where Cloudflare will route traffic sent to your custom hostnames (must be proxied).

To create your fallback origin:

1. Create a proxied A, AAAA, or CNAME record pointing to the IP address of your fallback origin (where Cloudflare will send custom hostname traffic).

2. Designate that record as your fallback origin.

3. Once you have added the fallback origin, confirm that its status is Active.

​​ Step 2 (optional) — Create CNAME target

The CNAME target — optional, but highly encouraged — provides a friendly and more flexible place for customers to route their traffic. You may want to use a subdomain such as customers.<SAAS_PROVIDER>.com.

Create a proxied CNAME that points your CNAME target to your fallback origin (can be a wildcard such as *.customers.saasprovider.com).

​​ Per-hostname setup

You need to perform the following steps for each custom hostname.

​​ Step 1 — Plan for validation

Before you create a hostname, you need to plan for:

1. Certificate validation: Upon successful validation, the certificates are deployed to Cloudflare’s global network.
2. Hostname validation: Upon successful validation, Cloudflare proxies traffic for this hostname.

You must complete both these steps for the hostname to work as expected.

​​ Step 2 — Create custom hostname

After planning for certification and hostname validation, you can create the custom hostname.

To create a custom hostname:

​​ Step 3 — Have customer create CNAME record

To finish the custom hostname setup, your customer needs to set up a CNAME record at their authoritative DNS that points to your CNAME target ¹.

Your customer’s CNAME record might look like the following:

www.mystore.com CNAME customers.saasprovider.com

This record would route traffic in the following way:

Requests to www.mystore.com would go to your CNAME target (customers.saasprovider.com), which would then route to your fallback origin (proxy-fallback.saasprovider.com).

​​ Service continuation

If your customer is also using Cloudflare for their domain, they should keep their DNS record pointing to your SaaS provider in place for as long as they want to use your service.

For more details, refer to Remove custom hostnames.