Gateway Sentry
Looking GlassDashboard

Products / Web Protection / WAF

The WAF That Lives at the Edge

A composable flow rules engine in front of your origin. Each rule matches a path pattern and activates modules: rate limit, block, challenge, headers, CORS, cache, or redirect.

per route flow rules403 / 429 or challenge0 app changes
Get ProtectedWeb Protection overview

Rules That Compose

Flow Rules

Each rule matches a path pattern and activates modules such as rate limit, block, headers, CORS, cache, and redirect. Stack them per route: your login page, your API, and your static assets each get exactly the treatment they need.

Enforcement

Actions include an immediate 403 Forbidden block, a 429 rate-limit response, a computational challenge page, or silent logging while you tune. Watch first, enforce when you are sure.

Bots & AI Scrapers

Block automated traffic by user agent with wildcard matching: python-requests, scrapy, curl, and friends can be blocked or challenged, and aggressive crawlers rate-limited per IP, session, or API key.

Headers & CORS

Manage CORS entirely at the edge, strip identifying headers, and inject security headers per route. Your application code never carries policy it does not need to know about.

A Rule Reads Like a Sentence

Match the login path, rate limit it per IP, challenge whatever exceeds it. Match the API, block everything but GET and POST. Each rule is declared in the dashboard and enforced at the edge in minutes, with silent logging when you want to watch before you commit.

One Engine, Every Layer

The same flow rules engine backs bot protection challenges and per-endpoint API limits, so one mental model covers everything the edge does to a request.

Keep Exploring

Bot Protection

The detection pipeline that decides who deserves a challenge.

API Protection

The same rules engine, tuned for endpoints instead of pages.

AI Threat Detection

Scoring that feeds the rules with live intelligence.

SaaS & Web Platforms

How product teams put the WAF to work.

Frequently Asked Questions

What is a web application firewall?
A web application firewall (WAF) inspects and filters HTTP traffic at the application layer before it reaches your origin server. Gateway Sentry runs a composable flow rules engine at the edge that can rate limit, block, challenge, or transform every request per route.
Is Gateway Sentry a good web application firewall for AI bots and scrapers?
Yes. The WAF blocks automated traffic by user agent with wildcard matching, so patterns like python-requests, scrapy, and curl used by AI scrapers and bots can be blocked or sent a computational challenge page. You can also rate limit aggressive crawlers per IP, per session, or per API key.
What is the difference between a WAF and an application layer firewall?
They are the same thing: a web application firewall is an application-layer (Layer 7) firewall that filters HTTP and HTTPS requests rather than raw packets. Gateway Sentry operates this layer at the edge so blocking, rate limiting, and header rules apply before traffic hits your server.
How does the Gateway Sentry WAF enforce rules?
Each flow rule matches a path pattern and activates modules such as rate limit, block, headers, CORS, cache, and redirect. Enforcement actions include an immediate 403 Forbidden block, a 429 rate-limit response, a computational challenge page, or silent logging.
How much does the web application firewall cost?
WAF traffic is billed on the usage-based web pricing of $30 per TB plus $0.55 per million requests, with no minimum commitment. You can deploy flow rules in minutes from a single dashboard with no application changes.

Get Protected in Minutes

Point your DNS at the edge and deploy rules from one dashboard. No code changes.

Get Protected