# Cloudflare AI Gateway vs Guard — 40° South

> Cloudflare AI Gateway is built for observability and content safety. Guard is built for Australian compliance evidence.

[← All comparisons ](/compare) 

Compare

#  Cloudflare AI Gateway vs Guard 

 Cloudflare AI Gateway is built for observability and content safety. Guard is built for Australian compliance evidence. 

Why this comes up

Cloudflare AI Gateway is a solid piece of infrastructure: it caches AI responses, rate-limits, logs requests, tracks costs, and offers basic content moderation. If you want a dashboard of your AI traffic and some guardrails on output, it delivers.

What it doesn’t do is anything Australia-specific or evidentiary. There’s no Tax File Number, Medicare, or ABN detection. There’s no per-call cryptographic attestation. There’s no regulatory mapping to CPS 234, the Privacy Act, or AI transparency. It’s a content-safety and observability tool, not a compliance-evidence tool.

Those are different problems. Knowing your AI traffic volume and blocking obviously toxic output is useful operationally. Proving to APRA that an Australian PII control fired on a specific call, and signing that proof so it can’t be altered, is what regulated buyers actually need. Guard does the latter.

The difference

Cloudflare gives you observability and content safety. Guard gives you Australian regulatory evidence.

## Side by side

| Capability                                              | Cloudflare AI Gateway | 40° South Guard |
| ------------------------------------------------------- | --------------------- | --------------- |
| Caching, rate limiting and observability                | ✓                     | \~              |
| Basic content moderation                                | ✓                     | \~              |
| Australian personal data detection (TFN, Medicare, ABN) | ✗                     | ✓               |
| Prompt injection detection inside uploaded documents    | ✗                     | ✓               |
| Per-call signed proof                                   | ✗                     | ✓               |
| CPS 234 / Privacy Act regulatory mapping                | ✗                     | ✓               |
| 7-year tamper-evident audit trail                       | ✗                     | ✓               |
| Australian data residency guarantee                     | \~                    | ✓               |

✓ = supported · \~ = partial · ✗ = not supported 

Reflects publicly available information as at July 2026\. Tools change; check current vendor documentation. 

[ Download the full comparison (PDF) ](/downloads/guard-vs-cloudflare.pdf) 

Could you run them together?

Yes. If you already use Cloudflare AI Gateway for caching and observability, keep it. Run Guard in the same path for the compliance layer it doesn’t provide: Australian PII detection, signed attestations, and regulatory mapping.

Observability and evidence are complementary, not competing.

## See Guard on your own AI calls 

Book a demo and we’ll show you a signed attestation for a real call, mapped to your obligations under CPS 234, the Privacy Act, and AI transparency. 

[Book a demo → ](/#get-started) [See all comparisons ](/compare)

---
Markdown version of https://40south.au/compare/cloudflare for AI readers. Site index for LLMs: https://40south.au/llms.txt