Skip to main content

Connecting a Custom Domain to CloudFFL OS

Every CloudFFL OS account includes a CloudFFL-managed web address. You can also use your own domain, such as yourstore.com or erp.yourstore.com, after your DNS records point to CloudFFL OS.

One Domain Serves the Whole CloudFFL OS Site

CloudFFL OS uses one domain for the customer-facing website and the staff back office. If the built-in website is enabled, visitors who go to the root of your domain, such as https://yourstore.com, land on your website. Staff still sign in from the same domain using the back-office path.

Customer website: https://yourstore.com/
Staff back office: https://yourstore.com/web
Alternate staff path, where enabled: https://yourstore.com/odoo

The website and staff back office are part of the same CloudFFL OS instance. Choose the domain you want customers or staff to use, then use /web or /odoo on that same domain for staff access.

Which Domain Should You Use?

  • Use your main domain, such as yourstore.com, when the built-in CloudFFL OS website should be your public website.
  • Use a subdomain, such as erp.yourstore.com or app.yourstore.com, when your public website is hosted somewhere else and CloudFFL OS is only for staff operations.
  • Add www only as a redirect to the main domain you choose, unless CloudFFL support tells you otherwise.

What You Need Before You Start

  • Access to your domain's DNS settings. This is usually managed where you bought the domain, such as Cloudflare, GoDaddy, Namecheap, or Google Domains/Squarespace.
  • The domain or subdomain you want to use for CloudFFL OS.
  • A message to CloudFFL support with the exact domain after the DNS record is added.

Using Your Main Domain for the Built-In Website

If CloudFFL OS should be your public website, point the root domain to CloudFFL OS. Your website will use the root address, and staff will use the same domain with the back-office path.

  1. Open your DNS provider.
  2. Create or update the root/apex record. Some DNS providers call this @.
  3. Set the record type to A.
  4. Set the value/content to 34.57.227.147.
  5. Set the proxy/CDN option to DNS only if available.
  6. Save the record.
  7. Send the domain to CloudFFL support so we can finish the secure routing setup.
Type: A
Name: @
Value: 34.57.227.147
Proxy/CDN: DNS only

Using a Subdomain for Staff Operations

If your public website is hosted somewhere else, use a subdomain for CloudFFL OS. For example, your public website can stay at https://yourstore.com, while CloudFFL OS runs at https://erp.yourstore.com.

  1. Open your DNS provider.
  2. Create a new DNS record.
  3. Set the record type to A.
  4. Set the name to the subdomain you want, such as erp.
  5. Set the value/content to 34.57.227.147.
  6. Set the proxy/CDN option to DNS only if your DNS provider has that option.
  7. Save the record.
  8. Send the full hostname, such as erp.yourstore.com, to CloudFFL support so we can finish the secure routing setup.
Type: A
Name: erp
Value: 34.57.227.147
Proxy/CDN: DNS only

Optional: Add www

If you want www.yourstore.com to work too, add a second A record for www. CloudFFL can redirect it to your main domain so customers do not see two different website addresses.

Type: A
Name: www
Value: 34.57.227.147
Proxy/CDN: DNS only

After DNS Is Saved

DNS changes often work within a few minutes, but some providers can take longer. CloudFFL support will verify that the domain points to CloudFFL OS, enable the secure certificate, and connect the domain to your account.

Use the DNS value shown in this guide, or the newer value provided by CloudFFL support. If your DNS provider offers a proxy/CDN toggle, leave the record set to DNS only.

Keep Your CloudFFL OS Address

Your CloudFFL-managed address stays available even after a custom domain is added. This gives your team and CloudFFL support a stable backup address for direct access.

Back to top