A web firewall and a cache at the door
Every visit passes a web firewall and limits before it reaches your app, with an Under attack switch, and static files are served from a cache.
Updated 17 Oct 20261 min read
Most attacks should stop at the door, before they reach your code.
What's new
A web firewall in front of every app. For now it watches: it records what it would block, and blocks nothing yet, while we make sure it never stops real visitors.
Limits on how fast one visitor may knock, and bans for password guessers.
Under attack: one switch, and every visitor sees a short check in their browser first, while limits get stricter.
Relax a rule for your own app when it stops something legitimate. Your logs show the rule's number.
A cache at the door: images, CSS and JavaScript your app allows to be cached are served fast. Each deploy clears it, and so does Clear the cache.
Find it on your app's Protection and speed card. Read Protection and speed.