Create Accountor Login

Edge Protection

Edge Protection: Cloudflare Configured for Your Site, Then Kept That Way

Out of the box Cloudflare runs on defaults that are safe but not tailored. We set the firewall, bot protection, rate limiting, caching, and SSL around how your site is actually used. Each morning we compare the live settings with what we set.

With Cascadia you get

  • Configured for your site, not a template
  • Firewall and bot rules set up
  • Speed settings tuned
  • Set once, checked daily
  • Drift caught the next morning
  • Changes made for you

Why Teams Start Here

Drift Caught the Next Morning

Nine settings are compared with ours every day. A change made yesterday reaches you today instead of in the middle of an incident, and we put it back if it was not yours.

Set Once, Checked Daily

Settings wander. Development mode gets switched on for a test and stays on, or a rule is disabled during an incident and never restored. The daily comparison catches both.

Configured for Your Site, Not a Template

A shop, a booking site, and a brochure site need different rules, so none of them gets a template. What we set is recorded, and you can see exactly what protects you.

What you get

Everything Edge Protection Covers

Everything below is part of Edge Protection and is set up and looked after by our team.

Firewall

  • Rules written around your site
  • Protection for wp-login and xmlrpc
  • Country and ASN blocking where it helps
  • Known bad traffic dropped at the edge
  • Exceptions for the tools you really use

Bots and Abuse

  • Bot protection configured rather than left on default
  • Rate limits on the paths that get hammered
  • Scrapers and vulnerability scanners blocked
  • Form spam cut down at the edge
  • Good bots allowed through

Speed

  • Caching tuned to how the site is built
  • Browser cache set sensibly
  • Always Online for when the origin fails
  • HTTPS enforced and TLS kept current
  • Development mode never left on

Watching

  • Nine settings compared daily with what we set
  • A ticket the morning after anything changes
  • 90 days of history, day by day
  • Bot and rate limiting rules checked with the rest
  • Settings put back when the change was not yours

Response and Fix Times

  • Urgent (site down or hacked): a response within 1 hour during business hours, fixed the same day
  • Normal requests: a response within 1 business day, fixed within 2 business days
  • DNS changes made within 2 business days
  • Every request timed, and reported each month against these times
  • Who did what: our team or automation, in your report

What Sets It Apart

  • Drift caught the next morning
  • Set once, checked daily
  • Configured for your site, not a template
  • Nothing switched on that you did not ask for
  • Your Cloudflare account stays yours
  • Nothing installed on your website

Want Your Edge Configured Properly?

Tell us which site to look at. We will read its current Cloudflare settings and report what we find.

Cloudflare Defaults Compared with Edge Protection

Defaults are safe but generic. The value is in rules matched to your traffic, caching that leaves logged-in pages alone, and a daily comparison against what was set.

Cloudflare left on defaultsEdge Protection
What to compareCloudflare left on defaultsEdge Protection
FirewallGeneric rules, or none at allRules written for how your site is used
CachingGeneric, and able to serve the wrong pageTuned to how the site is built
BotsDefault handling, not tied to your trafficRules reviewed as your site changes
TLSLeft wherever it was first setKept current and checked every day
DriftFound during the next incidentCaught the next morning, and put back when it was not you
UpkeepSet once and forgottenRevisited as your site and traffic change

What Clients Say About Working with Cascadia

“I’ve always dreaded website management, but Cascadia has done an incredible job with my WordPress site, making it one less thing for me to worry about.”
Alex R.Cascadia client

Want Your Edge Configured Properly?

Talk to us

Who Edge Protection Fits Best

Sites Needing More Than a Default

Different sites need different rules, so we set the firewall, bot protection, rate limiting, caching, and SSL for yours. The result is written down, so you can see what protects you.

Get Started

Sites with Edge Settings Nobody Has Reviewed

A poor edge setup stays invisible until it costs you: a rule that blocks your own checkout, a cache that shows a logged-in page to everyone, a TLS setting that quietly fails a card payment.

Get Started

Agencies with Client Sites

If you manage Cloudflare for several clients, a daily comparison against recorded settings shows which site moved, and one team can put it right.

Get Started

Ready to Hand Off Your Edge Settings?

Send us the site and we will watch its Cloudflare settings from then on, speaking up when one moves.

How It Works

1. We Read Your Current Settings

We review the live Cloudflare configuration and tell you what is wrong with it. We look for things like an old TLS minimum, development mode left on, or caching that shows logged-in users the wrong page.

Get Started

2. We Set Them for How Your Site Is Used

