Cloudflare on Flashcloud is portal-managed only. There's no separate cloudflare.com account to log into, no orange-cloud DNS dashboard to configure by hand. The Cloudflare CDN page in your portal sidebar is where the controls live, separate from the Manage CDN action on your hosting service page. This article draws the line between the two so you know what to expect and where to go for each.
What Cloudflare handles automatically
Because our nameservers point to Cloudflare, every hosted domain gets fast, geographically distributed DNS resolution with no setup. The proxy toggle on the CDN page is on by default for hosted domains, which means DDoS protection and edge caching are active out of the box, but it is a toggle, not a fixed setting, so it's worth knowing it's there.
What you control from the portal
The Cloudflare CDN page gives you a proxy toggle and a caching toggle, per domain, both on by default for hosted domains. Flip the proxy on and Cloudflare's edge sits in front of your site, caching static assets and absorbing traffic before it hits your server. From the same page you can purge the cache. From Manage, the advanced settings screen for that domain covers SSL/TLS mode, Under Attack mode, security level, minimum TLS version, Always Use HTTPS, Auto Minify, Brotli, Rocket Loader, and more. If you want a setting-by-setting breakdown of what each one actually does and when to touch it, see Every Cloudflare setting explained.
One thing worth being precise about: the proxy toggle applies to the whole domain, not to individual DNS records. There's no per-record orange cloud like you'd see on a native Cloudflare account. If you need to reason about when turning proxy mode on is actually worth it for your traffic, Setting up a CDN with Cloudflare covers that decision in more detail.
The AI crawlers panel
The CDN page also includes a panel for controlling AI crawler access to your site, split into three categories: search crawlers, AI assistants, and model training. Each has its own allow, block, or block-on-ad-pages setting, and the model training category adds an "ask nicely" option that relies on robots.txt rather than an active block. If you're already thinking about how AI tools discover and summarize your site, it's worth pairing this with llms.txt: helping AI assistants understand your website, which covers a complementary, passive way to describe your site to the same crawlers.
What isn't exposed, and why that's normal
A few things a native Cloudflare account gives you aren't part of this setup, because the account itself doesn't exist outside our portal. There's no Cloudflare analytics dashboard to check separately, no development-mode toggle, and no way to bring your own existing Cloudflare account into the mix. There's also no per-record proxy control, as mentioned above: it's domain-wide.
None of this is a missing feature so much as a different shape of the same product. You get the settings that matter for a hosted site, day to day, without needing a second login or a second place to check when something looks slow or a page won't load fresh content.
When to check your cache first
If a page looks stale after you publish a change, the CDN page's Purge cache button is the first thing to try, not a support ticket. Caching sits between your visitors and your server so pages load fast, and that means a change on your end doesn't always show up instantly on theirs. Purge, reload with a hard refresh, and check again before assuming something's broken.
If you've checked the settings above and something still isn't behaving, for example a domain that won't proxy correctly, or a security setting that seems to be blocking legitimate traffic, open a ticket from Support > New ticket in the portal. A real person looks at it; there's no phone line, but tickets and live chat both reach the same support team.