Rules go on at the edge, not inside WordPress. Anything that could block real visitors, such as a country rule or a tight rate limit, is explained to you before it goes on.

Get Started

3. You Get a Monthly Report

After setup the morning comparison runs by itself. A setting that moved becomes a ticket naming it and its previous value, and a report arrives each month.

Get Started

See the work

Your Monthly Report

Once a month you get one report showing what happened with DNS changes, edge protection, and your domains and their expiry dates, what we did about it, and anything we need from you.

  • Delivered every month on the first Tuesday on or after the 3rd, at 11 AM Pacific, covering the month just ended
  • A private link by email to the full report online, which stays open for 90 days
  • Written in plain English with anything that needs you at the top and how to fix it
  • Every service in one report website by website, so everything you have with us is in one place
A sample monthly report: a summary of the month, tiles for uptime, mobile speed, updates applied, and AI answers, then the items that need attention with how to fix each one
A sample report. Every name and number in it is made up.

Pricing

What Edge Protection Costs

Edge Protection

$49/mo per domain
Month to monthNo setup feeLeave any time

What We Do for You

  • Rules written around your site
  • Form spam cut down at the edge
  • Browser cache set sensibly
  • 90 days of history, day by day
  • DNS changes made within 2 business days
  • Drift caught the next morning

Ask us

Answers to Common Edge Protection Questions

Comparing us with another provider? Our comparison pages take the main ones in turn.

Compare with Wordfence, Sucuri, and MoreCompare with Wordfence, Sucuri, and MoreCompare with Wordfence and More

Still have a question?

Can you set up Cloudflare firewall rules for my site?

Yes. We write the firewall, bot, and rate limit rules around how your site is actually used, and each morning we compare nine settings with what we set. It is $49 a month per domain.

What does Edge Protection cover?

The firewall rules, bot protection, rate limiting, caching, and SSL on your Cloudflare account. We set them for how your site is used, then compare nine settings with ours every morning, so a change you did not make is something you hear about from us.

How much does Edge Protection cost?

$49 a month per domain.

How is this different from just turning Cloudflare on?

Turning it on gives you the defaults. The work is deciding which rules suit your traffic, writing them, and then noticing the morning after one of them changes. Defaults are a reasonable starting point and nothing more.

Can I do this on Cloudflare's free plan?

Yes. The service is about configuring Cloudflare properly, not about buying a higher plan. Where a paid feature would genuinely help, we say so and explain why.

Will a firewall rule block my own customers?

That is the risk we plan around. Anything that could block real visitors, such as a country rule or an aggressive rate limit, is explained before it goes on. We write exceptions for the tools you use, and good bots are let through.

Will caching break logged-in pages or checkout?

Not when it is tuned. Caching is set to match how the site is built, browser cache is kept sensible, and Always Online covers an origin failure without serving a logged-in page to everyone.

What happens to TLS and HTTPS?

HTTPS is enforced and the TLS minimum is kept current instead of staying where it was first set. SSL mode is set correctly and checked daily, because a quietly wrong TLS setting tends to surface as a failed card payment rather than as an error anyone sees.

What happens when a setting drifts?

You hear the next morning. A setting that moved becomes a ticket naming it and the value it had before. If the change was not yours, we put it back.

Do you keep a record of what you change?

Yes. Every setting we change is recorded, and the daily snapshots are kept for 90 days, so you can see what something was, when it changed, and whether we did it.

What access do you need?

Access to your Cloudflare account, usually an invitation you can withdraw at any time, plus a note of anything that must not be touched. Nothing is installed on your website, and we need no access to the site itself.

When does the monthly report arrive?

The report goes out on the first Tuesday on or after the 3rd of each month, at 11 AM Pacific, and covers the month before. It is emailed to the people on your account who receive reports, and the online copy stays open for 90 days.

How soon does setup begin?

Setup starts within two business days, and the first full picture follows within a week.

How is Edge Protection different from Managed DNS?

Managed DNS covers the records that point traffic to the right place. Edge Protection covers the settings that protect that traffic once it arrives: firewall, bots, caching, and SSL. Many sites want both, and Domain Pro combines them with Domain Management.

Is it worth it for a small site?

A small site is often the one left exactly as Cloudflare shipped it. Nothing is installed anywhere, so running the service adds no load to the site itself.

Do I need Cascadia hosting or maintenance to buy this?

No. It is a monthly service that works with whatever hosting you use, because the changes happen in your Cloudflare account.

Ask Us Anything

We’d love to hear from you!